BAL Whitelist Modifications for Week 54

For the first time ever, there aren’t any new tokens being added to the whitelist this week. But for the sake of process consistency and transparency, I am including the full proposal template and disclosing two suggested tokens that did not fulfill all the criteria for listing. One of them is incompatible, and the other will be added to the UI but is ineligible for liquidity mining until a price feed becomes available.

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:

There are no new tokens being added this week.

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

There are no new price pegs introduced this week.


Some requested tokens were omitted this week.

The following token possesses two mechanisms which are fundamentally incompatible with Balancer: a transfer fee and a rebasing supply. This violates Whitelist Criterion #3: The token’s transfer() and 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.

OMIT	eMax	0x15874d65e649880c2614e7a480cb7c9A55787FF6	Transfer fee AND rebase

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	VUSD	0x677ddbd918637E5F2c79e164D402454dE7dA8619	No price feed