Linking to a token page
The URL of a token page, from a launch address or a primary mint.
What is live today
TREND runs on its own dev validator. The mainnet programs are not deployed: their ids are reserved and no launch exists there. Statement as of 2026-10-10.
The client is https://dev.trend.fun today. https://trend.fun is a holding page until launch, so the links below use
the dev host. They change host and nothing else when mainnet opens.
What works today
| You have | Link | Notes |
|---|---|---|
| A launch address | https://dev.trend.fun/#/t/{launch} | The token page. |
| A primary mint | https://dev.trend.fun/#/t/{mint} | The page resolves a mint through GET /v1/launches/{id}, which matches an address, a primary mint or a ticker. |
| A collectible | https://dev.trend.fun/#/collectibles/{id} | A #/t/ link to a collectible redirects itself here. |
| A launch address, with a social preview | https://dev.trend.fun/t/{launch} | Serves the preview card, then redirects to the page. |
The route is a hash route: everything after # is read by the page in the browser. Some link parsers drop a fragment,
so test your own before relying on it.
What does not work yet
https://dev.trend.fun/t/{mint}, the path form with a mint, is not reliable for sharing. The preview route that
builds the social card matches a launch address only, so a mint link is expected to redirect to the page with a
"not found" preview card. This is read from the code and was not exercised against the deployed host. Use the hash form
above for a mint until the preview route learns to resolve one.
From the API
Every row from GET /v1/launches carries address and primaryMint. Build the link from either:
const link = (launch) => `https://dev.trend.fun/#/t/${launch.address}`;GET /v1/launches/{id} also accepts a ticker. Tickers are not unique, so a ticker resolves to one of the launches that
share it. Link by address or mint.