One named contact for DEX listing and liquidity setup

What does a DEX pool arrangement settle?

A DEX pool arrangement settles where the token will trade, which pair it will use and who approves each action. It turns several launch decisions into a clear sequence before assets or public instructions are involved.

The service covers pool launches on Uniswap, PancakeSwap, Raydium, Meteora and STON.fi. A suitable venue must match the token’s network and the project’s operating plans. We begin with the contract and network details, then record the intended pair, who contributes each asset and who can authorize transactions.

That distinction matters: pool coordination, liquidity provision and a lock arrangement are related, but they are not the same task. The written scope names each agreed responsibility. Your team can also see which actions remain with its authorized wallet holders.

A private briefing keeps early details with the people involved in the decision. If the project has other directory or verification work underway, the listings and verification overview shows the adjacent services. We keep this arrangement focused on the pool and its supporting records.

Venue selection follows the chain

A composed launch begins with compatibility, not assumption.

Uniswap and PancakeSwap may be considered for supported networks; Raydium and Meteora are options for Solana launches, while STON.fi is relevant to TON. The first decision is the network hosting the token contract. The second is whether the chosen venue supports the intended pool and operating arrangement.

The pair determines which asset sits alongside the token, so the treasury and token teams should agree on its source and authorization. We record those responsibilities before coordinating the pool. This avoids public instructions that name an unconfirmed pair or point to the wrong contract.

A single named point of contact keeps questions and approvals in one place. Any public-facing wording prepared for the launch is shown to you before it is shared. For projects also updating profile details, a DEXTools and DEXScreener profile update can keep visible token information aligned with the approved launch details. Solana teams may also coordinate this work with their wider ecosystem plans.

The liquidity record stays precise

A useful liquidity record states what is being locked, who controls it and what release conditions apply. The word “locked” alone does not explain the arrangement to your team or to people who later check its evidence.

Before assets move, we confirm which liquidity position or receipt is relevant to the selected pool design. The authorized person confirms the lock instructions, controlling address and intended period. After the relevant transactions, the record can include references and the public location where evidence is available.

The project should be able to answer these points from its own records:

• Do the token and pool addresses match the approved launch details?
• Who is authorized to initiate and control the lock?
• What conditions govern release, and how will they be described?
• Does the evidence correspond to the correct liquidity position?

We keep the lock description consistent with the arrangement the team approves. It is not a substitute for reviewing wider token controls. Where supply figures also need a separate verification workflow, see circulating supply verification.

The arrangement moves through four approvals

Four clear stages keep the pool plan, approvals and public record connected. Your team approves the operational details before coordination, then receives a concise handover when the agreed work is complete.

The named lead keeps the working record and brings open questions back to the relevant approver. Written sign-off is required for the pair, asset responsibilities and lock instructions before coordination begins. Nothing public-facing that we prepare leaves the desk before your approval.

The schedule is set once the contract details, signers and assets are ready. A concise handover records completed actions and references, so your team is not left piecing together decisions from separate conversations.

A note on pool visibility and platform boundaries

A completed pool creates the agreed on-chain trading venue, but it does not determine how third-party interfaces display or categorize it. Each protocol’s available pool and liquidity-lock mechanisms follow its own implementation, and external tracker visibility or ranking cannot be promised through pool setup.

Your team controls the token and pair approvals, authorized transactions, asset contributions and accuracy of its own launch communications. Before an announcement, check the final token and pool addresses on the relevant network. Confirm that the paired asset matches the approved plan and that any lock evidence relates to the correct position.

We document the work that has been agreed and completed, rather than describing an unconfirmed status as verified or featured. For separate token metadata work, an explorer token information update can address public-facing details on an explorer. A confidential record of approvals remains with the people handling the launch.

A quiet beginning, with the right detail

A short, private briefing is enough to establish whether the pool plan is ready for coordination. The most useful starting details are the target network, token contract, preferred venue and any lock requirement. Your named contact can then identify missing approvals and outline the next actions without circulating launch details more widely.

If the project is also preparing a directory submission, CoinGecko listing support and CoinMarketCap listing support can be considered separately. The pool record remains distinct, so each request has a clear owner and purpose.

A note naming the target network is enough to begin; your named contact will outline the next step and keep the material confidential until your written sign-off.

How it works

1. Share the launch essentialsProvide the network, token contract, intended venue and launch window. Identify the person authorized to approve transactions.
2. Approve the pool planYour token and treasury leads confirm the pair, asset responsibilities and any lock instructions in writing.
3. Coordinate the agreed setupThe named lead coordinates the approved actions and checks the resulting public records against the confirmed details.
4. Receive the handoverYour team receives a concise completion record with relevant references for internal records and accurate launch communications.