Check a coin yourself
Paste a coin's mint. This page derives the coin's vault addresses in your browser, reads them from the Solana RPC you choose, and tells you whether its creator fees and dev bag are behind a hash-based vault. After it loads, the check itself talks only to the RPC you choose and, for holder rewards and identity proofs, to the coin's own metadata file. The page's top bar asks our server for your session once on load.
iWhat the checks mean
Sealed means three things are true on chain at once: the vault program holds a Launch record for the mint, that record names a real vault whose address commits to its genesis public key, and pump.fun's fee-sharing config for the coin is locked with the vault's owner address receiving at least half of creator fees. That is the same rule the Appdrop site uses for its Sealed badge.
Standard fee split means there is no Launch record and no vault, and pump.fun's fee-sharing config is locked with its larger share going to an ordinary wallet. The split can never be changed, but the creator's share is behind that wallet's key. Such a coin is never reported as sealed. The chain does not record which site launched a coin, so this result says nothing about that. Every recipient and share is listed.
Team split means the locked split divides the creator share among several recipients. It is never reported as sealed unless a vault launched the coin and its owner address holds at least half; each recipient's share is behind that recipient's own key.
Holder rewards is the same, except that the larger share goes to the coin's distributor wallet, named in the coin's metadata (or entered above) and confirmed against the locked split. The split is enforced on chain; the payouts from the distributor to holders are made by Appdrop's server asking Privy to sign, in SOL, and you can follow them as outgoing transfers from that wallet on Solscan.
If the coin's metadata carries an identity signature, it is checked and shown under the seven checks. It says who signed the launch. It is never part of the sealed verdict.
The dev bag and its lock, the spend policy, the program's upgrade authority, and the vault's epoch and one-time key count are reported next to the verdict. A lock is shown with both numbers that matter: how many tokens it covers and how many the vault holds, because it protects only what is there. They do not change it, and they are never hidden inside it.
- pass the chain shows it.
- fail the chain shows the opposite. The verdict names the first failed check.
- ? it could not be read. Nothing is assumed.
- note and warn a fact you should weigh, such as an empty dev bag or a program that can still be upgraded.
iiWhat the result depends on
- The RPC. It answers every read. A dishonest RPC can show accounts that do not exist. Use your own node, or run the check against two providers.
- The program id. A Launch record under some other program proves nothing. The id is prefilled from this site when it can be, and you can type your own.
- This page's code. It is two plain files, ent-verify.js and the program's client at /pq/client/ix.js. The docs list a dozen lines that do the same reads without this page.
- pump.fun and the vault program. What a locked split and an upgrade authority mean for you is in the threat model.