# Token Listing Guide
Principle Requirements * **Development Completion:** The core functionality of the project must be fully developed and the code open-sourced. * **Whitepaper Disclosure:** The project’s whitepaper, detailing the economic model of the token, must be publicly accessible. * **Controller Assignment:** The token’s control must be vested in a DAO contract, or its controllers removed, to avert malicious modifications or issuance. * **Standard Compliance:** Tokens must conform to either the ICRC1 or DRC20 standards. * **Transaction Transparency:** Adherence to the DRC202 standard or implementation of the `get_transactions` query method (according to the SNS ICRC1 specification) is required for transparent transaction records. * **Additional Conditions for DeFi Projects:** Require the submission of an audit report conducted by a reputable security firm. Transition the DApp’s controller to a DAO or SNS. *Non-compliance may trigger delisting proposals by the ICLighthouse community.*
Listing Procedure on ICDex To list, navigate to , select “+ Token Listing”, and allocate 5,000 ICL (adjustable) to establish a trading pair.
Promoting Your Trading Pair ### 1. Introduction to Pair Score Pair Score serves as ICDex’s proprietary evaluation mechanism for trading pairs, assessing factors such as sponsorship, liquidity, and trading volume. A superior Pair Score elevates a pair’s listing position, enhancing visibility among traders. Trading pairs are stratified into three categories based on their Pair Score: * **TOP** (MAIN Pairings): Signifies extensive trader engagement. * **RISING** (Rising Parings): Indicates moderate trader participation. * **HIGH RISK** (Higher Risk Pairings): Reflects limited engagement and heightened risks. **Upgrade Criteria** Trading pairs on ICDex are systematically classified based on their Pair Score, which influences their visibility and accessibility to traders. Initially, all new trading pairs are assigned to **THIRD (STAGE0)**, indicating the starting level. Progression through the levels is determined as follows: * **To SECOND (STAGE1)**: A trading pair must achieve a Pair Score of 20 or higher. * **To MAIN (STAGE2)**: A trading pair needs to maintain a Pair Score of 60 or above for a minimum duration of one month. **Downgrade Criteria** To maintain the integrity and competitiveness of the trading environment, trading pairs are subject to downgrade if their performance declines: * **From MAIN to SECOND:** If a pair’s score falls below 50 and remains there for over three months. * **From SECOND to THIRD:** Should a pair’s score drop below 15 and stay there for more than three months. **Sponsorship Rules** ICLighthouse **URANUS NFT holders**, acting as listing referrers, play a pivotal role in influencing the Pair Score through sponsorships. The impact of sponsorship varies based on the status of the sponsor and the number of sponsors involved: * **Unverified Listing Referrer Sponsor**: Each sponsorship adds +10 to the Pair Score. * **Verified Listing Referrer Sponsor**: Each verified sponsorship contributes +15 to the Pair Score. * **Group Sponsorship Bonus**: If a trading pair is supported by 5 or more sponsors, it receives an additional +10 to its Pair Score. * **Maximum Sponsorship Influence**: The total score a pair can gain from sponsorships alone is capped at 70. ### 2. Enhancing Your Pair Score **2.1. Boosting Engagement and Trading Volume** Increasing your trading pair’s visibility and activity is pivotal for elevating its Pair Score. Implement these community-centric strategies to engage users and stimulate trading volume: * **Leverage the Referral Program:** Encourage community participation by utilizing the trading pair’s referral link available on the pair’s “Referral” page. This enables traders to share their unique link, attracting new users and tracking trade volumes generated by their referrals. For assistance, the ICLighthouse team is ready to support. * **Organize Trading Mining Events:** Partner with ICDex to host events where participants earn token rewards based on their trading volume over a defined period. Such initiatives boost engagement and liquidity. * **Host Trading Competitions:** Collaborate with ICDex to organize competitions, rewarding traders based on profit margins. This encourages active and strategic trading. * **Implement Strategic Orders:** Utilize advanced trading strategies, such as Iceberg, Grid, TWAP, and VWAP orders, to enhance volume and market presence. * **Deploy ICDex-Trader:** Expand the capabilities of ICDex-Trader, available at , into a comprehensive trading robot to automate and optimize trading strategies. **2.2. Improving Order Book Liquidity** Creating Orderbook Automated Market Making Pools (OAMM) Pools on ICDex is easy, combining traditional pool benefits with new features for more gains. Here’s how to do it quickly. 1. **Establish OAMM Pools:** Visit to create an Orderbook Automated Market Making Pool (OAMM Pool) for your trading pair and obtain its canister-id. Initiating an OAMM Pool incurs a fee of 500 ICL, reduced to 50 ICL for holders of NEPTUNE, URANUS, or SATURN NFTs. 2. **Secure Vip-Maker Status:** To enhance your OAMM pool on ICDex, consider inviting NEPTUNE NFT holders for a VIP-maker status or applying for it through an SNS proposal. This step, while optional, is highly recommended. Gaining VIP-maker status exempts your pool from strategy order fees and secures trading fee rebates for all maker orders, opening up an additional revenue stream. ***Keep in mind,** the ICLighthouse team supports only the initial proposal from a token’s development team for acquiring VIP-maker status for an OAMM pool.* For submitting a VIP-maker proposal, proceed to , select “ICLighthouse DAO,” and initiate a new proposal. Your submission should specify the action #ExecuteGenericNervousSystemFunction, with function\_id 1007 for “pair\_setVipMaker(app: Principal, account: Address, rate: Nat)” where the rate may reach up to 90. The payload must include the binary hex as a parameter, with a helpful tool available at [https://ic.house/tools](https://ic.house/tools.). For any technical assistance, the ICLighthouse team is ready to help. 3\. **Adding the Initial Liquidity:** The pool’s initial liquidity is crucial for its activation and can only be contributed by the creator of the pool. 4\. [**Transferring Funds from SNS Treasury to ICDex-Trader**](https://github.com/iclighthouse/ICDex-Trader)**:** This vital step involves decentralizing the transfer of funds to provide liquidity. For comprehensive instructions on this process, please refer to the documentation at **2.3. Securing Support from URANUS NFT Holders (Listing Referrers)** **URANUS NFT holders**, endowed with the role of listing referrers, possess the unique ability to sponsor trading pairs, thereby contributing significantly to the Pair Score: * **Unverified Listing Referrer Sponsor:** Each sponsorship from an unverified listing referrer adds +10 to the Pair Score. * **Verified Listing Referrer Sponsor:** Sponsorships from verified listing referrers contribute +15 to the Pair Score. * **Collective Sponsorship Reward:** A trading pair receiving sponsorship from 5 or more sponsors gains an additional +10 to its Pair Score. * **Sponsorship Cap:** The maximum boost a pair can receive from sponsorship activities is limited to 70 points. Each listing referrer is entitled to sponsor up to **12 pairs** annually, enhancing their visibility and trading volume on ICDex. **2.4. Submitting Metadata to Enhance Token Credibility** To ensure your token is perceived as credible and trustworthy on ICDex, it’s essential to provide comprehensive metadata to the ICLighthouse team. This includes: * **TokenControllers:** \[“7hdtw-…-cai”, “xxxx…-cai”], // Separated by commas * **TokenIsDecentralized**: true, // The token must be controlled by a DAO or have no controller * **TokenModuleHash:** “1d20aafd24d656e9ed9389325b4a113c5dda9bc6a06faf13934f30beb9d2d87e”, * **TokenMintable:** false, // Indicates whether the token is mintable * **TokenMaxSupply:** 1000000000000000, // The total supply, including possible future issuance * **Catalog:** “games”, // Available categories include: blockchain, exchanges, finance, businesses, gambling, games, storage, wallet, governance, property, identity, oracles, media, social, security, insurance, energy, health, ai\_vr\_ar, memes, and others * **Website:** [https://xxxxxx.xx](https://xxxxxx.xx/) * **Social:** * **Discord:** [https://xxxxxxxxxxx.xxx](https://xxxxxxxxxxx.xxx/) * **Github:**
**Useful Links** * **ICLighthouse NFT:** * **Discord listing-on-icdex channel:** --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://iclighthouse.gitbook.io/iclighthouse/overview/faq/project-faq/token-listing-guide.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.