BAL Whitelist - Round 21

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		ABYSS	0x0E8d6b471e332F140e7d9dbB99E5E3822F728DA6
    ADD		ALBT	0x00a8b738E453fFd858a7edf03bcCfe20412f0Eb0
    ADD		AUDIO	0x18aAA7115705e8be94bfFEBDE57Af9BFc265B998
    ADD		COIN	0x87b008E57F640D94Ee44Fd893F0323AF933F9195
    ADD		FNX		0xeF9Cd7882c067686691B6fF49e650b43AFBBCC6B
    ADD		FWB		0x7d91e637589EC3Bb54D8213a9e92Dc6E8D12da91
    ADD		JAMM	0x56687cf29Ac9751Ce2a4E764680B6aD7E668942e
    ADD		SOCKS	0x23B608675a2B2fB1890d3ABBd85c5775c51691d5
    ADD		WOO		0x4691937a7508860F876c9c0a2a617E7d9E945D4B

The proposed changes will go into effect at 00:00 UTC on Monday, November 16. 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 price pegs introduced this week.

Omissions

Some requested tokens were omitted this week.

The following tokens have possible rebasing mechanisms. It looks like OUSD at least has a non-rebasing option which is automatic for smart contracts, but I would need to know more about this mechanism as rebasing is dangerous for Balancer pools. I will be reaching out to the teams to gather more information. For now, these violate Whitelist Criterion #5: The token must not be vulnerable to the so-called "gulp() attack," which is exposed when a pool’s token balance changes unbeknownst to the pool. For now, known cases include tokens that charge a transfer fee and tokens that periodically rebase.

    PENDING: REBASE?	OUSD	0x2A8e1E676Ec238d8A992307B495b45B3fEAa5e86
    PENDING: REBASE?	VLO		0x98ad9B32dD10f8D8486927D846D4Df8BAf39Abe2

The following token lacks a price feed through the CoinGecko API, which violates Whitelist Criterion #7: The token must have a price feed accessible via CoinGecko’s API. This is instrumental to calculating a pool’s eligibility for BAL rewards.

    NO PRICE FEED		WZEC	0x4A64515E5E1d1073e83f30cB97BEd20400b66E10

Reference: Prior Proposals

https://forum.balancer.finance/t/proposing-the-token-whitelist-for-bal-distribution
https://forum.balancer.finance/t/bal-whitelist-round-2
https://forum.balancer.finance/t/bal-whitelist-round-3
https://forum.balancer.finance/t/bal-whitelist-round-4
https://forum.balancer.finance/t/bal-whitelist-round-5
https://forum.balancer.finance/t/bal-whitelist-round-6
https://forum.balancer.finance/t/bal-whitelist-round-7
https://forum.balancer.finance/t/bal-whitelist-round-8
https://forum.balancer.finance/t/proposal-to-update-the-whitelist-process
https://forum.balancer.finance/t/bal-whitelist-round-9
https://forum.balancer.finance/t/bal-whitelist-round-10
https://forum.balancer.finance/t/bal-whitelist-round-11
https://forum.balancer.finance/t/bal-whitelist-round-12
https://forum.balancer.finance/t/bal-whitelist-round-13
https://forum.balancer.finance/t/bal-whitelist-round-14
https://forum.balancer.finance/t/bal-whitelist-round-15
https://forum.balancer.finance/t/bal-whitelist-round-16
https://forum.balancer.finance/t/bal-whitelist-round-17
https://forum.balancer.finance/t/bal-whitelist-round-18
https://forum.balancer.finance/t/bal-whitelist-round-19
https://forum.balancer.finance/t/bal-whitelist-round-20

Can zHegic be squeezed onto this list? --> 0x837010619aeb2ae24141605afc8f66577f6fb2e7

Weird things to know about:
zHegic is a tokenized representation of a pool of Hegic tokens that accrues more Hegic overtime.
Hegic is already whitelisted
zHegic is non-deflationary

New tokens can only be added once a week in batches. After 00:00 UTC on Monday, it’s too late to get any new tokens into a batch. I’ll add zHEGIC to the list for consideration next week, though. Thanks!

Okay great :ok_hand: thank you

1 Like