Skip to content
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: Stable Pool V2 #212

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

EndymionJkb
Copy link
Collaborator

@EndymionJkb EndymionJkb commented Mar 17, 2025

Deployment preparation: Stable Pool V2

Deploy V2 of the Stable Pool, which raises the amp factor limit and allows the swap fee manager to change the amp factor without governance intervention.

build-info: balancer/balancer-v3-monorepo@e1ae7f0

Note that the readme issue with the Cow Fee Burner in the wrong place is addressed in PR #210.

Deployment preparation tasks checklist:

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

Deprecating old tasks checklist:

  • Old task was moved to deprecated/ directory
  • Deployments README is updated: old task is moved to the 'deprecated' section, and links are updated with the deprecated/ prefix
  • Old task imports in index.ts, input.ts and fork tests are updated
  • Old task README is updated with a warning sign, a link to the replacement task and a short description

Code checklist:

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

Issue Resolution

Closes #184

joaobrunoah
joaobrunoah previously approved these changes Mar 18, 2025
Copy link
Contributor

@joaobrunoah joaobrunoah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@@ -7,7 +7,7 @@ import { ONES_BYTES32, ZERO_ADDRESS } from '@helpers/constants';
import { bn, fp } from '@helpers/numbers';
import { StablePoolDeployment } from '../input';

describeForkTest('StablePool-V3', 'mainnet', 21336200, function () {
describeForkTest.skip('StablePool-V3', 'mainnet', 21336200, function () {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice to know that we need to actively skip the tests inside the deprecated folder. I wonder if there's a way to automatically ignore these tests.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We'd have to special-case it in the scripts, which we generalized to find everything (making other things easier). It's possible, but since deprecation isn't that common, maybe it's not too onerous. (Come to think of it, we should probably add that to the deprecation checklist then, which we just changed.)

Technically they should all still work; I believe we skip them mainly to save CI time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Prepare Stable Pool V2 for Balancer V3
2 participants