BAL Whitelist Modifications for Week 33

Note: For some time, there has been a discrepancy between the numbering conventions of whitelist proposals and liquidity mining periods. This is needlessly confusing, so with this proposal we are closing the gap. The previous proposal was for Whitelist Round 28, which corresponded to Week 32 of $BAL Liquidity Mining. So this proposal would have been Round 29, but we are simply calling it Week 33, and moving forward the proposals will follow this convention.

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.

Proposed Modifications

The following token has undergone a contract migration. I propose modifying the existing whitelist entry for this token so that it points to the new contract address. The existing cap will be preserved, and the old address will no longer participate in liquidity mining.

    MODIFY	COVER	0x5D8d9F5b96f4438195BE9b99eee6118Ed4304286	->	0x4688a8b1F292FDaB17E9a90c8Bc379dC1DBd8713

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

    ADD		COMBO	0xfFffFffF2ba8F66D4e51811C5190992176930278
    ADD		LDO		0x5A98FcBEA516Cf06857215779Fd812CA3beF1B32
    ADD		NFTX	0x87d73E916D7057945c9BcD8cdd94e42A6F47f776
    ADD		WSTA	0xeDEec5691f23E4914cF0183A4196bBEb30d027a0

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

There are no new price pegs introduced this week.


No requested tokens were omitted this week.