Request access

Seal. The verification layer for every project launch.

Every token can be copied. Its origin can’t. SEAL finds the token each project actually launched, marks the copies, and gives platforms the answer to show their users.

SEAL for platformsAPI reference

Anyone can launch a token with any name.

Only one is real.

SEAL traces every token back to its true origin, automatically. Nobody has to apply.

How it works. Detect. Trace. Verify.

SEAL picks up every new token the moment it launches.

It follows each one back to the wallet and block it came from.

The original gets its seal. Every copy is marked.

Value flows to the people who build.

Copies are filtered before they can drain a real project.

SEAL for platforms

Built into the places people trade.

SEAL is infrastructure. Launchpads, terminals and wallets ask it about the tokens they list, and their users see the answer where they already decide.

Request accessHow platforms use it
Every launchon Elysium, read straight from the chain
Block onethe full history, from the day the launchpads opened
One answerper project, with the rule and the evidence behind it
No sign-upSEAL finds every launch itself. Projects never register

The answer

One label per token, and the reason behind it.

SEAL groups every token that uses a project’s name and finds the one the project’s own channels point to. The rest are marked as copies. Tokens that are not project launches get no label at all.

Original

The project’s token

Its own website and X account both show this contract address.

Likely original

One channel so far

The project’s website shows this address. The label says likely until the second channel does too.

Copy

Someone else’s token

The project’s name and ticker, launched by a different wallet, before or after the real one.

Original needs the X check, which is in development. Until it ships, the strongest label SEAL gives is Likely original.

The API

One request. One answer.

Ask about a token by its address. SEAL answers with the label, the rule that decided it, one sentence your users can read, and the onchain evidence behind it. For a copy, it also names the project’s real token, so your product can offer it instead.

Read the API reference

GET/v1/tokens/elysium:0x678fb3ab…f50fcddd
// 200 OK
{
  "covered": true,
  "label": "Copy",
  "basis": "Uses the name and ticker of 0x8927…73a3, the token the project’s website pantheonperps.com points to. Launched after it by a different wallet (0x9267…0ac6).",
  "rule": "copy",
  "identity": {
    "tokens": 31,
    "original": "elysium:0x8927…73a3"
  }
}

A real response, shortened: one of 29 copies of Pantheon.

Independence

A label is only worth something if nobody can buy it.

Not for sale

No project can pay to be marked Original, and no partner gets different rules for its own tokens.

Honest about doubt

When SEAL can’t prove anything, it shows nothing. When the evidence conflicts, the label says Unresolved.

Every change on record

A label changes only when the evidence does, and the previous one stays in the token’s history with its date and reason.

Building on Elysium?

SEAL is opening to a small number of platforms first.

Request access