Request token pricing

If DefiLlama doesn't price a token, its balances read as $0 — in protocol TVL, in market cap, and in anything built on our price API. Use this form to ask us to price one.

Request received

We triage by how much value is affected and how quickly the source can be verified. We'll reply if the evidence needs a follow-up.

We price from liquidity or a verifiable onchain source.

A listing, CEX market, or DEX pool — with real 24h volume, not just depth.
An onchain oracle, or a NAV / pricePerShare() function on the contract.
A fixed relationship to a token we already price (wrapper, bridged leg, 1:1 peg).

We can't publish a price supplied by the issuer, or one read off a pool thin enough for a single trade to move. An unpriced token reads as an obvious $0; a wrong price looks correct and quietly corrupts everything downstream — so we prefer the visible failure. A token having launched is not on its own a reason for us to price it.

The token Chain Must match our chain slug. A slug we don't recognise returns the same empty response as an unpriced token, so a typo looks identical to missing coverage. Token contract address The main token you want priced. Others sharing the same source go further down.

Enter a chain and address and we'll check our price API for it.

The problem Request type Where is this visible on DefiLlama, and how much value does it affect? Link the page showing the missing or wrong number. This is how we prioritise — a request with no stated impact goes to the back of the queue.

The price source Where should the price come from? Pick the strongest that exists. Mention the rest in the evidence field. Evidence This decides whether we can act. Listing or CEX — URL or market, plus 24h volume. DEX pool — link to the deepest pool, its TVL, and its 24h volume; depth without volume gives a stale price we can't publish. Oracle — address, chain, the function to call, and how often it actually updates. NAV — address, the exact function, and what units it returns. Same as another token — the address it should track, and why that holds. Other addresses the same source covers (optional) Bridged legs, other chains, or a family of tokens priced off the same oracle or issuer. One chain:address per line — we'll check each against our API as you type. A token priced on one chain and unpriced on five bridged legs is still mostly unpriced, and that's usually one redirect each.

Anything else Notes (optional) Prior issues or PRs, redemption or peg mechanics, unusual behaviour (rebasing, scaled balances, transfer restrictions). Your email (optional) Only so we can come back to you if the evidence needs a follow-up.

I've read the criteria above. The price source I've named is public and independently verifiable — not a number supplied by the token's issuer.

Can supply a working adapter? A PR against coins/src/adapters is the fastest route to a priced token, by a wide margin.