-
Notifications
You must be signed in to change notification settings - Fork 292
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
feat: add 1.4.1 canonical contracts for Plume #882
Conversation
ERROR: chain is not registered on Chainlist |
28b4987
to
8841705
Compare
You can deploy the contracts by following the steps mentioned here: https://github.com/safe-global/safe-smart-account/tree/v1.4.1-3 |
Hey @remedcu - all the contracts are deployed already to the canonical addresses! For example: https://explorer.plumenetwork.xyz/address/0xfd0732Dc9E303f09fCEf3a7388Ad10A83459Ec99 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Running manually:
npm run review:verify-deployment -s -- --version "v1.4.1" --chainId 98865 --rpc "https://phoenix-rpc.plumenetwork.xyz/FH7uok8YdCXHhBu4B18j632wpHogyMYan" --verbose
Parsed options:
{
version: 'v1.4.1',
chainId: '98865',
rpc: 'https://phoenix-rpc.plumenetwork.xyz/',
verbose: true
}
chain 98865 exists on Chainlist
RPC reported chain 98865
CompatibilityFallbackHandler deployments:
• canonical deployment OK
CreateCall deployments:
• canonical deployment OK
MultiSend deployments:
• canonical deployment OK
MultiSendCallOnly deployments:
• canonical deployment OK
Safe deployments:
• canonical deployment OK
SafeL2 deployments:
• canonical deployment OK
SafeMigration deployments:
• canonical deployment OK
SafeProxyFactory deployments:
• canonical deployment OK
SafeToL2Migration deployments:
• canonical deployment OK
SafeToL2Setup deployments:
• canonical deployment OK
SignMessageLib deployments:
• canonical deployment OK
SimulateTxAccessor deployments:
• canonical deployment OK
Add new chain
Please fill the following form:
Provide the Chain ID (Only 1 chain id per PR).
Provide RPC URL for the chain (should be able to query at least 3+ requests per second for automatic PR check).
Relevant information: