On behalf of the Balancer community, I’d like to propose the following modifications to the token whitelist used for BAL governance distribution. For reference, please see the previous proposals which detail the motivation for creation of the whitelist and define the list of tokens used to date:
https://forum.balancer.fi/t/proposing-the-token-whitelist-for-bal-distribution
https://forum.balancer.fi/t/bal-whitelist-round-2
https://forum.balancer.fi/t/bal-whitelist-round-3
-
Out of an abundance of caution, I propose to temporarily remove AMPL from the whitelist. While there are no immediate concerns, the supply rebasing mechanism does present some interesting complexities with respect to Balancer’s internal balance tracking and gulp() arbitrage opportunities. In light of the deflationary token attack, the Balancer team will collaborate with the Ampleforth team on an audit. This audit will explore the possibly unforeseen consequences of AMPL’s daily supply rebase as it concerns Balancer pools. After completion of the audit, so long as no vulnerabilities are found, AMPL will be reinstated to the token whitelist.
REMOVE AMPL 0xD46bA6D942050d489DBd938a2C909A5d5039A161 -
DFOhub’s BUIDL token has undergone a contract swap. The second item on this proposal is the migration of this token’s whitelist entry from the old contract to the new one:
CHANGE BUIDL 0x7b123f53421b1bF8533339BFBdc7C98aA94163db -
Finally, I propose adding the following tokens to the existing whitelist:
ADD BZRX 0x56d811088235F11C8920698a204A5010a788f4b3 ADD DUSK 0x940a2dB1B7008B6C776d4faaCa729d6d4A4AA551 ADD GRG 0x4FbB350052Bca5417566f188eB2EBCE5b19BC964 ADD MCB 0x4e352cF164E64ADCBad318C3a1e222E9EBa4Ce42 ADD MTA 0xa3BeD4E1c75D00fa6f4E5E6922DB7261B5E9AcD2 ADD MYST 0xa645264C5603E96c3b0B078cdab68733794B0A71 ADD ONG 0xd341d1680Eeee3255b8C4c75bCCE7EB57f144dAe ADD RARI 0xFca59Cd816aB1eaD66534D82bc21E7515cE441CF ADD SWAP 0xCC4304A31d09258b0029eA7FE63d032f52e44EFe ADD UTRUST 0x70a72833d6bF7F508C8224CE59ea1Ef3d0Ea3A38 ADD YFI 0x0bc529c00C6401aEF6D220BE8C6Ea1667F6Ad93e ADD sDEFI 0xe1aFe1Fd76Fd88f78cBf599ea1846231B8bA3B6B ADD sXAG 0x6A22e5e94388464181578Aa7A6B869e00fE27846 ADD wNXM 0x0d438F3b5175Bebc262bF23753C1E53d03432bDE
The proposed changes would go into effect at 00:00 UTC on Monday, July 20.