Detect
Every launch is caught the moment it exists, with its name, ticker, image, creator and launchpad. Nobody submits tokens, and none is left out.
SEAL for platforms
Show your users which token the project launched, and which are copies. One integration covers every project launch on Elysium, with the evidence behind every answer.
Built for launchpads, trading terminals and wallets. Access is by request.
The problem
A token can be copied in seconds: its name, its ticker, its image. On a busy launchpad the copies outnumber the original before most traders have even seen it, and every platform lists them side by side with nothing to tell them apart.
Today the work falls on the trader: compare addresses, search explorers, ask in group chats. Most don’t, and the wrong token gets bought. The platform that answers the question for them is the one they trust.
How it works
SEAL reads Elysium block by block and answers one question for every project launch: of all the tokens that use its name, which one did the project launch?
Every launch is caught the moment it exists, with its name, ticker, image, creator and launchpad. Nobody submits tokens, and none is left out.
Lookalike names are normalized and grouped. Each token is traced to the wallet that launched it, and to everything that wallet launched before.
The project’s own website is read for the contract address, with its X account next. The token they point to is the original, the others are copies, and every label carries its evidence.
The API
Ask about any token by its address. SEAL answers with the label, the rule that decided it, and the evidence behind it, ready to show next to the token.
/v1/tokens/elysium:0x678fb3ab…f50fcddd// 200 OK { "token": { "chain": "elysium", "address": "0x678fb3ab…f50fcddd", "name": "PANTHEON", "symbol": "PANTHEON" }, "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", "rules_version": "2026-11-12.1", "identity": { "tokens": 31, "wallets": 29, "position": 31, "earliest": "elysium:0xd336…d452", "original": "elysium:0x8927…73a3" }, "evidence": { "creation_tx": "0x39b6…10d0", "block": 5392322, "created_at": "2026-11-12T14:38:15Z", "creator": "0x9267…0ac6" } }
A real response, shortened: one of 29 copies of Pantheon.
In your product
A trader commits to a token in four places. SEAL is built to sit in each of them, and every surface reads the same response, so your product never contradicts itself.
31 tokens named Pantheon · 29 copies flagged · 1 with its own website, left unlabelled
The second Pantheon is a copy. pantheonperps.com points to a different contract.
A generic trading interface showing real SEAL answers: Pantheon and its copies on Elysium, as the engine labelled them on 13 November 2026. Prices, balances and the chart are illustrative. Original needs the X check, which is in development; until then the strongest label is Likely original.
The labels
Three labels carry the decision. Same creator and Unresolved have labels of their own, and tokens SEAL does not cover get none. All are defined in Reading a label.
The project’s own website and X account both point to this token.
One of the project’s two channels points to this token so far, and the label says so.
Uses a project’s name and ticker, from a different wallet. Shown wherever the name appears.
Trust
A label is only worth showing if your users can trust it. These are the commitments behind every one.
Every label rests on public chain data and the project’s own public website and X account. Nothing is hidden.
Each label links to the transactions and addresses it rests on. Nobody has to take our word for it.
No project can pay to be marked Original, and no partner gets different rules for its own tokens.
When SEAL can’t prove anything, it shows nothing. When the evidence conflicts, the label says Unresolved. Likely is never shown as certain.
A label changes only when the evidence does. The previous label stays in the token’s history, with its date and reason.
Anyone can challenge a label with evidence, and projects confirm their own token by showing its address on their website and X.
Request access
SEAL is opening to a small number of platforms first, so each integration gets our full attention. Tell us what you list and where the label would appear.
Questions
SEAL reads every token launched on Elysium since its launchpads opened on 2 November 2026, and every new one as it launches. It labels the project launches among them and the tokens that copy them. Memes and tweet plays get no label. Nobody has to submit a token.
As soon as the project’s channels show its address and SEAL has read them. Every new token is on record within seconds of its launch, and its copies are grouped with it from the start.
No. A token is Original only when the project’s own website and X account both show its address, and nobody can buy that. See Confirm your token.
The new label replaces the old one in the API, and the old one stays visible in the token’s history with its reason. Platforms should update the label they show and never keep one that has been replaced.
Anyone can challenge it with evidence. Challenges are decided under the same rules as every other label, and the decision is added to the token’s record. See Challenge a label.
No. The mark says the project’s own website and X account point to this token. It says nothing about price, safety or quality, and should not sit next to wording that suggests it does.