$UNCANNY uncanny
0x98c4a58f452f81f234538eac55c4ca056de35a15
0x98c4a58f452f81f234538eac55c4ca056de35a15
Unlikely. Launched from an impersonator's wallet: it was funded through the same chain of wallets that launched $COMD #1996 and 2 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.
launch an ai influencer with its own coin. it posts on its own and the trading fees pay for its content. robinhood chain.
The token description, written by whoever launched it.
Not scored
Impersonators aren't scored: nothing they point at belongs to them.
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. 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.
| Kind | Link | Claims it? |
|---|---|---|
| Website | useuncanny.fun/coming-soon | named
read |
| X account | x.com/useuncanny | named
read |
Raw data for this file: 0x98c4a58f….json