-
Notifications
You must be signed in to change notification settings - Fork 39
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
Network deployment: Mode #116
Conversation
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.
Check the batch-relayer-v6; copy/pasted fraxtal reference
"ManagedPoolAmmLib": "0x6817149cb753BF529565B4D023d7507eD2ff4Bc0", | ||
"ExternalWeightedMath": "0x6B5dA774890Db7B7b96C6f44e6a4b0F657399E2e", | ||
"RecoveryModeHelper": "0x7Ba29fE8E83dd6097A7298075C4AFfdBda3121cC", | ||
"ManagedPoolFactory": "0x043A2daD730d585C44FB79D2614F295D2d625412", |
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.
Weird that the Pool verified, but not the Factory
Good catch; thanks @EndymionJkb ! |
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.
All I noticed was the relayer thing. Looks good now.
Still didn't verify the Managed Pool factory, but it did everything else, and they're not used anyway
Description
Deployment to Mode network. Similar to #114, but without veBAL support. Child chain gauges are deployed, but we don't expect to read veBAL balances.
Most of the contracts should be verified in modescan; only managed pool factory threw an error.
Type of change
Checklist:
master
, or there's a description of how to mergeIssue Resolution
N/A