Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce a tax/fee on inactive pools and stale gauges to remove trapped tokens #4898

Closed
daniel-farina opened this issue Apr 12, 2023 · 1 comment

Comments

@daniel-farina
Copy link
Contributor

Background

The current system has numerous inactive pools and stale gauges with tiny amounts of tokens trapped in them. This creates difficulties in routing and filtering for the users. Additionally, nearly all gauges cannot completely distribute all their tokens due to indivisibility, leaving some amount trapped in them. A proposal has been suggested to introduce some kind of tax/fee on inactive pools and stale gauges to have their tokens completely removed and resolve these issues.

Suggested Design

The suggested design for this proposal is to introduce a tax/fee on inactive pools and stale gauges over time. This will allow us to reduce or eliminate the initial creation fees and help clean up inactive pools and stale gauges. The fee will incentivize users to close their pools and gauges, which will reduce unnecessary data and improve routing efficiency. Additionally, this proposal will help remove trapped tokens and free up space for other users.

Acceptance Criteria

The tax/fee system should be implemented in a way that is fair and incentivizes users to close inactive pools and stale gauges.
The tax/fee should be introduced over time to allow for the reduction or elimination of initial creation fees.
The system should effectively remove trapped tokens and clean up inactive pools and stale gauges.
The proposal should improve routing efficiency and reduce unnecessary data.

@p0mvn
Copy link
Member

p0mvn commented Apr 12, 2023

Added to #4700, will unassign me for now in case someone else has capacity to pick this up

@p0mvn p0mvn removed their assignment Apr 12, 2023
@github-project-automation github-project-automation bot moved this from Todo 🕒 to Done ✅ in Osmosis Chain Development Apr 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

3 participants