> For the complete documentation index, see [llms.txt](https://docs.tradecraft.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tradecraft.fi/token-issuers/listing-a-token-on-tradecraft.md).
# Listing a token on Tradecraft
What asset issuers need to list a CIP-56 token on Tradecraft and seed its first pool.
Tradecraft is the largest decentralized exchange on Canton by total value locked and asset volume. Tradecraft does not issue tokens; it lists them. The issuer brings the token and liquidity, and Tradecraft brings the market makers, inventory providers, and trading volume that turn a pool into a market.
This page covers the requirements and the process for a listing.
## How a listing works
A listing on Tradecraft is a liquidity pool pairing the issuer’s token with Canton Coin (CC), seeded to a minimum depth and traded against by Tradecraft’s inventory-provision bot and partner market makers. That trading activity creates validated volume on Canton for the token.
| Participant | What they bring | What they get |
| ------------------- | ------------------------------------------------------------------------------------------------------- | ------------------------------------------------------ |
| Issuer | A live CIP-56 token, a price feed, and the initial liquidity (its own or from its liquidity providers). | A liquid market for the token on Canton’s largest DEX. |
| Tradecraft | Pool creation, the inventory-provision bot, and market-maker relationships. | Trading volume and depth on the venue. |
| Liquidity providers | Pairs of tokens deposited into the pool so trades have inventory to settle against. | Swap fees in proportion to their share of the pool. |
## Requirements
Each of these is confirmed on the introductory call. Several can be in progress at the start.
| Requirement | Details |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Live CIP-56 token | The token is live on Canton mainnet as a CIP-56 asset, or within a few weeks of launch. The pool can be created ahead of launch so trading opens on day one. |
| Reliable price feed | A centralized reference price: an API, or a listing on an exchange that is not another DEX. Tradecraft’s bot prices the pool against it. |
| Security audit | Market makers and third-party liquidity providers do not deploy capital without a completed audit verifying the token’s backing. For bridged tokens, documentation of the bridge’s security model is also required. |
| Minimum liquidity | $150,000 total value locked in the first pool, split evenly: $75,000 of the token and $75,000 of CC. Liquidity can come from the issuer, the issuer’s liquidity providers, or both. |
| Token icon | A square icon for the token, used in the Tradecraft interface and by integrated wallets. |
{% hint style="info" %}
**There is no listing fee.** The only capital requirement is the liquidity in the pool, which remains in the control of whoever deposited it.
{% endhint %}
## The listing process
Every listing follows the same six steps. Pool creation takes one to two days once Tradecraft has the token and icon; the overall timeline is usually set by how quickly liquidity is ready.
{% stepper %}
{% step %}
### Introductory call
Tradecraft and the issuer walk through the token, the timeline, and the terms on this page. The issuer should be ready to cover:
* Whether the token is live on Canton
* The price-feed source
* Current and upcoming exchange listings
* Audit status, and bridge security documentation if the token is bridged
{% endstep %}
{% step %}
### Agree terms and sign
Both sides agree on the commercial terms and the liquidity commitment, and sign the agreement.
{% endstep %}
{% step %}
### Shared Slack channel
Tradecraft opens a channel with the stakeholders from both teams. Everything from this point happens there: receiving addresses, test results, and announcement timing.
{% endstep %}
{% step %}
### Pool creation
The issuer sends roughly $10 worth of the token and the token icon to the address shared in Slack. Tradecraft’s engineering team creates the TOKEN/CC pool and its pool address and runs a test transaction against it. This takes one to two days.
{% endstep %}
{% step %}
### Seed the pool
The issuer or its liquidity providers deposit the initial liquidity. Once the $150,000 minimum is met, Tradecraft runs a swap test and opens the pool publicly.
{% endstep %}
{% step %}
### Go live
Tradecraft and the issuer coordinate the public announcement, and Tradecraft’s inventory-provision bot and partner market makers begin trading the pool.
{% endstep %}
{% endstepper %}
## Issuer rewards
Depending on an issuer’s status on the Canton network, issuers can earn Canton issuer rewards on the volume generated on Tradecraft, in a compliant manner. Tradecraft covers the specifics on the introductory call.
## Pairing and liquidity guidelines
* **The first pair is against CC.** The first pool pairs the token with Canton Coin.
* **Additional pairs use other approved assets.** After the CC pool, further pairs can be added against other assets approved for CIP-56 pairs. Not every asset is approved yet, so pairs should be confirmed with Tradecraft before being planned around.
* **Pools should stay above $100,000.** Market makers need depth to stay competitive. If liquidity drops below this level, volume falls with it.
## Inventory-providing assistance
Tradecraft can provide issuers with inventory-providing assistance: Tradecraft runs its inventory-provision app on the issuer’s behalf using the issuer’s own inventory. Setup and terms are covered on the introductory call.
## Meeting the liquidity minimum
Issuers that need help meeting the listing minimum can ask Tradecraft for introductions to liquidity providers it works with. Participation is not guaranteed: providers decide independently, and they will want to see the token’s audit first. See [Guide: How to Provide Liquidity](/using-tradecraft/guide-how-to-provide-liquidity.md) for how deposits work.
## Frequently asked
### How long does a listing take?
Pool creation takes one to two days once Tradecraft has the token and icon. Overall timing is usually set by when liquidity is ready.
### Does Tradecraft issue or custody the token?
No. Tradecraft lists the token and brings trading activity to it. The token remains the issuer’s, and liquidity in the pool remains withdrawable by whoever deposited it.
### Can an issuer list more than one token?
Yes. Each token gets its own CC pool with its own minimum liquidity.
## Changes and updates
The requirements and terms on this page reflect how Tradecraft onboards issuers as of October 2026. Canton network rules change, and when a change affects listings, Tradecraft updates this page.
## Get started
Prospective issuers can email with the following to schedule an introductory call:
* Token name and ticker, and whether it is live on Canton
* Price-feed source
* Current or upcoming exchange listings
* Audit status, plus bridge security documentation if the token is bridged
* Expected liquidity and target listing date
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.tradecraft.fi/token-issuers/listing-a-token-on-tradecraft.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.