-
Notifications
You must be signed in to change notification settings - Fork 176
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]: Berachain bArtio #1196
Labels
Comments
Validation has failed with the following errors:
Validation failed!❌ |
Validation has failed with the following errors:
Validation failed!❌ |
All elements have been validated and are correct:
Validation successful!✅ |
/execute |
🚀 Starting to apply the changes for the new address! |
✅ Execution finished, please review the PR and merge it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
I would like to add Berachain bArtio safe addresses.
Chain ID
80084
Chain detail URL
https://chainlist.org/chain/80084
RPC URL
https://bera-testnet.nodeinfra.com
Blockscout Client URL
No response
Etherscan Client URL
No response
Etherscan Client API URL
No response
Version
1.3.0
Address (Master copy)
0xd9Db270c1B5E3Bd161E8c8503c55cEABeE709552
Deployment Tx hash (Master copy)
0xdc938bf371028a858a7b03c2873d5c0155963dd7a15e5301997c0f1c0781a1b6
Block explorer URL (Master copy)
https://bartio.beratrail.io/address/0xd9Db270c1B5E3Bd161E8c8503c55cEABeE709552
Address (Master copy L2)
0x3E5c63644E683549055b9Be8653de26E0B4CD36E
Deployment Tx hash (Master copy L2)
0x42ca351bb114ec7c71ddab1f5f563d8beb62f7795529fed0edeeb3a9388d9d7d
Block explorer URL (Master copy L2)
https://bartio.beratrail.io/address/0x3E5c63644E683549055b9Be8653de26E0B4CD36E
Address (Proxy factory)
0xa6B71E26C5e0845f74c812102Ca7114b6a896AB2
Deployment Tx hash (Proxy factory)
0xa00794fb20d2d31802465188ade3a91f4bc1951f2ad57594ba9b2ca3e9bf722e
Block explorer URL (Proxy factory)
https://bartio.beratrail.io/address/0xa6B71E26C5e0845f74c812102Ca7114b6a896AB2
The text was updated successfully, but these errors were encountered: