• © Goverland Inc. 2026
  • v1.0.8
  • Privacy Policy
  • Terms of Use
BancorBancorby0xc26892F608B3E97A24149F9C273449416e222060definavigator.eth

Proposal to Determine Whitelisting Status of sUSD on Bancor V3

Voting ended almost 4 years agoSucceeded

TL;DR

  • BIP17 allowed for the migration of all active V2.1 pools to V3
  • The DAO’s whitelisting requirements are here
  • 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 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 sUSD
  • sUSD’s token contract allows for burning of sUSD from any account, including the token vault contract on Bancor V3.
  • Link to contract: https://etherscan.io/token/0x57Ab1ec28D129707052df4dF418D58a2D46d5f51

Voting Instructions:

To whitelist sUSD on Bancor V3, vote FOR this proposal

To do nothing, vote AGAINST this proposal

Off-Chain Vote

For
2.2M vBNT34.4%
Against
1.79M vBNT28%
Abstain
2.4M vBNT37.6%
Download mobile app to vote

Discussion

BancorProposal to Determine Whitelisting Status of sUSD on Bancor V3

Timeline

Jun 19, 2022Proposal created
Jun 19, 2022Proposal vote started
Jun 22, 2022Proposal vote ended
Oct 26, 2023Proposal updated