On behalf of the Balancer community, I’d like to propose the following modifications to the token whitelist used for BAL governance distribution. As a reminder, these whitelist proposals are now pre-approved on objective technical criteria only, so they are not subject to community vote. All new tokens will be placed at cap1
for liquidity mining, meaning each token’s measured BAL-eligible liquidity is scaled to a maximum of $1M (at time of writing). At any time, community members may propose to increase a token’s cap to the next tier. 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
https://forum.balancer.fi/t/bal-whitelist-round-4
https://forum.balancer.fi/t/bal-whitelist-round-5
https://forum.balancer.fi/t/bal-whitelist-round-6
https://forum.balancer.fi/t/bal-whitelist-round-7
https://forum.balancer.fi/t/bal-whitelist-round-8
https://forum.balancer.fi/t/proposal-to-update-the-whitelist-process/217
First, I would like to propose modifying the following contract addresses in the whitelist. These tokens are already whitelisted but have migrated to new contracts:
MODIFY ARTE 0x34612903Db071e888a4dADcaA416d3EE263a87b9
MODIFY DOS 0x0A913beaD80F321E7Ac35285Ee10d9d922659cB7
MODIFY OCEAN 0x7AFeBBB46fDb47ed17b22ed075Cde2447694fB9e
I would also like to propose adding the following new tokens to the whitelist:
ADD BAND 0xBA11D00c5f74255f56a5E366F4F77f5A186d7f55
ADD DAM 0xF80D589b3Dbe130c270a69F1a69D050f268786Df
ADD eMTR 0x29E9fDF5933824ad21Bc6dbb8BF156EFA3735e32
ADD eMTRG 0xBd2949F67DcdC549c6Ebe98696449Fa79D988A9F
ADD EVAN 0x89E3aC6Dd69C15e9223BE7649025d6F68Dab1d6a
ADD FLUX 0x469eDA64aEd3A3Ad6f868c44564291aA415cB1d9
ADD GRT 0xb83Cd8d39462B761bb0092437d38b37812dd80A2
ADD LOCK 0x95172ccBe8344fecD73D0a30F54123652981BD6F
ADD QDAO 0x3166C570935a7D8554c8f4eA792ff965D2EFe1f2
ADD SAI 0x89d24A6b4CcB1B6fAA2625fE562bDD9a23260359
ADD sXMR 0x5299d6F7472DCc137D7f3C4BcfBBB514BaBF341A
ADD SXP 0x8CE9137d39326AD0cD6491fb5CC0CbA0e089b6A9
ADD TEND 0x1453Dbb8A29551ADe11D89825CA812e05317EAEB
ADD USDQ 0x4954Db6391F4feB5468b6B943D4935353596aEC9
ADD VLT 0x6b785a0322126826d8226d77e173d75DAfb84d11
ADD YAMv2 0xAba8cAc6866B83Ae4eec97DD07ED254282f6aD8A
ADD YFII 0xa1d0E215a23d7030842FC67cE582a6aFa3CCaB83
The proposed changes would go into effect at 00:00 UTC on Monday, August 24.