BAL Whitelist - Round 23

On behalf of the Balancer community, I’d like to propose the following modifications to the token whitelist used for BAL governance distribution. As a reminder, these whitelist proposals are now pre-approved on objective technical criteria only, so they are not subject to community vote. All new tokens will be placed at cap1 for liquidity mining, meaning each token’s measured BAL-eligible liquidity is scaled to a maximum of $1M (at time of writing). At any time, community members may propose to increase a token’s cap to the next tier. For reference, please see the previous proposals which detail the motivation for creation of the whitelist and define the list of tokens used to date. Links are included at the end of this post.

Proposed Modifications

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

    ADD		L2			0xBbff34E47E559ef680067a6B1c980639EEb64D24
    ADD		PRQ			0x362bc847A3a9637d3af6624EeC853618a43ed7D2
    ADD		TRU			0x4C19596f5aAfF459fA38B0f7eD92F11AE6543784
    ADD		WZEC		0x4A64515E5E1d1073e83f30cB97BEd20400b66E10
    ADD		xAAVEa		0x80DC468671316E50D4E9023D3db38D3105c1C146
    ADD		xAAVEb		0x704De5696dF237c5B9ba0De9ba7e0C63dA8eA0Df

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

There are no new pegs introduced this week.


Some requested tokens were omitted this week.

The following token exhibits ERC-223 transfer() behavior which reverts all transfers to non-ERC-223 smart contracts. This will break the Balancer exchange proxy, which does not implement the ERC-223 standard but does expect transferability between contracts. This is a violation of Whitelist Criterion #3: The token’s transfer() and transferFrom() implementations must exhibit the expected behavior - namely, transferring N tokens from one address to another.

    BAD TRANSFER	`c	0xe324C8cF74899461Ef7aD2c3EB952DA7819aabc5

Reference: Prior Proposals