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

Increase the trading liquidity limit in the THALES-BNT pool to 200k

Voting ended almost 4 years agoSucceeded

Increase the trading liquidity limit in the THALES pool from 100k BNT to 200k BNT

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

TL;DR

  • THALES is already whitelisted for 100k BNT

  • That pool was filled by Thales DAO as soon as the proposal has passed

  • Thales governance already expressed willingness to fill the THALES side with the doubled limit

  • I am proposing to double the liquidity limit as there is no capacity remaining:

image

  • 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 200k BNT.
  • THALES’s DAO will fill ANY remaining liquidity balance with their treasury up to 200k BNT. If more space becomes available, another proposal will be made to THALES’s governance to approve filling any remaining liquidity.

Rationale

The deepest THALES pools are:

The THALES/WETH 0.3% Uniswap V3 Pool on Optimism with ~$711K liquidity and $55k Daily volume [1]

A trading liquidity limit of 200k BNT opens up space for an additional 100k BNT of capacity and roughly $130k of single-sided staking capacity with BNT at $1.30. If the pool is filled completely it will be roughly $520k in depth (with BNT at $1.30) and a proposal to increase the trading liquidity limit will be considered then.

THALES token address: 0x8947da500eb47f82df21143d0c01a29862a8c3c5

Project Website: https://thalesmarket.io/

All other details are applicable as in the original whitelisting proposal

Off-Chain Vote

For
3.6M vBNT61.7%
Against
1.41K vBNT0%
Abstain
2.24M vBNT38.3%
Download mobile app to vote

Discussion

BancorIncrease the trading liquidity limit in the THALES-BNT pool to 200k

Timeline

May 29, 2022Proposal created
May 29, 2022Proposal vote started
Jun 01, 2022Proposal vote ended
Oct 26, 2023Proposal updated