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

Proposal to increase trading liquidity limit in the FODL pool from 100k BNT to 250k BNT

Voting ended about 4 years agoSucceeded

Proposal to increase the trading liquidity limit in the FODL pool from 100k BNT to 250k BNT

For this proposal to pass, it requires a 35% quorum and 66.7% supermajority.

This proposal is expected to appear on Snapshot for voting on [date=2022-03-13 timezone="Europe/London"]. Make sure to stake your vBNT for voting before this date and time to participate in the DAO decision.

TL;DR

  • The FODL pool has recently been whitelisted .
  • A suggestion from @glenn to increase the trading liquidity limit from 100k to 250k in the whitelisting thread was made.
  • The FODL liquidity on other decentralised exchanges justifies proposing an increase.
  • Increasing the pool’s liquidity will improve price impact and help direct more volume to Bancor.
  • This proposal seeks to increase the trading liquidity limit in the pool from 100k BNT to 250k BNT.

Rationale

The FODL pools with deepest liquidity in Ethereum DEXes are:

The FODL/USDC 0.3% SushiSwap pool with $7,281,625.00 liquidity, and $205,978.89 daily volume [1].

The FODL/WETH 0.3% SushiSwap pool with $6,230,332.17 liquidity, and $177,020.27 daily volume [2].

The extra liquidity would bring the total pool liquidity to at least ~$1.35m, if the space in the pool is filled. If full, the Bancor FODL pool would only have 18.47% of the liquidity in the FODL/USDC Sushiswap pool. Therefore, if it happens, a proposal to increase the trading liquidity limit again should be considered.

FOR

Increase trading liquidity in the FODL pool from 100k BNT to 250k BNT.

AGAINST

Keep the trading liquidity in the FODL pool at 100k BNT.

[1] FODL-USDC | SushiSwap Analytics

[2] FODL-WETH | SushiSwap Analytics

Off-Chain Vote

For
5.52M 73.1%
Against
2.05K 0%
Abstain
2.03M 26.9%
Download mobile app to vote

Timeline

Mar 14, 2022Proposal created
Mar 14, 2022Proposal vote started
Mar 17, 2022Proposal vote ended
Oct 26, 2023Proposal updated