jubeira commented 4 months ago

Deployment preparation: `FraxtalRootGaugeFactory`

Build-info: https://github.com/balancer/balancer-v2-monorepo/commit/281e98f78dca2c3aabb990c5841e5036c12fa7f6. 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:

[x] Deployments README is updated with the new task name and link
[x] Task README has a description and links to the artifacts
[x] build-info is updated with artifacts compiled at the specified commit
[x] Artifacts are generated from build-info
[x] New task has a working fork test

Deprecating old tasks checklist: N/A

Code checklist:

[x] The diff is legible and has no extraneous changes
[x] Complex code has been commented in tests and scripts
[x] Fork test block number and test cases are appropriate for this deployment
[x] The base branch is either master, or there's a description of how to merge

Issue Resolution

N/A

jubeira commented 3 months ago

@EndymionJkb added deposit tx to description (it's also in the inputs script).

jubeira commented 3 months ago

Updated build info and fork test now with gauge that has network tag. PTAL @EndymionJkb

balancer / balancer-deployments