BAL Whitelist Modifications for Week 44

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

First, I would like to propose adding the following new token to the whitelist, with an important caveat: this is a rebasing token. Therefore, normal pools are prone to being gulp-attacked on rebases. But this token does come with a list of known Balancer pools which get atomically gulped on each rebase, thereby preventing gulp-attacks. Only officially sanctioned pools will be included in liquidity mining. At time of writing, there are two such pools, and their addresses are listed below. This is very similar to our treatment of AMPL (Ampleforth).

ADD		MARK			0x67c597624B17b16fb77959217360B7cD18284253
only for pools:			0x049C586132110F6551D758deB50A7c984FC0EC59

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

ADD		ACE				0x06147110022B768BA8F99A8f385df11a151A9cc8
ADD		DEXTF			0x5F64Ab1544D28732F0A24F4713c2C8ec0dA089f0
ADD		DG				0x53C8395465A84955c95159814461466053DedEDE
ADD		DORA			0xbc4171f45EF0EF66E76F979dF021a34B46DCc81d
ADD		pxUSD_MAR2022	0x4B606e9Eb2228c70f44453AFe5a73e1FeA258Ce1
ADD		stETH			0xae7ab96520DE3A18E5e111B5EaAb095312D7fE84
ADD		SWFL			0xBa21Ef4c9f433Ede00badEFcC2754B8E74bd538A
ADD		SYNC			0xB6ff96B8A8d214544Ca0dBc9B33f7AD6503eFD32
ADD		TEAM			0x1c79ab32C66aCAa1e9E81952B8AAa581B43e54E7
ADD		XEND			0xE4CFE9eAa8Cdb0942A80B7bC68fD8Ab0F6D44903
ADD		YD-BTC-JUN21	0x4b7Fb448dF91C8Ed973494F8C8c4f12DAF3A8521
ADD		YD-ETH-JUN21	0xcBE430927370e95B4B10cFc702c6017EC7abEfC3

The proposed changes will go into effect at 00:00 UTC on Monday, March 29. 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	pxUSD_MAR2022	<->	USD group
SOFT	stETH			<->	ETH group
SOFT	YD-BTC-JUN21	<->	USD group
SOFT	YD-ETH-JUN21	<->	USD group


No requested tokens were omitted this week.


I screwed up again, just like last week. This comment is an amendment to the list to correct my mistake. Once again, I missed an LBP token, and the sale begins later today so eligibility hasn’t been a factor yet. Nothing retroactive here. I knew about this token but forgot to include it in the list above as I was racing to reconcile all the others. Sincerest apologies.

ADD		ILV		0x767FE9EDC9E0dF98E07454847909b5E959D7ca0E