Payload PR - BIP-199
The poolRecoveryHelper is a smart contract, which allows permissionless calling of the enableRecoveryMode() call
assuming that any of the rate providers used in a given pool are failing. This allows anyone in the balancer or greater web3 community to
put the pools into a state where bad rateProvider data does not create routing issues. It also allows for permissionless
automation to be setup to look for problems and quickly react.
More details on RecoveryMode and the poolRecovery Manager can be found in the text of BIP-121 which originally introduced these concepts.
This BIP requests adding authoriation for the pool recovery manager to operate on the recently deployed v3 Weighted Pool Factory and the v3 Composable Stable Pool Factory and all pools generated by them.
The transaction details were generated by this script with inputs and outputs in this directory
The following files can be found both linked below and in the payload PR linked above:
|Filename||Description of Contents|
|inputs.json||The inputs to the script mapping functions and deployments to target addresses that can execute them.|
|results_address_sorted.md||The resulting changes printed in a table sorted by target chain and target address. (to easily understand permisisons granted)|
|results_deployment_sorted.md||The resulting changes printed in a table sorted by target chain and target deployment. (for verification against action ids)|
|function_descriptions.md||A table that describes what each function that is being granted privileged access to allows.|
||For each change with changes, a transaction builder json named after said chain exists to apply the changes described in the tables.|
In the tables above:
The “poolRecoveryHelper” caller group:
- maps to the deployed poolRecoveryHelper contract
As described in the payload json, the authorizer will be called to grant the roles as described.
The change can be reviewed by the below by comparing the results_deployment_sorted.md file to the source of truth, which should match the order found in the source of truth for actionIds on the balancer-v2-monorepo.
For record, the contents of results_address_sorted.md are printed here:
This BIP is about allowing automation and the greater Web3 community to move pools into a state where there is less risk,
in situations where there could be some concern about their function. A number of higher AUM V2 pools spent quite a bit
of time in Recovery Mode recently as a result of some recently discovered and patched reentrency issues.
It has been well demonstrated that, while recoveryMode can create some minor UX problems for exiting pools and results in less revenue being earned by the DAO, it otherwise has no ill-effects nor creates new risk.
Directory of Addresses used by script which generated the table and multsig payloads