Skip to main content
SaucerSwap listing is permissionless. You do not need to submit a request or ask permission to make your Hedera Token Service (HTS) token tradable — you create a liquidity pool, and users can trade the token immediately. This page covers the full path from first pool to incentivized listing, plus how to take your token cross-chain. For anything not covered here, contact [email protected].

​
List a token

1

Create a liquidity pool

Any account can create a SaucerSwap V1 pool for an HTS token. Follow the V1 liquidity tutorial to create a pool and seed it with initial liquidity. V2 pool creation is permissioned and governed by the SaucerSwap DAO to limit liquidity fragmentation.
2

Confirm the token is tradable

Once at least one pool exists, users can trade the token by entering its token ID (for example, 0.0.12345) in the token selector on the swap page.
3

Submit an icon and metadata

Add a token icon and project metadata so the token displays properly in the web app. See Token icon and metadata below.
4

Apply for incentives (optional)

Default- and extended-class tokens are eligible for yield farm and LARI incentive campaigns through governance.

​
Token classes

Tokens on SaucerSwap fall into one of three classes: default, extended, or untracked. Classification affects discoverability in the web app, API coverage, and incentive eligibility — not tradability. Criteria, as of July 2026:
  • Default — the token has an icon (via token metadata or Davinci Pics) and either a V2 pool or a place among the top 50 V1 pools that contain at least one common token, ranked by aggregated TVL and volume and updated monthly. Common tokens: HBAR, HBARX, SAUCE, xSAUCE, USDC, USDC[hts], USDT[hts], WBTC[hts], WETH[hts].
  • Extended — the token has an icon available via token metadata or Davinci Pics.
  • Untracked — every other token. Users can still trade it by entering its token ID.

​
Token icon and metadata

​
Tokens with an admin or metadata key

Set or update token metadata with third-party tools: Metadata should follow the Hedera fungible token metadata schema (HIP-405).
SaucerSwap checks token information frequently and updates it automatically.
The following fields are supported:

​
Tokens without an admin or metadata key

Add or update the token icon and information on Davinci Pics. Updating a token on Davinci Pics requires connecting either:
  • the token’s treasury account, or
  • the account that executed the token create transaction.

​
Incentive campaigns

​
Yield farm (V1)

The V1 yield farm lets liquidity providers stake LP tokens in the Masterchef contract to earn dual rewards in SAUCE and HBAR. A token becomes farm-eligible once it is in the default or extended class. Creating or amending a farm campaign is a governance action: a proposal must follow the governance process and specify which farm weights would be adjusted to create the new farm. All approved farms emit both SAUCE and HBAR.

​
LARI (V2)

The Liquidity-Aligned Reward Initiative (LARI) is built into SaucerSwap V2: liquidity providers earn incentives automatically based on the size and efficacy of their positions, with no staking step. Rewards are distributed by airdrop at the end of each two-week epoch, and campaigns can distribute multiple HTS tokens per pool — so you can run a campaign denominated in your own token. Creating or amending a LARI campaign is also a governance action. A proposal must specify the campaign duration and the token allocation per epoch; see the current LARI weights for how live campaigns are configured. To initiate a LARI campaign, contact [email protected].

​
Take your token cross-chain (Axelar ITS + Squid)

You can deploy an existing HTS token to other chains with Axelar’s Interchain Token Service (ITS), then list it with Squid so it appears in the token dropdown of SaucerSwap’s in-app bridge.

​
Prerequisites

  • Your HTS token exists on Hedera mainnet (or testnet)
  • The token’s EVM address (0x...) — not the 0.0.x token ID
  • MetaMask with the Hedera network added, and HBAR for gas
  • A signing account that is associated with the token, ideally holding a balance
1

Add Hedera to MetaMask

The fastest path is Chainlist: connect your wallet and select Add to MetaMask for Hedera Mainnet (and Hedera Testnet if needed). You can also add the network manually with official Hedera network settings. Confirm you can switch to the Hedera network and see an HBAR balance.
2

Get the token's EVM address

Look up the token by its 0.0.x ID on HashScan and copy the EVM address (0x...). Make sure it is the token address, not a wallet or account address.
3

Deploy the token to other chains with Axelar ITS

Open the Axelar ITS portal, connect MetaMask, and paste the token’s EVM address. Select the destination chains you want (for example, Base or BNB Chain), then sign the transaction in MetaMask and pay gas in HBAR. Wait until the portal shows the token as deployed on the selected chains, then run a small test transfer to confirm.
4

List the token in Squid

ITS deployment alone does not surface the token in bridge interfaces. From the ITS page for your token, select Add Your Token on Squid, or go directly to the axelar-configs repository and follow the instructions to list an interchain token on Squid. A merged example pull request shows the expected shape. Once your pull request is approved and merged, Squid begins surfacing the token in the bridge modal.
Cross-chain transfers can take from a few minutes to a few hours depending on the chains involved. Track any transfer on AxelarScan by transaction hash or wallet address. If your token does not appear in Squid after listing, the usual cause is that the axelar-configs pull request has not been merged or propagated yet.

​
Next steps

Create a V1 pool

Walk through creating and seeding a V1 liquidity pool for your token.

Governance process

Learn how farm and LARI proposals move from RFC to on-chain vote.

LARI weights

See how live LARI campaigns allocate rewards across pools each epoch.

Bridge tutorial

See the in-app bridge your users will use once your token is listed.