Skip to content

Conversation

@clement-ux
Copy link
Collaborator

Description

This PR only create Governance script to migrate to new CurvePB.
This pending governance proposal will upgrade PoolBooster CentralRegistry to support new CurvePoolBoosterFactorty, which support new CurvePoolBooster.
Once this proposal succeed, it could be possible to execute this one that:

  • Deploy CurvePB using the new CurvePBFactory, corresponding to the 4 CurvePB we already have.
  • UndelegateYield from related CurvePool to CurvePoolBooster
  • DelegateYield from related CurvePool to new CurvePoolBooster.
  • RescueToken (OETH or OUSD) from old CurvePB and send them to new CurvePB.

New CurvePB address have been computed using this contract "0xB6073788e5302122F4DfB6C5aD53a1EAC9cb0289".

Copy link
Member

@sparrowDom sparrowDom left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Collaborator

@shahthepro shahthepro left a comment

Choose a reason for hiding this comment

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

  • All deployed contracts are listed in the deploy PR's description
    • Found 0xb929fD0C424B0c5e19DCF2E32abd18E65A50D0F1 and 0xB6073788e5302122F4DfB6C5aD53a1EAC9cb0289 from governance proposal
  • Deployed contract's verified code (and all dependencies) match the code in master
  • Contract constructors have correct arguments
  • The transactions that interacted with the newly deployed contract match the deploy script.
  • Governance proposal matches the deploy script
  • Smoke tests pass after fork test execution of the governance proposal

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.

4 participants