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

veBALDeploymentCoordinator gauge deployment #1187

Merged
merged 8 commits into from
Mar 22, 2022
Merged

Conversation

TomAFrench
Copy link
Contributor

This PR connects the veBALDeploymentCoordinator to the gauge factories and GaugeAdder contracts.

At construction time we provide two arrays - one of pools for which we want to deploy gauges for (these will be automatically added to the GaugeController), one of the 4 recipients to receive the BAL for the gauge types which won't initially have their proper gauge contracts (SingleRecipientGauges will be deployed to point at all of these).

@TomAFrench TomAFrench requested a review from nventuro March 21, 2022 15:46
Co-authored-by: Nicolás Venturo <nicolas.venturo@gmail.com>
@nventuro nventuro merged commit bf43cc9 into master Mar 22, 2022
@nventuro nventuro deleted the veBAL-gauge-deployment branch March 22, 2022 17:59
TomAFrench added a commit that referenced this pull request Mar 24, 2022
* master:
  Deploy Batch Relayer V2 to Polygon (#1182)
  Fix reading historical balances/total supply by timestamp (#1201)
  Prevent duplicate gauges for a pool being added to GaugeController (#1185)
  Authorizer: Fix missing renames (#1193)
  Misc fixes on LM system (#1196)
  Lock gauge implementation on LiquidityGaugeFactory (#1195)
  Create bal_supply.md (#1192)
  Use BALTokenHolder factory in coordinator (#1194)
  fix: Decimal math errors in stable-pool math.ts (#1188)
  Fix tests for real now
  Fix tests
  Add BAL Token Holder contract (#1149)
  Authorizer: Rename and improve wording (#1167)
  ManagedPool weight storage (#1102)
  Add snapshot link to veBAL script readme (#1189)
  veBALDeploymentCoordinator gauge deployment (#1187)
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