BAL Whitelist - Round 13

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:

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

Proposed Modifications

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

    ADD		BUSD	0x4Fabb145d64652a948d72533023f6E7A623C7C53
    ADD		DHT		0xca1207647Ff814039530D7d35df0e1Dd2e91Fa84
    ADD		DPI		0x1494CA1F11D487c2bBe4543E90080AeBa4BA3C2b
    ADD		DUSD	0x5BC25f649fc4e26069dDF4cF4010F9f706c23831
    ADD		FRONT	0xf8C3527CC04340b208C854E985240c02F7B7793f
    ADD		GHST	0x3F382DbD960E3a9bbCeaE22651E88158d2791550
    ADD		HGET	0x7968bc6a03017eA2de509AAA816F163Db0f35148
    ADD		LINA	0x3E9BC21C9b189C09dF3eF1B824798658d5011937
    ADD		ONE		0x4D807509aECe24C0fa5A102b6a3B059Ec6E14392
    ADD		PCT		0xbc16da9df0A22f01A16BC0620a27e7D6d6488550
    ADD		POWER	0xF2f9A7e93f845b3ce154EfbeB64fB9346FCCE509
    ADD		SAFE	0x1Aa61c196E76805fcBe394eA00e4fFCEd24FC469
    ADD		UNI		0x1f9840a85d5aF5bf1D1762F925BDADdC4201F984

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

    SOFT	BUSD	USD group
    HARD	BUSD	aBUSD
    SOFT	DUSD	USD group

Omissions

The following tokens lack price feeds on CoinGecko, which violates Whitelist Criteria #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. 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.

    NO PRICE FEED	AGA		0x2D80f5F5328FdcB6ECeb7Cacf5DD8AEDaEC94e20
    NO PRICE FEED	ORTC	0x0b11D5d078955C6E5913beEaba85660202A4FC55
    NO PRICE FEED	TMH		0xe6Db41A000916fa272787348d87Dcb51cb8a9a48
1 Like