Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

There is no chain_id= 97 for 1.4.1 contracts #331

Closed
IvanKodak opened this issue Dec 8, 2023 · 3 comments
Closed

There is no chain_id= 97 for 1.4.1 contracts #331

IvanKodak opened this issue Dec 8, 2023 · 3 comments

Comments

@IvanKodak
Copy link
Contributor

IvanKodak commented Dec 8, 2023

I want to test gnosis multisig creation on BSC testnet, but I can't do it, because there is no BSC testnet chain id for 1.4.1 version.
Please check: https://github.com/safe-global/safe-deployments/blob/v1.28.0/src/assets/v1.4.1/safe_proxy_factory.json

But in network contract is exist: https://testnet.bscscan.com/address/0x4e1DCf7AD4e460CfD30791CCC4F9c8a4f820ec67

@mmv08
Copy link
Member

mmv08 commented Dec 11, 2023

I want to test gnosis multisig creation on BSC testnet, but I can't do it, because there is no BSC testnet chain id for 1.4.1 version. Please check: https://github.com/safe-global/safe-deployments/blob/v1.28.0/src/assets/v1.4.1/safe_proxy_factory.json

But in network contract is exist: https://testnet.bscscan.com/address/0x4e1DCf7AD4e460CfD30791CCC4F9c8a4f820ec67

Since the deployment process is trustless (anyone can deploy contracts), such things may happen. You create a PR to add the address to the list of deployments

@DmytroShalaiev
Copy link
Contributor

@mmv08 the PR is waiting for review, thanks.

@nlordell
Copy link
Collaborator

nlordell commented Jun 3, 2024

Closed by #372

@nlordell nlordell closed this as completed Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants