On behalf of the Balancer community, I’d like to propose the following modifications to the token whitelist used for $BAL governance token distribution. All new tokens will be placed at
cap1 ($1M) as described in the updated whitelist proposal. At any time, community members may propose on the forum to increase a token’s cap to the next tier.
As a reminder, these whitelist proposals are pre-approved on objective technical criteria, so they are not subject to community vote. To suggest a token for inclusion in one of these proposals, please use the #token-requests channel in the Balancer Discord. Requested tokens will be vetted in a single batch at the end of each week. The official instructions and listing criteria can be found here.
For reference, the active whitelist can be found here. Note that the additions suggested within this proposal are unlikely to appear on the official list until a few days after publication. Also see the original motivation for creating the whitelist.
I would like to propose adding the following new tokens to the whitelist:
ADD 300 0x167E2A574669b0EeB552aaF3Da47c728cb348a41 ADD GRT 0xc944E90C64B2c07662A292be6244BDf05Cda44a7 ADD renFIL 0xD5147bc8e386d91Cc5DBE72099DAC6C9b99276F5
The proposed changes will go into effect at 00:00 UTC on Monday, December 21. Pools containing newly 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. For reference, please see the
SOFT renFIL <-> FIL group
Some requested tokens were omitted this week.
The following token has optional transfer fee functionality. Currently, all fees are set to zero; however, the owner has authority to re-enable transfer fees at any time, which would be a violation of Whitelist Criterion #3: The token’s
transferFrom() implementations must exhibit the expected behavior - namely, transferring N tokens from one address to another. Certain divergences from this behavior, such as transfer fees, can cause issues with Balancer pools, and these tokens will be rejected. The community should decide whether or not to trust the contract owner not to re-enable fees. For now, this token is denied as a matter of precaution pending community consensus.
TRANSFER FEE EURS 0xdB25f211AB05b1c97D595516F45794528a807ad8
The following tokens lack price feeds via the CoinGecko API, which is a violation of 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 ibETH 0x67B66C99D3Eb37Fa76Aa3Ed1ff33E8e39F0b9c7A NO PRICE FEED YD-BTC-MAR21 0x002f0B1A71C5730CF2F4dA1970A889207BdB6D0D NO PRICE FEED YD-ETH-MAR21 0x90f802C7E8fb5D40B0De583e34C065A3bd2020D8