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

Proposal: Approve BAND, SAO, JRT, SRM, CEL, KNC and RUNE pools with funding limit of 0 in V3

Voting ended over 3 years agoSucceeded

This proposal is expected to appear on Snapshot for voting on [date=2022-07-17 time=15:00:00 timezone="UTC"]. Make sure to stake your vBNT for voting before this date and time to participate in the DAO decision.

To pass, this needs 35% Quorum and 66.7% FOR

TLDR:

  • Bancor V3 went live with over 100 tokens https://blog.bancor.network/100-tokens-go-live-on-bancor-3-e2a4e0f19c46
  • As noted in that post "The results of this security review are provided to allow the DAO to separately consider 9 tokens from the approved v2.1 whitelist. The tokens proposed for additional deliberation are: USDT, OCEAN, SAO, JRT, BAND, BUSD, sBTC, SRM, sUSD."
  • All of these token were individually voted on by the BancorDAO - OCEAN and USDT were voted in.
  • RUNE, KNC and CEL were voted to have deposits disabled in previous votes. This proposal is suggested to allow them on V3 with a funding limit of 0 to allow for migrations.

Current Liquidity (at time of writing) of the 7 pool that were not voted into V3

sUSD - 0 BAND - $123 SAO - $113,964 BUSD - 0 JRT - $89,645 SRM - $5,585 sBTC - 0

This proposal seeks to create V3 pools for BAND, SAO, JRT and SRM with a funding limit (a.k.a trading liquidity) of 0.

This proposal also seeks to provide support for the migration of RUNE, KNC and CEL to V3 but set the funding limit to 0.

I am not using the terms "whitelisting" as these would all have a funding limit of 0.

FOR Create V3 pools for BAND, SAO, JRT, SRM, RUNE, KNC and CEL with a funding limit (a.k.a trading liquidity) of 0.

AGAINST Take no action

Off-Chain Vote

For
3.68M vBNT62.3%
Against
3.03K vBNT0.1%
Abstain
2.22M vBNT37.6%
Download mobile app to vote

Discussion

BancorProposal: Approve BAND, SAO, JRT, SRM, CEL, KNC and RUNE pools with funding limit of 0 in V3

Timeline

Jul 17, 2022Proposal created
Jul 17, 2022Proposal vote started
Jul 20, 2022Proposal vote ended
Oct 26, 2023Proposal updated