$PEDIGREE PedigreeWTF
0x99f8f0e2f3b2811d11ce26faf2189665cafd7ff4
0x99f8f0e2f3b2811d11ce26faf2189665cafd7ff4
Launched from an impersonator's wallet: it was funded through the same chain of wallets that launched $LUDI #1126 and 36 other confirmed copies.
Launched from a wallet, or a chain of wallets, that also launched a confirmed copy of a real project. Its own project hasn't claimed it.
Wrong verdict? Report it. A person reads every report, and it triggers a fresh check.
Every dev has a pedigree. Every new coin on Pons, tagged by the record of the wallet that launched it: how many coins, how many graduated, how far the best one got. Read straight from the chain.
The token description, written by whoever launched it.
Not scored
Impersonators aren't scored: nothing they point at belongs to them.
In launch order, coloured by verdict. This one is ringed.
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.
Trading fees fund this agent: half is staked as ORBIO and earns CREDIT, 30% is minted to it as CREDIT, 10% becomes a balance it can spend on models and tools, and 10% goes to Orbio.
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.
| Kind | Link | Claims it? |
|---|---|---|
| Website | pedigree.wtf | named |
| X account | x.com/pedigreewtf | unbound |
Raw data for this file: 0x99f8f0e2….json