Start with the chain, then match the pool
DEX listing and liquidity setup starts by matching your token and chain to a practical pool plan. We help organize the choices before anyone schedules a transaction or publishes launch details.
The venue name alone is not enough to make that call. Your technical owner should confirm the token contract and chain. Your liquidity contact should confirm the intended pair and pool design. Then we can coordinate around a suitable option, including Uniswap, PancakeSwap, Raydium, Meteora or STON.fi.
| Part of the plan | What your team confirms | What we coordinate |
|---|---|---|
| Venue and chain | Token contract and target chain | Whether the selected venue fits those details |
| Pair and pool | Intended trading pair and pool plan | A shared record of the agreed setup |
| Liquidity actions | Authorized contacts and transaction roles | The agreed sequence and public references |
| Lock, if planned | Mechanism and terms the team approves | Coordination and evidence included in the plan |
This table gives each owner a clear question to answer. It also helps keep DEX setup separate from directory applications, which have their own steps. For the wider picture, see Listings and verification. If a centralized venue is also on your roadmap, centralized exchange listing support is a separate workstream.
Give the launch a calm, shared starting point
Picture a two-person game studio after a quiet month of posting. The contract is ready, but the studio has not settled who checks the pair or confirms the liquidity actions. We would put those decisions on one short checklist before anyone announces a pool.
A launch plan works best when the facts come from the people who own them. Your technical contact confirms the contract and chain. Your treasury contact confirms who can act and who approves each transaction. Your communications lead uses those same details in public updates.
We help these people work from the same version of the plan. That means checking the token address, intended pair, official project links and launch window together. It also means flagging any missing decision early, rather than letting an assumption appear in an announcement.
Say a project already has a pool but needs to explain its liquidity arrangement. We can help gather the public references and clarify what the team can accurately say. For separate token contract or explorer details, explorer token information and logo updates may be useful alongside the pool work.
What should your team decide about liquidity and a lock?
Your team should decide what goes into the pool, who controls the relevant transactions and whether a lock belongs in the plan. We make those choices visible before coordinating the agreed actions.
Liquidity setup means adding the intended assets to the selected pool. A liquidity lock is a separate arrangement with its own mechanism and terms. It should not be described as automatic or assumed to work the same way across every venue. We ask your team to identify what “locked” means for this launch and what public record will support that description.
Agree the transaction roles
Name the technical and treasury contacts who can verify details and coordinate authorized actions. Confirm who approves each transaction, and make sure the launch plan uses the correct chain and token contract. This gives everyone a clear handoff rather than a trail of conflicting instructions.
Make the public record understandable
Keep the details a reader can check in one place: the token contract, chain, pool or pair reference. Include transaction records for the agreed actions. If a lock is included, note its mechanism and the public evidence that supports its terms. Our handover can then show what happened without asking your community to piece it together from scattered messages.
If a launchpad is part of your plan too, launchpad listing support covers a different set of decisions.
A five-part route from project details to handover
We organize the work around five checkpoints, from the first project details to a record your team can keep. You approve the venue and responsibilities before launch actions are coordinated.
- Gather the basics. Share the contract, chain, intended pair, preferred venue and launch window. Name the technical and treasury contacts.
- Check the details. We compare the supplied information and flag open decisions about the pool, transaction roles or lock arrangement.
- Agree the plan. Your team confirms the venue, pair, responsibilities and work to be coordinated. We do not move ahead on assumed approvals.
- Coordinate the setup. We work with authorized project contacts on the agreed pool and liquidity actions, then collect the relevant public references.
- Hand over the record. You receive the confirmed pool details, transaction references and any agreed lock evidence, with project follow-ups noted.
For example, imagine your technical lead is available before your communications lead. We can use an early check-in to confirm contract and pair details. Then align the public wording once the remaining owners have approved the plan. The schedule is set with your team around readiness and availability, not guessed from a generic launch calendar. If profile details need attention after setup, DEXTools and DEXScreener profile updates can be handled as related work.
Keep the pool record clear after launch
A useful handover lets your team compare public pool details with the transaction records for the actions it agreed to take. We provide a concise written summary of the venue, chain, token and pair, alongside the references gathered during coordination.
Before sharing a launch update, check that the contract address matches your official project source. Confirm that the pool reference points to the intended chain and token. If you describe liquidity as locked, make sure readers can find the supporting record and understand its terms. For other tracker submissions, CoinMarketCap listing support and CoinGecko listing support are distinct tasks, but consistent token facts help connect them.
A third-party DEX controls how its interface displays or indexes a pool. A lock provider applies its own terms; neither outcome is ours to set. We commit to the agreed coordination and evidence, not a particular display or trading response.
To start, send Brand Community the token contract, target chain, preferred venue, intended pair and launch window. Include the technical and treasury contacts who can confirm details. We’ll review those inputs, point out what needs a decision, and map the next steps with your team.
How it works
- Share the launch detailsSend the contract, chain, intended pair, preferred venue and launch window. Name the technical and treasury contacts.
- Review what is readyWe check the supplied facts and note any open decisions about the pool, transaction roles or lock.
- Confirm the planYour team agrees the venue, responsibilities and actions before coordination begins.
- Coordinate the agreed workWe work with authorized project contacts and gather public references for the handover.
- Receive the recordYou get pool details, transaction references and any agreed lock evidence in one concise summary.
Frequently asked questions
Which DEX venues can fit into this pool plan?
We can coordinate pool work involving Uniswap, PancakeSwap, Raydium, Meteora and STON.fi. The right fit starts with your token’s chain, intended pair and pool plan. Share the contract address and target chain so we can review those details before you settle on a venue.
What should I send before we discuss a pool launch?
Send the token contract, chain, intended pair, preferred venue, launch window and official project links. Name the technical contact who can confirm token details and the treasury contact for transaction coordination. If a lock is planned, include its proposed mechanism or the person who will decide on it.
Can you coordinate a liquidity lock as well?
Yes, when it is part of the agreed work. Your team chooses or approves the mechanism and confirms the terms it wants to communicate. We can coordinate the agreed steps and collect public evidence, then include those details in the handover. For instance, the record can identify the mechanism and the reference readers can inspect.
Who is responsible for signing pool transactions?
The project’s authorized signers remain responsible for approving and carrying out transactions. We coordinate with the technical and treasury contacts your team identifies, and check that those roles are clear before the launch sequence is agreed. This keeps transaction authority with your project while making the coordination easier to follow.
How long should we allow for DEX pool setup?
We set a working schedule after checking contract readiness, venue choice, signer availability and any planned lock arrangement. If those details are ready, we can agree the next checkpoints with your team. If an owner still needs to decide, we include that in the plan. The schedule is confirmed before launch actions are coordinated.
Does pool setup also update CoinMarketCap or CoinGecko?
No, those are separate listing processes. Pool setup records on-chain details, while tracker submissions follow their own requirements. We can help keep the token facts consistent between the workstreams. For example, your team can coordinate the pool first and then prepare a separate CoinMarketCap listing or CoinGecko listing.
Tell us about your project
Answer four quick questions and a manager will send you a plan, timing and a price range within the hour. Everything stays confidential.
Loading the form…