-
Notifications
You must be signed in to change notification settings - Fork 175
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
[New chain]: Snaxchain 1.3.0 eip155 #1335
Comments
Unfortunately, the automated github check will fail since Snaxchain Mainnet is based on OP stack and Master Copies were predeployed. |
Hello @falvaradorodriguez 👋 |
Validation has failed with the following errors:
Validation failed!❌ |
/execute |
🚀 Starting to apply the changes for the new address! |
✅ Execution finished, please review the PR and merge it. |
Hello @ElvisKrop No worries. In this particular case, you can leave the hash without value and we do the validation manually. The automatic PR is already created and merged with the commit of the master copy addresses completed in block 0 (Genesis). Thanks. |
Thanks a lot @falvaradorodriguez ! |
Summary
Chain ID
2192
Chain detail URL
https://chainlist.org/chain/2192
RPC URL
https://mainnet.snaxchain.io/
Blockscout Client URL
https://explorer.snaxchain.io/api/v1/graphql
Etherscan Client URL
No response
Etherscan Client API URL
No response
Version
1.3.0
Address (Master copy)
0x69f4D1788e39c87893C980c06EdF4b7f686e2938
Deployment Tx hash (Master copy)
No response
Block explorer URL (Master copy)
https://explorer.snaxchain.io/address/0x69f4D1788e39c87893C980c06EdF4b7f686e2938
Address (Master copy L2)
0xfb1bffC9d739B8D520DaF37dF666da4C687191EA
Deployment Tx hash (Master copy L2)
No response
Block explorer URL (Master copy L2)
https://explorer.snaxchain.io/address/0xfb1bffC9d739B8D520DaF37dF666da4C687191EA
Address (Proxy factory)
0xC22834581EbC8527d974F8a1c97E1bEA4EF910BC
Deployment Tx hash (Proxy factory)
0x145a5cbf4142848ca294cb93fce63026563846dd25fd00ff56a6682cdf1244a8
Block explorer URL (Proxy factory)
No response
The text was updated successfully, but these errors were encountered: