-
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
Deployment preparation: Fraxtal root gauge factory #117
Deployment preparation: Fraxtal root gauge factory #117
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.
See comment on naming. Also, we usually include manual bridge transactions for root gauges, to ensure the events are the same, etc. (e.g., #80)
@EndymionJkb added deposit tx to description (it's also in the inputs script). |
Updated build info and fork test now with gauge that has network tag. PTAL @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.
I verified that the build-info matches and tests pass. Looks good! Just some minor docs suggestions.
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.
LGTM
Deployment preparation:
FraxtalRootGaugeFactory
Build-info: balancer/balancer-v2-monorepo@281e98f.
The code is very similar to the Optimism Root Gauge; it just adds a network tag to identify the target L2.
The fork test is a mix between 'modern' gauge tests (Avax, Base) which use LZ-based gauges with the Optimism Root Gauge Factory test. The setup is the latest (i.e. it creates a synthetic veBAL whale) and all the cooldowns and periods are fixed, and it checks the Optimism bridge events (which are the same in OP and Fraxtal).
About the inputs: L1 token bridge and Fraxtal BAL addresses naturally differ between OP and Fraxtal. Besides that, the initial gas limit also differs: the one in this task was taken from a test TX.
Deposit TX sample: https://etherscan.io/tx/0xbbff35c8add8d11f2fac562731ec9dab58582c3a14b64580d01b8c757fc976bd
Recipient TX: https://fraxscan.com/tx/0x6b27d68f24275892a22c0a53d2de40cd4610c465b7c1233dc917580c0a855fc9
Deployment preparation tasks checklist:
README
is updated with the new task name and linkREADME
has a description and links to the artifactsbuild-info
is updated with artifacts compiled at the specified commitbuild-info
Deprecating old tasks checklist: N/A
Code checklist:
master
, or there's a description of how to mergeIssue Resolution
N/A