Kerne Logo
Verify Any Stablecoin

Verify any stablecoin's reserves yourself.

Paste any Base or Ethereum stablecoin address. This reads its live supply straight from the chain and tells you, honestly, which part of its backing you can verify yourself and which part requires trusting an attestor. Free, no signup, nothing to install. Do not trust the issuer, and do not trust us. Check it yourself.

It reads on-chain supply, which is self-verifiable, and names each known token's real reserve-transparency method. It is not an audit, a rating, or a solvency opinion, and a token appearing here is not an endorsement.

Check a stablecoin

Paste any Base or Ethereum token address. We read its live supply from the chain and tell you which part of the backing you can verify yourself.

Try:

Where verification ends and trust begins

Every stablecoin tells you it is fully backed. The question that separates them is how much of that claim you can check for yourself. There are three honest answers, and this tool gives you the right one for any token you paste.

1
Supply: you read it yourself

Every stablecoin's total supply is a contract function anyone can call from any node. This tool reads it live and hands you the one-line command to reproduce the exact number. No trust required, on any token.

2
Reserves: it depends

On-chain crypto collateral (LUSD, crvUSD, GHO) is readable directly. Off-chain cash, Treasuries, or exchange positions (USDC, USDT, most delta-neutral designs) are not; for those you read a third-party attestation. The tool names which case applies and who the attestor is.

3
The verdict, in two columns

For each token you get the same honest split: what you can verify yourself, and what you have to trust someone for. Attestation is a legitimate, common model; the point is to be precise about where verification ends and trust begins, never to pretend trust is absent.

Want the full field side by side? Read the Stablecoin Reserve Recomputation Report, our findings from recomputing every one of these dollars, or see the synthetic-dollar reserve transparency scorecard, which ranks the synthetic-dollar field on this exact axis, or the signed-attestation verifier for checking a proof someone handed you.

Or verify a specific stablecoin

Each token below has its own page: a live on-chain read of its supply and an honest, sourced answer to "can I verify its reserves myself, without trusting an attestor?" The verdict on the reserve leg is shown on each card.

What this tool does and does not prove

This reads live on-chain data and, for tokens in our curated registry, names the real method behind the reserves. The supply it shows is something you can reproduce yourself in one command. It does not value off-chain holdings, does not confirm that any off-chain reserve exists, and does not opine on solvency. It is not an audit, a rating, or financial, legal, or accounting advice.

Categories like "trust an attestor" describe the structure of a token's verification, not the quality of the issuer. Attestation is a legitimate, common, and often well-run model; several of the attested stablecoins here are large and audited. The point is precision about where verification ends and trust begins, so you decide with your eyes open. And always confirm you pasted the canonical contract address: a look-alike token can copy any name, but only the address is identity.

Common questions

Can you verify a stablecoin's reserves yourself?

Partly, and this tool shows you exactly where the line is. The total supply of any stablecoin is something you can always read yourself, live, from the chain. The reserves backing it are a different question. If the backing is held off-chain in custody (most fiat-backed coins like USDC and USDT, and the off-exchange leg of most CeFi delta-neutral designs), you read a third-party attestation and trust that the attestor saw the truth. If the backing is on-chain crypto collateral (LUSD, crvUSD, GHO), you can read most of it yourself. Paste any address above to see which case applies.

Is USDC fully backed, and can I check it?

USDC is backed by cash and short-dated US Treasuries held with regulated custodians, disclosed through monthly third-party attestations and a weekly reserve report. You can verify the on-chain supply yourself at any moment; the reserves themselves sit off-chain, so for those you read the attestation rather than the bank accounts. That is a legitimate, regulated model. This tool reads the live supply and names the attestor so you know precisely what you are trusting.

What is the difference between supply you can verify and reserves you have to trust?

Supply is on-chain: a contract function (totalSupply) you can call yourself from any node, so it needs no trust. Reserves are whatever backs that supply. When the backing is on-chain, you can read it directly. When it is off-chain cash, Treasuries, or exchange positions, you cannot read it; you read an attestation that a third party publishes after looking at accounts you cannot see. This tool separates the two for any token so you know exactly where verification ends and trust begins.

Is this tool an audit or a rating?

No. It reads live on-chain supply and, for known tokens, names the real transparency method behind the reserves. It is not an audit, a solvency opinion, a rating, or financial advice. A token appearing here is not an endorsement, and trust an attestor describes the structure of the verification, not the quality of the issuer. Several attested stablecoins are large, audited, and well run.

Two tokens can share a ticker on the same chain. How does this tool handle that?

By ignoring the ticker. This tool takes an address, not a symbol, and reads that contract, which is the only thing that is actually unique. ERC-20 symbols are not unique and are not registered anywhere, so the same ticker can legitimately appear twice on one chain. It happens to our own: Kerne's kUSD is 0x5C2EfdF0D8D286959b42308966bc2B97f5680AA3 on Base, 18 decimals, and a separate, unrelated token called K Dollar issued by Bankcoin Capital also reports kUSD on Base with 6 decimals. Chain ID does not separate those two; the address does. We wrote that collision up at kerne.fi/which-kusd-on-base. The general lesson is the one this tool is built on: check the address, never the ticker.

From a free read to a signed one

Want a signed, archived, re-derivable version of this read?

The check above is free and live. When you need it as a record, Kerne produces a signed, point-in-time statement anyone you forward it to can verify in about three lines without trusting you. Self-serve: the instant machine-signed read of a token's live supply, decimals, and symbol at a block is delivered on the page about two minutes after you pay in USDC on Base, no email and no human in the loop. Step up to the human-reviewed read for a signed statement of what any single public address held on-chain as of a specific block, or commission the full teardown of any issuer, the same document Kerne publishes on its research page. Current rates are on the pricing page.

Issuing a dollar yourself, with the GENIUS Act rulebook coming? The bundled transparency stack your holders can verify, a hosted verify page, scheduled machine-signed reserve reads, and a freshness badge, is the GENIUS-readiness kit. Setup then a monthly fee. Not compliance and not an audit: the verifiable layer above the attestation floor.

Kerne is infrastructure and a service provider, not an auditor, a rating agency, a custodian, or an investment adviser. This tool reads public on-chain data and names publicly disclosed transparency methods. It is not an audit, a solvency or credit opinion, a recommendation, or any form of investment, legal, tax, or accounting advice, and the appearance of any token is not an endorsement. Reserve-transparency descriptions are sourced from each issuer's public disclosures and the Kerne synthetic-dollar scorecard, cross-verified June 29, 2026; verify at the canonical sites. Kerne is not affiliated with any issuer or attestor named here. Kerne is early: it has one completed external audit, published in full on July 31, 2026, and its deployed vault runs earlier bytecode than the reviewed commit, disclosed at kerne.fi/dataroom.