31 Pantheons. One real one.

The name is taken before the project launches.

The first token named Pantheon appeared 3 days and 13 hours before the project’s own. By launch day there were 18. 2 of them came from wallets with hundreds of launches each (794, 800): farms that register names in bulk and wait.

The project launches its token.

0x8927…73a3, from 0x930f…2d4c, a wallet that has launched exactly one token. It is number 19 in launch order. Anyone choosing by age would have picked one of the 18 before it.

The copies keep coming.

The next Pantheon came 3.7 minutes later from 0xc292…2a98, a wallet with 285 launches. 9 more followed within three hours, and 12 in all after the project’s launch.

The project’s own website shows one address.

Pantheon’s token links pantheonperps.com and @pantheonperps. SEAL reads the website and the scripts it loads, and finds 0x8927…73a3 there and none of the other 30. That makes it the project’s token. 9 of the copies link pantheonperps.com too, borrowing the real project’s website, but the website does not point back to them.

One token with the name, 0x9863…a14e, links a different website and X account of its own. It may be a separate project that happens to share the name, so SEAL gives it no label rather than call it a copy.

One Likely original, 29 copies.

The real token is Likely original: one of the project’s two channels confirms it. Every other Pantheon from a different wallet is a Copy, and each copy’s answer names the real token, so a platform can offer it instead. These are the API’s actual answers:

{
  "covered": true,
  "label": "Likely original",
  "basis": "The project's website pantheonperps.com shows this contract address. One channel so far: SEAL has not yet checked the project's X account.",
  "rule": "website",
  "identity": { "tokens": 31, "position": 19, "original": "elysium:0x892723bf41f2e1af70adb1ff19036810888473a3" }
}

{
  "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 (0xc292…2a98, a wallet that has launched 285 tokens).",
  "rule": "copy",
  "identity": { "tokens": 31, "position": 20, "original": "elysium:0x892723bf41f2e1af70adb1ff19036810888473a3" }
}

Launch order called the real Pantheon a copy.

SEAL’s first rules picked the earliest token as the original. For Pantheon that meant the project’s own token was labelled a Copy of an older Pantheon from another wallet. The label history keeps every step, and it is why the rules now rest on what the project itself shows:

From Likely original to Original.

The X check is in development. Once SEAL reads @pantheonperps and finds the same address there, the token becomes Original: two channels the project controls, both pointing to it. Until then the label says Likely, and platforms show it as such.