Research · 12 November 2026

The state of copies on Elysium.

Every token launched through Elysium’s launchpads, read from the chain and grouped by name. Who launches them, how fast copies follow a real project, and why the earliest token is so often the wrong one.

Data every launch from 2 to 12 November 2026 Snapshot 12 November 2026, 20:24 UTC Source the SEAL engine, read from the chain Download the data (JSON)
74%of launches used a name and ticker that already existed
85%of all tokens came from 6.4% of wallets
5 smedian time from a project’s launch to its first copy
51%of copies were launched before the project’s own token

Three in four launches use a name that is already taken.

Of the 138,053 tokens launched on Elysium so far, 102,622 share their normalized name and ticker with a token that was already there. Case, spacing and lookalike characters are folded together, so PANTHEON, Pantheon and Panthеon with a Cyrillic e count as one name.

Most reuse is not aimed at any project. It is the same handful of names, launched again and again.

Launches per dayEvery token launched through an Elysium launchpad, by day (UTC)
Reused a nameNew name

A few wallets launch almost everything.

SEAL counts a wallet with 4 or more launches as a farm: no project team launches its own token that many times. 1,258 such wallets, out of 19,795 that launched anything, created 117,569 tokens. The busiest one launched 5,527 on its own.

This is why SEAL never treats launch activity as evidence. A farm can launch any name in seconds, before or after the project it imitates.

Farm wallets, as a share of wallets and of launchesFarm: a wallet with 4 or more launches
Farm walletsEveryone else
Share of wallets6.4%
Share of launches85%

Copies arrive in seconds.

5 s

For the 58 projects SEAL has confirmed and that were copied after they launched, the first copy came a median of 5 seconds later. 30 of them were copied within five seconds, often in the same block or the next.

Nobody types a name that fast. Copies are launched by programs that watch for new projects.

Time from a project’s launch to its first copyProjects whose website confirms their token, copied after launch

The earliest token is often a copy.

Of the 323 copies SEAL has labelled, 165 were launched before the project’s own token and 158 after it. Farms take a project’s name as soon as it is announced, so by the time the team launches, the name is already trading.

Any rule that calls the first token the original is wrong about half the time. SEAL’s first rules did exactly that, and it is why they were replaced: see the Pantheon case study.

When copies were launchedCopies of projects SEAL has confirmed
Before the project’s tokenAfter it
165 before · 158 after51% before

Almost nothing launched is a project.

Only 3,953 launches, 2.9% of the total, look like a project: a website and X account of their own, product wording, a team that launches once. The rest are memes, tweet plays and farm output. SEAL labels the project launches and the tokens that copy them, and gives everything else no label.

Among the project launches, SEAL has confirmed 72 through the project’s own website, marked 323 copies, and left 31 unresolved where two teams point to different tokens.

Most copied project namesCovered identities by number of tokens with the name
NameTokensWalletsSEAL
SeedEly $SEED3431Likely original
PANTHEON $PANTHEON3129Likely original
HYPEJAK $HYPEJAK3124Unresolved
Elydex $ELYDEX2119Likely original
OCIA $OCIA1710Likely original
Wick $Wick1515Likely original
Elysium Mail $MAIL1513Likely original
elle $ELLE1413Likely original
Hypermon $HYPERMON1010Likely original
stasy.fun $stasy109Likely original

The biggest name on Elysium has no confirmed token.

By market value, the largest project launch on Elysium is a token named LiquidV, at about $122k with $196k traded in a day, according to DexScreener at the time of this snapshot. 22 tokens on Elysium use the name.

The website those tokens link, liquidv.xyz, shows 6 contract addresses. None of them is any of the 22 tokens. So SEAL gives none of them a label. That is not a verdict against them: it means the project has not pointed to any of them, and SEAL does not guess.

What SEAL shows for LiquidVThe API’s answer for the largest of the 22 tokens
// GET /v1/tokens/elysium:0xd126…7f2d
{
  "covered": false,
  "label": null,
  "basis": "A project launch, but the project's own website does not show this contract address, and SEAL does not read X accounts yet. No label until a channel shows it."
}

One in five project websites is already gone.

SEAL has read 1,824 websites that project launches link. 392 of them, 21%, no longer answer, and 17 send visitors to a different domain. A website is easy to put up and easy to drop, which is why SEAL re-reads them on a schedule, and why one channel alone only ever gives Likely original.

Project websites SEAL has read
Unreachable21%

392 unreachable · 17 moved to another domain · 1,415 answering

How these numbers were made

Definitions and limits.

Every figure on this page is computed by engine/research.py from SEAL’s database and published as one file: research.json. Market values come from DexScreener at the time of the snapshot and change constantly.

LaunchA token created through an Elysium launchpad, read from the chain since the first launch on 2 November.
NameThe normalized name and ticker together. A shared ticker alone does not make two tokens the same name.
Project launchA token SEAL’s project filter accepts: its own website or X account, no farm wallet, no meme or tweet-play wording.
ConfirmedThe project’s own website shows the token’s contract address. The X check is in development, so no token is Original yet.
First copySeconds from the confirmed token’s block time to the first later token with the same name from a different wallet.
LimitsThe project filter can miss real projects or let some memes through, and websites change. The numbers describe what SEAL saw, not every intention behind a launch.

See it on one project.

How SEAL found the real Pantheon among 31 tokens with the name.

Read the case study