> For the complete documentation index, see [llms.txt](https://docs.kujira.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kujira.app/dapps-and-infrastructure/fin/listing-tokens-on-fin.md).

# Listing tokens on FIN

<https://fin.kujira.network/trade/listing>

FIN offers a user interface at <https://fin.kujira.network/trade/listing> that allows community members to propose the launch of a new token pair on the FIN platform using Kujira governance. In order to use this feature, you must have a Sonar, Metamask, Leap, or Keplr wallet and be connected.

<figure><img src="/files/DnCUrax52rZMc8orB92j" alt=""><figcaption><p>Submit a Kujira Governance proposal to list a FIN token pair</p></figcaption></figure>

To create a proposal, you will need to select a base asset and a quote asset for the proposed token pair. The base asset is the asset that is being traded, while the quote asset is the asset being used to price the base asset. For example, if the base asset is [KUJI](/tokenomics/kuji-token.md) and the quote asset is USK, then the price of KUJI would be quoted in [USK](/dapps-and-infrastructure/usk-stablecoin.md).

After you have submitted your proposal, it will enter the deposit phase. During this phase, a minimum deposit must be provided by one or more addresses before the proposal can move on to the voting stage. It is important to note that not all tokens may be eligible for listing on FIN.

After the community governance process approves a proposal, the team will set up a token pair user interface on FIN, and begin allowing limit order buys and sells to gather initial liquidity. Once there is enough liquidity, trading will commence.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.kujira.app/dapps-and-infrastructure/fin/listing-tokens-on-fin.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
