> For the complete documentation index, see [llms.txt](https://docs.feel.cash/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feel.cash/more/legacy-coins.md).

# Legacy coins

Understand how Feel.cash supports legacy Charms coins, which onchain properties stay unchanged, and how to verify each coin’s original configuration.

Feel.cash continues to support coins historically launched through Charms. These legacy launches used the Clanker stack. They are existing onchain assets, not new Feel.cash launches and not older versions of the current Feel.cash market configuration.

## What stays the same

* contract address and chain;
* token balances and holders;
* pool and liquidity positions;
* fee recipients and allocation rules;
* transaction history;
* immutable launch parameters.

There is no automatic token conversion, migration contract, swap, redenomination, or replacement coin. The same contract remains the coin.

## What changes

The canonical product experience can move to a Feel.cash coin page, and supported legacy coins can be returned through the coin-first API. The product name, interface, or URL can change without changing the onchain asset.

Legacy records can retain provenance needed for historical compatibility. Integrators should identify them by chain and contract, then use the fee, pool, and allocation data recorded for that specific coin.

## Do not apply current launch defaults

Current Feel.cash defaults — including the `fee1` address ending, starting market configuration, 1.5% market fee, and fee split — do not apply retroactively to legacy coins.

Do not infer compatibility from a ticker or from a current launch template. Read the coin's own contract, pool, and API record.

## Historical URLs

Historical Charms market URLs can redirect to the corresponding Feel.cash coin page through an explicit stored mapping.

Redirects must never guess by ticker. Tickers can be reused; the stable identity is the chain plus complete contract address.

## For exchanges and indexers

Treat a supported legacy coin as a distinct compatibility class:

| Field                         | Rule                                              |
| ----------------------------- | ------------------------------------------------- |
| Identity                      | Chain ID + full contract address                  |
| Deployment stack              | Clanker                                           |
| Official new Feel.cash launch | No                                                |
| Contract migration            | None                                              |
| Fees and allocations          | Read from the coin's own historical configuration |