How the seal works

SEALED launches real pump.fun coins — real bonding curves, real graduation, your wallet is the creator, creator fees are yours. The difference is one reordering at birth: the coin's contract address is generated first, and the token metadata — pinned to IPFS before the coin exists — names that exact CA, together with your description.

The launch, step by step

1. The CA is born before the coin. Your browser generates the mint keypair locally. At this moment the coin's address is known, but nothing exists on-chain yet.
2. The seal is pinned. Your image and a metadata JSON go to IPFS. The JSON contains your name, ticker, image, your description, and a seal block naming the coin's own CA. IPFS content is addressed by its hash — changing one byte changes the URI — so this JSON is frozen forever.
3. The coin is created. A standard pump.fun create + buy, signed by your wallet, pointing the token's on-chain metadata at that exact URI. From this moment the chain itself references a document that could only have been written by someone who knew the CA before launch.
4. The board verifies. Our server re-reads the metadata from the mint account, fetches the JSON, and only lists the coin if seal.ca equals the mint. Listing is permissionless — the chain is the gate, not us.

Why a copycat can't fake it

A copycat launching "the same coin" five minutes later can copy your name, ticker, image — even your description. But their token's metadata can only contain one of two things:

• No seal — instantly distinguishable from the original, or
• Your seal — which names your CA, not theirs. Their own mint address won't match, and the mismatch is visible to anyone, on-chain, forever.

They cannot write their own CA into a seal that predates our board listing conventions being checked, because a valid seal must live in the metadata the token was created with — and to put their CA there they would have had to launch through the same commit-CA-first flow. At which point they are not faking a coin; they are just launching a different sealed coin with its own, different CA. The original stays uniquely identifiable.

Verify a seal yourself (no SEALED required)

1. Open the token on any explorer (Solscan) and read its metadata URI from the mint account.
2. Open that URI — it's a JSON on IPFS.
3. Compare seal.ca (or ca) in the JSON to the token's mint address. Equal → sealed original. Missing or different → copy.

The seal also freezes the description: what you read on a sealed coin's page is what the creator committed to at birth, not something edited after the pump.

Honesty notes

• What the seal proves: this exact token committed to its own CA and description before launch, through a launchpad that does commit-first ordering. It uniquely marks the original among copycats.
• What the seal does NOT prove: that the coin is safe, that the dev won't sell, or that it will go up. It is provenance, not an endorsement.
• Costs: a bare pump.fun launch costs ~0.01 SOL of rent + network fees; SEALED adds a flat 0.01 SOL launch fee, charged inside the create transaction itself — atomic, so if the coin isn't created you aren't charged, and a retry can never charge you twice. No ongoing cut: we never touch your keys, and the coin and its creator fees are 100% yours, forever.