Docs
Home Platforms API Research About Request access

Overview

What is SEAL

SEAL finds the real token of every project that launches on Elysium, marks the copies, and shows the evidence behind every answer.

The problem

Launching a token on Elysium takes a name, a ticker, an image and a few seconds. Nothing stops anyone from launching a second token with the same name, the same image and the same links a minute later, or a minute before.

Traders find tokens by name. When a project launches, copies follow within minutes, some of them launched before the real token by wallets that watch for announced names. Whoever buys a copy usually finds out only after the real token has moved without them.

What SEAL does

SEAL reads every token launched on Elysium. It picks out the project launches, groups every token that uses a project’s name, and reads the project’s own website for the contract address. The token it points to is the project’s token. The others are copies. Checking the project’s X account as well is in development.

Every label comes with its evidence: the creation transaction, the creator, and the page where the project shows its address. Nobody has to take SEAL’s word for it.

Nobody applies to SEAL, nobody registers, and nobody pays for a label. Memes and tweet plays get no label at all.

Who it is for

Platforms
Show which token is the project’s own, right next to the token, on launchpads, terminals, screeners and wallets. Access is by request.
Projects
Nothing to do beyond what projects already do: show the contract address on their own website and X account.
Traders
Meet SEAL on the platforms they already use. The mark next to a token says the project itself points to it.

What SEAL is not

SEAL is not a rating, a price signal or an audit. It reports which token a project launched. An original token can still fail, and a label is never a reason on its own to buy anything.

SEAL reports origin. It is not investment advice. Read the Disclaimer.

Overview

Reading a label

SEAL labels project launches and the tokens that copy them. Everything else gets no label. This chapter explains what each label means, what stands behind it, and how labels change.

The labels

Original

The project’s own website and its own X account both show this token’s contract address.

Likely original

One of the project’s channels shows this address. The other does not yet, so the label says likely. Read the basis before relying on it.

Copy

Uses the name and ticker of a project’s token, launched by a different wallet. A copy can be older than the project’s token.

Same creator

Launched by the same wallet as the project’s token: a relaunch or a test, not a copy.

Unresolved

The channels of two different projects each point to a different token with this name, or the website that confirms a token may be a clone of an older project’s. SEAL shows no original until the evidence settles it.

No label

Memes, tweet plays, tokens from launch farms, and projects whose channels do not show an address yet get no label. Platforms show nothing for them.

No label is not a verdict. It means SEAL has nothing it can prove about that token.

What a record shows

Behind every label is a record anyone can read.

Label and basis
The label, and the rule that decided it, in one sentence.
Evidence
The creation transaction, block, creator address and launchpad, and the project page that shows the address.
Identity
The other tokens that use the same name and ticker, with their labels.
History
Every change to the label, with its date and its reason.

Labels change

A Likely original becomes Original when the project’s second channel shows the address. A label is reviewed when a channel changes: when a project takes its address down, or when another project’s channels point to a different token with the same name. Every change is logged and the previous label stays visible.

A label is a statement about the evidence at the time it was made, not a promise about the future.

Method

How SEAL finds the original

Anyone can launch a token with any name, image and links. This chapter sets out which tokens SEAL labels, how it decides which one is the project’s, and where that evidence stops.

Scope

SEAL answers one question: of all the tokens that use a project’s name, which one did the project launch?

SEAL labels project launches only: products, protocols, companies and teams. Memes and tweet plays get no label. Nobody can say which of a hundred identical memes is the real one, and SEAL does not try.

SEAL reports origin. It does not rate projects, predict prices or judge whether a token is safe to hold.

Coverage

SEAL starts on Elysium, Kinetiq’s layer-2, which settles to HyperEVM. It reads every token created through the Elysium launchpads it follows.

Tokens deployed directly as ERC-20 contracts, and tokens on HyperEVM and HyperCore, are not covered yet.

Definitions

Token
A contract address on Elysium. Two deployments are two tokens, even if everything else about them is identical.
Identity
The name and ticker a token presents to traders, after normalization.
Project launch
A token launched by a product, protocol, company or team, as opposed to a meme or a tweet play.
Channel
A website or an X account that the project controls and that the token links in its launch metadata.
Original
The token the project’s own channels point to.
Copy
A token from a different wallet that uses the name and ticker of a project’s token.

Discovery

SEAL reads Elysium block by block. Launchpads emit an event for every token they create, carrying the token and the creator. A token enters the record as soon as SEAL reads that event.

For each token SEAL stores the creation transaction, the block and the position within it, the creator, the launchpad, and the launch metadata as first seen: name, ticker, image, description and links. Nobody submits tokens to SEAL, and there is no listing.

Identity

Before tokens can be compared, their names and tickers are normalized: Unicode NFKC normalization, case folding, invisible characters and accents removed, and lookalike characters folded to the letter they imitate. ORBlT, 0RBIT and ОRBIT (with a Cyrillic О) all resolve to ORBIT.

Two tokens share an identity when both their normalized name and their normalized ticker match. A shared ticker alone is not enough.

Project launches

SEAL reads every launch, then decides whether it is a project. A token is not a project if any of these holds:

  • Its wallet has launched four tokens or more. Teams launch one token. Farms launch thousands.
  • Its name or description is a meme.
  • It links someone else’s post, a news article or a video instead of an account of its own.
  • Its description is a launch tool’s boilerplate.

Otherwise it needs channels of its own: a website on its own domain, an X account, or both. They are weighed together with whether they match the name, whether the description describes a product, and whether docs or code are linked. Websites and accounts that tokens of three or more different names link belong to launchpads and tools, and count for nobody.

When in doubt, the answer is no label. A missed project shows nothing. A wrong Copy would hurt a real one.

Channels

A project tells its own people which token is theirs: it puts the contract address on its website and posts it from its X account. A copy can borrow a project’s name and links, but not its channels.

Website
SEAL reads the homepage of the website a token links, together with the scripts the page loads, and looks for contract addresses. A page that shows many addresses, or the tokens of several projects, is a listing and does not count.
X account
SEAL will read the public profile and posts of the X account a token links, and look for the contract address. This check is in development: today SEAL reads websites only, so no token is labelled Original yet.

Links alone prove nothing. Anyone can put a real project’s website in a token’s metadata. What counts is the address on the project’s own channel.

Classification

Within one identity, SEAL applies the rules below in order. The first rule that holds decides the label.

Not a project
If no token in the identity is a project launch, no token in it gets a label.
Not confirmed
If no project channel shows the address of any token in the identity, no token in it gets a label yet.
Conflicting
If the channels of two projects show different tokens, launched by different wallets, the identity is Unresolved. It is also Unresolved when an older token with the name links a different website and X account and describes the project in the same words as the confirmed one: the newer website may be a clone, and a clone always shows the cloner’s own address.
Confirmed
The token the project’s channels show is the Original when its website and its X account both show it, and Likely original when one of them does.
Same creator
Another token from the same wallet is labelled Same creator.
Its own channels
A token with the same name that links a different website and a different X account of its own may be a separate project. It gets no label.
Everything else
Every other token in the identity is a Copy, including copies launched before the project’s token.
LabelMeaning
OriginalThe project’s website and X account both show this address.
Likely originalOne of the two shows this address. The basis is shown.
CopyUses a project’s name and ticker, from a different wallet.
Same creatorFrom the same wallet as the project’s token.
UnresolvedTwo projects point to different tokens. No original is shown.

Every label comes with the evidence behind it: the creation transaction, the creator and the page that shows the address, all of which anyone can check. SEAL does not publish a score, because a number would hide the reasoning.

Edge cases

The copy came first
Copiers watch for announced names and launch before the real token, so order of creation alone would favour the copy. The project’s channels outrank order: the token they show is the project’s, even if a copy is older.
Same name, different projects
Two projects can use the same name without either copying the other. A token that links channels of its own gets no label rather than a wrong Copy.
Relaunches and tests
Tokens launched by the project’s own wallet are labelled Same creator, never Copy.
Borrowed links
A token that links a real project’s website, but whose address that website does not show, gets nothing from the link.
Address posted late
Many projects post their address after launch. Their token gets its label once SEAL reads the channel again. Until then it has none.

Corrections

Anyone can challenge a label by submitting evidence, as described in Challenge a label. A challenge is decided by the same rules as every other label. Each change is logged with its date and its reason, and the previous label stays visible in the token’s history. Nothing is removed silently.

Independence

Labels cannot be bought. A project cannot pay to be marked original, and cannot pay to have another token marked as a copy.

Limitations

X is not read yet
Today SEAL confirms tokens through websites only. Until the X check ships, the strongest label is Likely original, and a project whose website does not show its address gets no label.
One channel can be faked
Anyone can put up a website in an hour. A website alone gives Likely original, never Original. An X account with a history is much harder to fake, which is why Original needs both.
Channels can be taken over
If a project loses control of its website or account, that channel can point to the wrong token until the project takes it back.
Silent on some real projects
A project whose channels never show its address, or that SEAL does not recognize as a project, gets no label.
Only what is public
Private agreements, offchain intent and the people behind an address are outside what SEAL can see.
Sequencer order
Elysium is a rollup. The order of transactions within it is the order its sequencer recorded.
Origin is not safety
An original token can still lose its value, be abandoned or be misused by its own team.

For projects

Confirm your token

There is nothing to sign up for and nothing to submit. Show your token’s contract address on your own website and your own X account, and SEAL finds it.

How it works

SEAL labels your token Original when your website and your X account both show its contract address.

Today SEAL reads websites; the X check is in development. Until it ships, a website that shows your address gives your token Likely original. Post the address on X anyway, so your token is ready when it does.

Both have to be the ones your token links in its launch metadata. The link then runs both ways: your token points to your channels, and your channels point to your token. A copy can link your website, but your website will never show its address.

On your website

Show the full contract address as text on your homepage, for example next to a buy link or in the footer. SEAL reads the homepage and the scripts it loads. An address that appears only in an image, or behind a login, cannot be read.

On X

Post the full contract address from your project’s account, and leave the post up.

Before and after launch

Copies often launch before the real token. That does not matter: once your channels show your address, your token is the one SEAL marks and the others are Copies, older or not.

Post the address as soon as your token exists. Until SEAL has read it, your token has no label.

If you relaunch

Show the new address on both channels. Launch the new token from the same wallet if you can: the old token is then labelled Same creator rather than Copy.

If you lose a channel

If someone takes over your website or your account, contact us from the channel you still control and challenge the label.

Confirming costs nothing, and labels cannot be bought.

For projects

Challenge a label

If you think a label is wrong, you can challenge it. Challenges are decided by evidence, under the same rules as every other label.

Who can challenge

Anyone: a project, a holder, a researcher. There is no fee, and a challenge is treated the same way whoever sends it.

What to include

Token
The contract address on Elysium.
The label
The label you dispute, and the label you believe is correct.
Evidence
Transactions, addresses, or pages and posts on the project’s own channels that support your case. A statement without evidence cannot change a label.

How it is decided

The evidence is checked and the rules in the Method are applied to it, exactly as they would be to new evidence found by SEAL itself.

Either way, the decision and its reason are added to the token’s record. If the label changes, the previous label stays visible in its history.

While it is open

The current label stays in place while a challenge is reviewed. If the challenge shows that the evidence conflicts, the identity moves to Unresolved until it is settled.

If it is your token

If you are the project, you usually do not need to challenge anything. Confirm your token: once your channels show its address, your token is the one SEAL marks, even if a copy was launched earlier.

Send a challenge

Send your challenge through the contact form (choose “A label”) or to @sealmarkets on X, with the token and the evidence in the message.

For platforms

Showing the SEAL mark

Launchpads, terminals, screeners and wallets can show SEAL labels next to the tokens they list. This chapter sets out how.

The mark

Original

The SEAL mark in blue, with the word Original.

Likely original

The mark in outline grey, with the words Likely original.

Copy

No mark. The word Copy, in your warning colour.

Same creator and Unresolved are shown as text, without a mark. Tokens without a label show nothing.

Rules

Original only
Show the blue mark only on tokens labelled Original. Never on Likely original.
Copies everywhere
Show Copy wherever the token’s name appears, in lists and search results too. That is where traders pick the wrong token.
Nothing for no label
A token without a label gets no mark and no warning. No label does not mean copy.
Link the evidence
Link the mark to the token’s SEAL record, so anyone can see what it rests on.
Stay current
Labels can change. Update yours when SEAL publishes a change, and do not keep a label after it has been replaced.
Keep the mark intact
Do not redraw, recolour or merge the mark with other badges.

What the mark says

The mark says that the project’s own website and X account both point to this token. It says nothing about price, safety or quality, and should not sit next to wording that suggests it does.

Access

Access for platforms is by request. Tell us what you list and where the label would appear: Request access. The fields, endpoints and errors are documented in the API reference.

Trust

Independence

A label is only worth something if nobody can buy it. These are the commitments that keep SEAL’s labels independent.

Commitments

Labels are not for sale
No project can pay to be marked original, or pay to have another token marked as a copy.
No application
SEAL decides on its own which launches it labels. Nobody applies or registers, and nobody can opt a token out.
Partners get no exceptions
A launchpad or platform that works with SEAL gets the same rules for its tokens as everyone else.
One set of rules
Every label is decided by the Method. Labels change only through new evidence or a challenge.
Nothing silent
Every change is logged with its date and its reason. Previous labels stay visible.

Trust

Data sources

Everything SEAL uses is public. This chapter lists where it comes from, and what SEAL does not use.

Sources

Elysium
Blocks, and the events Elysium launchpads emit when they create a token, with the creator they record.
Launch metadata
What creators provide at launch: name, ticker, image, description and links.
Project websites
The homepage of the website a token links, and the scripts that page loads, fetched over HTTPS with a plain request.
X
Public profiles and posts of the accounts that tokens link.

What SEAL does not use

Price and volume
Market activity never decides origin. A copy that trades more is still a copy.
Private data
SEAL does not use private messages, private data or information it cannot show.
Unsupported claims
Reports without evidence do not change a label.

First seen

Launch metadata can change after a token is created. SEAL keeps the metadata it first saw. Websites and accounts are read again over time, so a label follows what the project’s channels show now.

Trust

Disclaimer

What a SEAL label is, and what it is not.

Information only

SEAL provides information about the origin of tokens. Nothing SEAL publishes is investment, financial, legal or tax advice, or a recommendation to buy, sell or hold any token.

Origin is not safety

A label says where a token came from. It says nothing about a token’s value, liquidity, security or the conduct of its team. An original token can still lose its value.

Labels can be wrong

Labels are based on the public evidence available when they are made. That evidence can be incomplete or change, and labels can change with it. SEAL is provided as is, without any warranty that a label is complete or correct.

Your decisions

You are responsible for your own decisions. Check the evidence on a token’s record, and do your own research before trading.

Third parties

SEAL is independent. It is not affiliated with Hyperliquid, Kinetiq, Elysium or any launchpad unless stated. Their names are used only to describe what SEAL covers.