# BAL Whitelist Modifications for Week 50

**URL:** <https://forum.balancer.fi/t/bal-whitelist-modifications-for-week-50/1873>\
**Category:** Liquidity Mining \[deprecated\]\
**Created:** [May 9, 2021, 10:43pm UTC](https://forum.balancer.fi/t/bal-whitelist-modifications-for-week-50/1873 "2021-05-09T22:43:34Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![rabmarut](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.balancer.fi/rabmarut/32/55_2.png) [@rabmarut](https://forum.balancer.fi/u/rabmarut)\
**Post date:** [May 9, 2021, 10:43pm UTC](https://forum.balancer.fi/t/bal-whitelist-modifications-for-week-50/1873/1 "2021-05-09T22:43:34Z")

</div>

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](https://forum.balancer.fi/t/proposal-to-update-the-whitelist-process/217). 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](https://discord.gg/ARJWaeF). 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](https://docs.balancer.finance/core-concepts/bal-liquidity-mining/exchange-and-reward-listing).

For reference, the active whitelist can be found [here](https://github.com/balancer-labs/assets/blob/master/lists/eligible.json). 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](https://forum.balancer.fi/t/proposing-the-token-whitelist-for-bal-distribution) for creating the whitelist.

# Proposed Modifications

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

```
ADD GDT 0xc67B12049c2D0CF6e476BC64c7F82fc6C63cFFc5
ADD NFTFY	0xBf6Ff49FfD3d104302Ef0AB0F10f5a84324c091c
ADD OIL 0x0275E1001e293C46CFe158B3702AADe0B99f88a5
ADD sAMZN	0x9CF7E61853ea30A41b02169391b393B901eac457
ADD sFB 0xf50B5e535F62a56A9BD2d8e2434204E726c027Fa
ADD sGOOG	0xC63B8ECCE56aB9C46184eC6aB85e4771fEa4c8AD
ADD sNFLX	0x5A7E3c07604EB515C16b36cd51906a65f021F609

```

The proposed changes will go into effect at 00:00 UTC on Monday, May 10. 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](https://forum.balancer.fi/t/modifying-wrapfactor-applying-a-0-7-factor-to-soft-pegged-pairs/108).

There are no new price pegs introduced this week.

# Omissions

Some requested tokens were omitted this week.

The following token does not return a boolean on `transfer()`, which is a violation of Whitelist Criterion #2: _The token must conform to the ERC-20 interface described in EIP-20. Namely, the functions `transfer()`, `transferFrom()`, and `approve()` must return booleans._

```
OMIT	XYO 0x55296f69f40Ea6d20E478533C15A6B08B654E758	Bad transfer

```
