DEX listing and liquidity setup across 5 pool venues

5 checks before a pool is booked

5 report items make the pool handoff easier to verify. They cover the selected venue, pair, pool address, transaction references and agreed lock details. Before booking, we check the launch inputs with your project contact. The account contact keeps one current version of the checklist.

Before we book, prepare these 7 items:

• Token: name, ticker and contract address, checked by your team.
• Chain: the network where the token contract is deployed.
• Venue: preferred option from Uniswap, PancakeSwap, Raydium, Meteora or STON.fi.
• Pair: intended assets for the pool and the team-approved configuration.
• Liquidity: assets available and the person authorized to approve their use.
• Lock: whether a liquidity lock is required and who approves its conditions.
• Links: official website and community pages for launch communications.

Your team retains control of project wallets and transaction approvals. Never send seed phrases or private keys.

We use the checklist to keep pool details consistent with your approved token information. If the launch also needs directory submissions, review Listings and verification separately. A pool launch is not a data-provider listing.

Which DEX fits your token’s chain?

5 named DEX venues are covered, but your token’s chain narrows the choice. We confirm the contract network and intended pair before preparing launch details. Your team then confirms the venue and approval contacts.

Use these 4 checks to compare the options:

• Chain match: confirm the token and pair assets use the required network.
• Pool fit: confirm the venue and pool setup match your approved plan.
• Approval path: name the person who can review and sign each transaction.
• Public path: make sure your website and community can point to the correct pool.

Uniswap, PancakeSwap, Raydium, Meteora and STON.fi are covered here. We do not assume they share the same setup. The chosen venue and pair go into the written launch checklist.

Keep the token contract, pair details and official links aligned across your project materials. If profile details also need attention, see DEXTools and DEXScreener profile updates.

5 venues, different pool inputs

5 venues give you a clear starting point for the launch conversation. The table shows what we confirm for each option. It does not claim every pool uses the same setup. Your token’s chain, pair and authorized approver determine the preparation.

The table is a preparation aid, not a statement about venue-specific eligibility. Send your target venue if you have one. Otherwise, send the chain and pair you are considering.

We review those inputs with your account contact before transaction preparation. For other data-provider work, CoinGecko listing support is a separate service.

4 handoff points from kickoff to pool record

4 handoff points keep the launch sequence visible to your team. Each point has a named decision or record. Nobody has to guess which details are approved. The schedule follows your team’s responses and transaction approvals.

1. Input check: Send the contract, chain, target venue, pair and official links. We review the checklist with your account contact.
2. Venue confirmation: Your authorized contact confirms the venue, pool details, liquidity plan and any lock requirement.
3. Transaction preparation: Your team checks the addresses, assets and signing responsibilities before approving launch activity.
4. Pool handoff: We coordinate the agreed pool and lock steps. Then we provide pool details and relevant transaction references.

Work starts within 24 hours of confirmed payment. While the placement is live, we send a report every 24 hours. These are working defaults and adjust to the job.

The handoff record gives your team a concrete item to check before sharing pool information. If you also need a CoinMarketCap listing, keep that submission distinct from the DEX pool work.

What does a liquidity-lock record show?

1 lock record should identify the agreed pool and relevant transaction details. Your team needs those details for review. Before coordination, confirm which liquidity position is covered. Also name the transaction approver and where the record will be shared. We include the agreed details in the handoff.

The report can show:

• Venue and pool details matched against your approved information.
• Relevant transaction references for the agreed pool and lock work.
• The lock conditions authorized by your project and the resulting record.
• Any unresolved input that needs confirmation from your team.

A DEX controls its own interface and display or indexing of pool information. We cannot promise how or when a venue presents a pool. We commit to the agreed coordination and handoff record. Your team should verify the final address and lock details against its approved information before publishing them.

Send us your token page, contract address, target venue and preferred window. We’ll review the 7 checklist items. Then we’ll confirm the launch sequence with your account contact.

How it works

1. 1. Send 5 launch inputsShare the contract, chain, intended pair, target DEX and project contact. Keep private keys and seed phrases private.
2. 2. Confirm the venueWe review the venue, pair, liquidity plan and any lock requirement with your authorized contact.
3. 3. Approve transaction detailsYour team checks the addresses, assets and signing responsibilities before launch coordination proceeds.
4. 4. Coordinate the poolWe coordinate the agreed pool launch and any included liquidity-lock steps with your designated approver.
5. 5. Check the handoff recordYou receive pool details and relevant transaction references. Verify them before using them in launch communications.