BAL Whitelist Modifications for Week 42

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.

Proposed Modifications

I would like to propose adding the following new tokens to the whitelist:

ADD		KINE	0xCbfef8fdd706cde6F208460f2Bf39Aa9c785F05D
ADD		mBTC	0x945Facb997494CC2570096c74b5F66A3507330a1

The proposed changes will go into effect at 00:00 UTC on Monday, March 15. 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 wrapFactor proposal.

SOFT	mBTC	<->	BTC group


Some requested tokens were omitted this week.

The following token lacks a price feed via the CoinGecko API, which means it can be listed on the UI but is 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	VISR	0xf62dfF6d13B8AC6f7707335b4D936a2Ca5e16D04	No price feed