Skip to content

Deployment: Liquidity Bootstrapping Pool V4 - #399

Merged
EndymionJkb merged 8 commits into
masterfrom
deployment/lbp-v4
May 18, 2026
Merged

EndymionJkb merged 8 commits into
masterfrom
deployment/lbp-v4

Conversation

@EndymionJkb

Copy link
Copy Markdown
Collaborator

Deployment: Liquidity Bootstrapping Pool (V4)

This is the same as V3, minus the migration features.

One code change: had to extend the pause window to the current standard (still had the old value).

Deployment tasks checklist:

  • Contract(s) deployed to all target networks / testnets
  • TX IDs are properly generated
  • Action IDs are generated after deployment (if applicable)
  • If a governance proposal is required, Action IDs have been sent to the Maxis
  • Outputs for all target networks are generated, and linked in the task readme
  • Addresses files are up to date with the new deployment
  • Contracts are verified in every network
  • Deployments CHANGELOG is updated
  • There are no code changes of any kind

Issue Resolution

@EndymionJkb EndymionJkb changed the title Deployment: Liquidity Bootstrapping Pool (V4) Deployment: Liquidity Bootstrapping Pool V4 May 14, 2026
@EndymionJkb
EndymionJkb requested a review from joaobrunoah May 14, 2026 19:12
joaobrunoah
joaobrunoah previously approved these changes May 14, 2026

@joaobrunoah joaobrunoah left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM!

# Conflicts:
#	CHANGELOG.md
#	action-ids/arbitrum/action-ids.json
#	action-ids/avalanche/action-ids.json
#	action-ids/base/action-ids.json
#	action-ids/gnosis/action-ids.json
#	action-ids/hyperevm/action-ids.json
#	action-ids/mainnet/action-ids.json
#	action-ids/monad/action-ids.json
#	action-ids/optimism/action-ids.json
#	action-ids/plasma/action-ids.json
#	action-ids/sepolia/action-ids.json
#	action-ids/xlayer/action-ids.json
#	addresses/arbitrum.json
#	addresses/avalanche.json
#	addresses/base.json
#	addresses/gnosis.json
#	addresses/hyperevm.json
#	addresses/mainnet.json
#	addresses/monad.json
#	addresses/optimism.json
#	addresses/plasma.json
#	addresses/sepolia.json
#	addresses/xlayer.json
#	deployment-txs/arbitrum.json
#	deployment-txs/avalanche.json
#	deployment-txs/base.json
#	deployment-txs/gnosis.json
#	deployment-txs/hyperevm.json
#	deployment-txs/mainnet.json
#	deployment-txs/monad.json
#	deployment-txs/optimism.json
#	deployment-txs/plasma.json
#	deployment-txs/sepolia.json
#	deployment-txs/xlayer.json

@joaobrunoah joaobrunoah left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM!

TestBalancerToken,
Router: TrustedRouter,
PauseWindowDuration: 4 * YEAR,
PauseWindowDuration: 75 * 12 * MONTH,

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

We changed it to 75 years?
Well, after the stable stuff, that's safer for sure.

@EndymionJkb EndymionJkb May 18, 2026

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

I personally think 75 years is excessive, but it's how Juani deployed the other pools, so I stayed with it.

Probably 10 would be fine (25 if we want to be crazy). 75 is actually bumping up against the uint32 limit (or it will in 6 years). We might as well just do type(uint32).max at that point.

I didn't want to leave it at 4 (the old leftover value).

@EndymionJkb
EndymionJkb merged commit bb4693d into master May 18, 2026
49 checks passed
@EndymionJkb
EndymionJkb deleted the deployment/lbp-v4 branch May 18, 2026 22:23
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.

2 participants