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. Links are included at the end of this post.
The following token recently underwent a contract migration. I would like to propose modifying the existing whitelist entry for this token so that it points to the new contract address. The token will retain its current liquidity cap for
capFactor and any existing price pegs used to compute
wrapFactor. The old contract address will no longer participate in liquidity mining.
MODIFY ANT 0x960b236A07cf122663c4303350609A66A7B288C0 -> 0xa117000000f279D81A1D3cc75430fAA017FA5A2e
I would also like to propose adding the following new tokens to the whitelist:
ADD DFD 0x20c36f062a31865bED8a5B1e512D9a1A20AA333A ADD SEEN 0xCa3FE04C7Ee111F0bbb02C328c699226aCf9Fd33
The proposed changes will go into effect at 00:00 UTC on Monday, November 9. Pools containing whitelisted tokens will begin to accrue BAL rewards beginning at 00:00 UTC on Monday; but they may not appear on the Balancer pools UI with symbol/logo until a bit later in the week, most likely Tuesday or Wednesday. Please be patient. Furthermore, whitelisted tokens will not be added to the Balancer exchange UI; the core team adds tokens to the official exchange UI at their own discretion and considers a variety of factors. Tokens can always be traded using contract addresses in place of symbols, and anyone is free to fork the open source exchange UI to add more symbols.
Resulting Soft/Hard Pegs
The following price pegs will be added to the BAL mining scripts in response to the whitelist changes. At time of writing, soft pegs receive a
wrapFactor of 0.2 and hard pegs receive a
wrapFactor of 0.1.
There are no new price pegs introduced this week.
Some requested tokens were omitted this week.
The following tokens are not verified on Etherscan, which violates Whitelist Criterion #1: The token’s smart contract must be verified on Etherscan. Neglecting this small degree of transparency adds unnecessary friction to the process of vetting for the remaining criteria.
UNVERIFIED TONE 0x2Ab6Bb8408ca3199B8Fa6C92d5b455F820Af03c4 UNVERIFIED VLO 0x98ad9B32dD10f8D8486927D846D4Df8BAf39Abe2
The following token lacks a price feed through the CoinGecko API, which violates Whitelist Criterion #7: The token must have a price feed accessible via CoinGecko’s API. This is instrumental to calculating a pool’s eligibility for BAL rewards.
NO PRICE FEED FNX 0xeF9Cd7882c067686691B6fF49e650b43AFBBCC6B
Reference: Prior Proposals