Trust Badge
Live chain facts for any token, each one linked to its proof. The creator can add a Verified Dev seal.
Beta.The facts are read live for any SPL or Token-2022 token. The Verified Dev payment is built and simulated against the live chain, and has not yet been signed and sent from a real wallet on mainnet. The attestation with the Solana Attestation Service is not built.
How it works
Paste any token address. The badge reads the mint, its metadata, the largest holders and the launchpad account straight from Solana.
Each line shows one fact buyers check first, and opens its proof on an explorer. Embed the badge on a site, or use the image badge anywhere a picture works.
The creator can add the Verified Dev seal. They sign in with the wallet the launchpad recorded as creator, which is free, then pay 0.1 SOL once in one transaction. We read the payment back from the chain before the seal shows.
Facts on the badge
| Fact | What it tells you |
|---|---|
| Launched on | The launchpad, read from its own curve or pool account where possible, and progress to graduation. |
| Mint authority | Whether anyone can still create more of the token. |
| Freeze authority | Whether anyone can freeze token accounts. |
| Metadata | Who can still change the name and image, and whether the metadata is locked. |
| Token extensions | For Token-2022 tokens: a transfer fee, a permanent delegate, a transfer hook, a pause switch or other powers, with the authority behind each. |
| Creator of record | The wallet the launchpad recorded as creator, and how we found it. |
| Top holders | The largest wallets and their share, with pools, program accounts, locks and burn addresses left out and labelled. |
| Locks | Locks we found on the token, with their unlock dates. |
| Verified Dev | Whether the creator has signed in with the creator wallet. |
Each fact links to its proof on an explorer. The badge is not an audit and not an endorsement.
What it costs
Free. The badge, the image badge and every fact on them cost nothing. The Verified Dev seal is the one paid part: 0.1 SOL once per token, paid by the creator wallet inside the verification transaction. Network fees are separate.
Good to know
- Facts are read when the badge loads. They are not an audit, an endorsement or a promise about the future.
- Top holders leave out trading pools, program accounts, locks and burn addresses, and the badge says so.
- The Verified Dev seal shows only while the wallet that paid is still the token's creator of record. If the creator of record changes, the seal goes stale and the badge says so.
- Verified Dev shows that the wallet which launched the token paid and signed. It does not say the token is safe or that the team will do anything.
- The creator of record comes from the chain: the pump.fun curve creator, the LaunchLab or Meteora pool creator, or the metadata update authority when it is a wallet. The developer Jupiter lists is shown for information only.
- A creator that is a program or a multisig vault cannot sign a message, so that team cannot verify yet.
- Ledger wallets may not be able to sign in, because that depends on message signing support.
- The image badge at /badge/<token address>.png works where a script cannot run, such as a post on X or a README. It shows one dot per fact and never prints the token's own name or logo.
- Believe, Bags and Moonshot tokens are recognised from Jupiter's index, so their progress figure comes from the index and not from the chain.
Under the hood
- Mint and freeze authority, Token-2022 extensions (transfer fee, permanent delegate, transfer hook, pausable) and the metadata update authority are read from the mint and its metadata account.
- The launchpad is identified by decoding the curve or pool account for pump.fun, the Raydium LaunchLab platforms (StonkFun and Bonk.fun among them) and Meteora's bonding curve.
- Sign in is a Sign In With Solana message, checked on our server with an Ed25519 signature. Before the server trusts the wallet as the creator, it reads the chain again.
- The Verified Dev transaction has two instructions: a System Program transfer of 0.1 SOL from the creator wallet to our treasury, and a Memo that reads iam-verify and the token address. The server reads the payment back from the chain and stores one record per token.
- A session proves control of a wallet and nothing else. Every protected action checks the chain again.