Currently, there are two types of tokens tradeable on SaucerSwap: whitelisted tokens that appear in the default menus and analytics, and all other HTS tokens, which are imported into token menus in a fully permissionless manner. There are some pain points associated with this current method of verification. For example, projects must complete a Sentinel report, fill out a token listing request form, wait for the community to vote on their token, and finally, meet a liquidity requirement. This is not a good fit for all projects, and as such, three new classes of tokens are being introduced:
1. Default
Characteristics:
- Appears in default menusi. No disclaimer
- Appears in analyticsi. No disclaimer
- Listing announcement from SaucerSwap on Twitter
- Eligible for listing on data aggregators (CoinGecko, CMC)
- Price APIi. Token price displays in HashPack and other applications
Criteria:
- HeadStarter Sentinel report
- SaucerSwap request form
- Passing community vote (>50%)
- Minimum $10k token liquidity
2. Extended
Characteristics:
- Appears in default menusi. User prompted with “Caution” disclaimer
- Appears in analyticsi. User prompted with “Caution” disclaimer
- Eligible for listing on data aggregators (CoinGecko, CMC)
- Price APIi. Token price displays in HashPack and other applications
Criteria:
- SaucerSwap request formi. Listing ETA is 48 hours
3. Experimental
Characteristics:
- Does not appear in default menusi. Tokens must be imported by ID (e.g., 0.0.123456)ii. User prompted with “Warning” disclaimer
- Does not appear in analytics
- Price APIi. Token price displays in HashPack and other applications
Criteria:
- No criteria; any HTS token can be imported, used to create a liquidity pool, and traded.
In addition to this amended token listing procedure, projects can apply for yield farms after their token has been added to either the default or extended list. There will be a limit to how many farms a given token can receive, with this number generally being capped at two. A project can submit a new request form if it has one or more farms and wishes to incentivize an additional token pair. Once the SaucerSwap team has received a form, the decision will be brought to a community vote in the same manner as token listings. Note that the token must have a reasonable amount of liquidity and sustained trading volume for it to be considered for a farm. This is to ensure there is organic demand for the token without additional incentives. Liquidity and volume will be assessed on a case-by-case basis. All yield farms will receive dual token emissions (SAUCE and HBAR). Farm weights and initial listings will vary per project and will be governed via DAO-based token-weighted voting once it is phased in.
For collaboration, token listing, and farm inquiries, please complete the following request form:
Link to form: https://z30ev00547x.typeform.com/to/YBGqwGup
Summary
The addition of SaucerSwap’s Extended List removes the need for a Sentinel report, liquidity requirement, or community vote. As such, getting a token listed on SaucerSwap will have significantly less friction and be much quicker. This allows for a more permissionless nature of our DEX while embracing the previously established, more stringent process for tokens in our Default List. Please note that because of the single-sided staking rollout, we have a backlog of requests, which will be processed in the order they were received.
