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

How to list in omnipool and manage deposits over XCM #189

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

spazcoin
Copy link
Contributor

  1. define the requirements for listing a new token in the Omnipool. Be specific about requirements.
  2. explain 5% Omnipool TVL caps as well as 5% add/remove liquidity limits.
  3. explain the process to remotely deposit/withdraw liquidity from parachain governance (should this be a separate page?)

from the last time I ran through these scripts
and how to manage Omnipool liquidity deposits remotely over XCM
@spazcoin spazcoin force-pushed the howToListInOmnipool branch 2 times, most recently from 846c26b to d52f99a Compare May 25, 2024 18:16
updates after initial council discussion:
* increase price discovery time to 8 months
* clearly explain how Hydration governance will vote on token listing.

The situation of tokens without a treasury was discussed but no good
solution decided and therefore it is left to tokenholder discussion
and evaluation on a case-by-case basis in the future.
moved the "exception" up to the beginning of the Prerequisites section
using the following more explicit statement from amphibiousparakeet:
> The actual decision lies with HDX token holders who may still reject
> a token that meets all criteria and may accept a token that does not.
@spazcoin
Copy link
Contributor Author

The Omnipool Listing Requirements in this PR were ratified by Hydration governance in https://hydration.subsquare.io/democracy/referenda/152

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant