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 each Friday, to take effect the following Monday. 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 ARCX 0xED30Dd7E50EdF3581AD970eFC5D9379Ce2614AdB ADD MPL 0x33349B282065b0284d756F0577FB39c158F935e6 ADD O-OCEAN-MAR22 0x24D8C2163D6B13A6B8770B794d00c98Cb4E0cBCa ADD SALT 0x4156D3342D5c385a87D264F90653733592000581
The proposed changes will go into effect at 00:00 UTC on Monday, April 26. 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.
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 O-OCEAN-MAR22 <-> USD group
Some requested tokens were omitted this week.
The following tokens lack price feeds via the CoinGecko API, which means they can be listed on the UI but are not yet eligible for liquidity mining due to violation of Whitelist Criterion #7: The token must have a price feed accessible via CoinGecko’s API, e.g. this example link for WETH. This is instrumental to calculating a pool’s eligibility for BAL rewards. If a token meets all of the remaining criteria but not this criterion, it can be added to the UI whitelist and reconsidered for the mining whitelist once the price feed becomes available.
OMIT ARES 0x358AA737e033F34df7c54306960a38d09AaBd523 No price feed OMIT oneBTC 0xC88F47067dB2E25851317A2FDaE73a22c0777c37 No price feed OMIT oneETH 0xEc0d77a58528a218cBf41Fa6E1585c8D7A085868 No price feed OMIT oneLINK 0x18Cc17a1EeD37C02A77B0B96b7890C7730E2a2CF No price feed OMIT oneVBTC 0x7BD198b9107496fD5cC3d7655AF52f43a8eDBc4C No price feed OMIT oneWING 0x8F041A3940a5e6FB580075C3774E15FcFA0E1618 No price feed