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 CUDOS 0x817bbDbC3e8A1204f3691d14bB44992841e3dB35 ADD DEFI++ 0x8D1ce361eb68e9E05573443C407D4A3Bed23B033
The proposed changes will go into effect at 00:00 UTC on Monday, February 1. Pools containing newly whitelisted tokens will begin to accrue BAL beginning at 00:00 UTC on Monday; but they may not appear on the Balancer pools UI with symbol/logo until a few days later. 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
There are no new price pegs introduced this week.
Some requested tokens were omitted this week.
The following token lacks a price feed 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 mining. Because it has been vetted and deemed safe for use within Balancer, it will be added to the UI only and reevaluated for liquidity mining eligibility once the price feed is established.
OMIT xHDX 0x6FCb6408499a7c0f242E32D77EB51fFa1dD28a7E No price feed