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

Set trading fees to 1% on LPL-BNT pool from current .1%

Voting ended about 4 years agoSucceeded

TLDR

  • This proposal seeks to increase the pool fees from .1% to 1% on the LPL-BNT pool. We have the largest amount of liquidity for this token by far (~23 times as much as the next largest pool) and can earn more profits for LPs by doing so. This would be to the detriment of arb bots that are otherwise profiting from the low fees on this pool ATM.

For

  1. A higher conversion fee will bring in more trading fees for this pool and be more profitable for LPL LPs.

Against

  1. We should not increase the pool fees

Abstract There are currently ~110K $BNT and ~71.3K $LPL tokens in the BNT-LPL pool. This has resulted in a pool that has roughly ~800K in liquidity. This proposal seeks to increase the pool fees from .1% to 1% as we have the largest amount of liquidity for this token by far (~23 times as much as the next largest pool on Uniswap V3)

image|479x297

Motivation

The second-largest pool for LPL is on Uniswap V3 and it is paired with ETH. Pool depth is roughly 38K and fees are set at 1%:

image|279x500

There is also a much smaller size pool on Uniswap V2 with 20K in liquidity:

image|399x500

This pool shares some similarities to the TRACstrong text pool in which we have the largest amount of liquidity for a specific token. This means that the observations which we will gather from the following fee change schedule:

https://gov.bancor.network/t/proposal-trac-bnt-fee-change-schedule-and-performance-analysis/3239

might prove to be useful for this pool in the future. From my personal observations and experience, having a 1% fee for this pool is reasonable for this token given the liquidity depth and also because we would be at the same conversation fee as Uniswap V3 as well.

Off-Chain Vote

For
5.53M 100%
Against
2.67K 0%
Abstain
0 0%
Download mobile app to vote

Timeline

Dec 26, 2021Proposal created
Dec 26, 2021Proposal vote started
Dec 29, 2021Proposal vote ended
Oct 26, 2023Proposal updated