Dossier

← New launches

Pons launch

$MURKLE Murkle

Launched by 0xa39f…0dab

0xa8aff28dbf02c8783db22e34402df4e8bde63061

ImpersonatorFlagged 11 days after launch
Market cap—
24h volume—
Price—per token, in USD
Bonding curve
—
24h buys / sells
—
Real holders
—

Market numbers come from Orbio and cover Orbio agents only.

Is this $MURKLE the project's token?

No. Not the token @murkledotxyz claims (it claims $ETHMURKLE 0xc8140a3a45…).

An official channel lists a different contract, or says this token isn't theirs.

The project behind the identity it copies hasn't launched a token the index knows of.

Wrong verdict? Report it. A person reads every report, and it triggers a fresh check.

The project

Nothing it points at describes a product yet.

Score

Not scored

Impersonators aren't scored: nothing they point at belongs to them.

Trader’s card

Original or copy

  • First token named $MURKLE. 1 later token reused the ticker

In launch order, coloured by verdict. This one is ringed.

Creator

  • This wallet launched nothing else within a week of this one
  • It hasn't sold out of any of its 1 other launch; 1 was an impersonator
  • Didn't buy at launch

Owner and fees

  • Extra creator fee of 2% on every buy and sell, on top of Pons’s 1%, fixed at launch

From the chain alone: holder counts are real end buyers, not routers or bots, and bots are wallets that buy 10 or more launches a day.

Who it points at

The accounts and sites in the token's own metadata, and whether each one claims this token. Metadata is written by the launcher, so only the claim counts. Dossier reads them throughout a launch's first day. After that it reads them again while people trade the token or look at its file: opening a file last read over a day ago queues a fresh read.

KindLinkClaims it?Last read
X accountx.com/murkledotxyz contradicted claims a different contract
read

Raw data for this file: 0xa8aff28d….json