# Proposal to Determine Whitelisting Status of SAO on Bancor V3

**URL:** <https://gov.bancor.network/t/proposal-to-determine-whitelisting-status-of-sao-on-bancor-v3/3674>\
**Category:** DAO Archive (SUBMITTED)\
**Created:** [June 14, 2022, 12:55pm UTC](https://gov.bancor.network/t/proposal-to-determine-whitelisting-status-of-sao-on-bancor-v3/3674 "2022-06-14T12:55:08Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![foxsteven](https://avatars.discourse-cdn.com/v4/letter/f/838e76/32.png) [@foxsteven](https://gov.bancor.network/u/foxsteven)\
**Post date:** [June 14, 2022, 12:55pm UTC](https://gov.bancor.network/t/proposal-to-determine-whitelisting-status-of-sao-on-bancor-v3/3674/1 "2022-06-14T12:55:08Z")

</div>

This proposal is expected to appear on Snapshot for voting on June 19, 2022 (Lisbon) . Make sure to stake your vBNT for voting before this date and time to participate in the DAO decision. To pass, this proposal needs a quorum of 35% and 66.7% FOR votes.

TL;DR

- [BIP17](https://snapshot.org/#/bancornetwork.eth/proposal/0xb4dbbc5edb107d03bc43ebc23f37e996a3a04cb85ae6de2fbfe4860281e3987f) allowed for the migration of all active V2.1 pools to V3
- The DAO’s whitelisting requirements are [here](https://docs.bancor.network/about-bancor-network/token-whitelisting-requirements)
- There are certain cases in which tokens were whitelisted before these requirements were in place.
- This proposal is for the DAO to vote specifically on some of these pools where the token contract may add significant risk.
- NOTE: These exceptions are only possible for tokens that were whitelisted in V2.1.
- Other tokens that were not whitelisted on V2.1 have no such exemptions as they were not live on Bancor before the whitelisting requirements were in place.

Summary:

- As outlined in the recent [blog post](https://blog.bancor.network/100-tokens-go-live-on-bancor-3-e2a4e0f19c46) there are 9 tokens that will be each brought up specifically for the DAO to vote on a white listing in V3.
- This proposal is for SAO
- SAO’s token contract allows the contract owner to burn tokens in any address, including the token vault contract of Bancor 3.
- Link to contract: [Sator: SAO Token | Address 0x3ef389f264e07fff3106a3926f2a166d1393086f | Etherscan](https://etherscan.io/address/0x3ef389f264e07fff3106a3926f2a166d1393086f)

Voting Instructions:

To whitelist SAO on Bancor V3, vote FOR this proposal

To do nothing, vote AGAINST this proposal

---

<div class="post-metadata">

**Author:** ![glenn](https://dub1.discourse-cdn.com/flex013/user_avatar/gov.bancor.network/glenn/32/1720_2.png) [@glenn](https://gov.bancor.network/u/glenn)\
**Post date:** [June 18, 2022, 7:53pm UTC](https://gov.bancor.network/t/proposal-to-determine-whitelisting-status-of-sao-on-bancor-v3/3674/2 "2022-06-18T19:53:49Z")

</div>

> [@foxsteven](#):
>
> SAO’s token contract allows the contract owner to burn tokens in any address, including the token vault contract of Bancor 3.

Just want to note here that this token has been bridged via the wormhole. All wormhole tokens behave this way and it is not specific to SAO. That is, they all have the owner set to the wormhole bridge:

> **[Wormhole: Portal Token Bridge | Address...](https://etherscan.io/address/0x3ee18b2214aff97000d974cf647e7c347e8fa585)**
>
> The Contract Address 0x3ee18b2214aff97000d974cf647e7c347e8fa585 page allows users to view the source code, transactions, balances, and analytics for the contract address. Users can also interact and make transactions to the contract directly on...

You can verify this with another token such as Wormhole USDT, Wormhole USDC, etc…

> **[Wormhole: USDTbs Token | Address 0xde60adfddaabaaac3dafa57b26acc91cb63728c4 |...](https://etherscan.io/address/0xde60adfddaabaaac3dafa57b26acc91cb63728c4#readProxyContract)**
>
> The Contract Address 0xde60adfddaabaaac3dafa57b26acc91cb63728c4 page allows users to view the source code, transactions, balances, and analytics for the contract address. Users can also interact and make transactions to the contract directly on...

Essentially, if another token from Solana is bridged over to Ethereum then it will also have the same properties (not something that is specifically being done by the team).

There are few teams (mean finance ATM but other NFT projects as well) on Solana that are very interested in building up liquidity on mainnet Ethereum (and more will come) and in my opinion, we should look at the merits of these projects and their trustworthiness in addition to any potential security concerns that are out of their control (technically, some of these teams can launch a native ERC 20 token on Ethereum but a lot of them are not native to Ethereum in the first place).

If the Bancor DAO does decide that we don’t want to allow **any** wormhole bridge tokens, then we are closing ourselves to a large set of legitimate projects that are building on Solana. In my opinion I don’t think this is the right path to take.

---

<div class="post-metadata">

**Author:** ![glenn](https://dub1.discourse-cdn.com/flex013/user_avatar/gov.bancor.network/glenn/32/1720_2.png) [@glenn](https://gov.bancor.network/u/glenn)\
**Post date:** [June 19, 2022, 2:48pm UTC](https://gov.bancor.network/t/proposal-to-determine-whitelisting-status-of-sao-on-bancor-v3/3674/3 "2022-06-19T14:48:19Z")

</div>

Adding the latest onboarding proposal for anyone that might have questions about the project:

> [@Proposal: Onboard Sator (SAO) token](https://gov.bancor.network/t/proposal-onboard-sator-sao-token/3246):
>
> For this proposal to pass, it requires 35% quorum and 66.7% supermajority. This proposal is expected to appear on Snapshot for voting on 2021-12-19T17:00:00Z (UTC). Make sure to stake your vBNT for voting before this date and time to participate in the DAO decision. TL;DR • Proposal to whitelist Sator token • Sator is a social utility token powering our next generation content engagement metaverse • There are no apparent security concerns that would prohibit whitelist status • Proposing 10…
