$LEAK Leak
0x65b11792fcc01337d754a807226757d53954f933
0x65b11792fcc01337d754a807226757d53954f933
Not confirmed. Its X account and website don't list this contract (yet).
Nothing official lists this contract. That isn't proof of a scam, but no one has claimed it.
Wrong verdict? Report it. A person reads every report, and it triggers a fresh check.
Dossier’s readUtility
Tracks trending crypto accounts and surfaces the tokens behind their buzz before it becomes obvious.
An AI summary of what the launcher’s description, the X account and the site say. It describes; the verdict above is what vouches.
See the crypto accounts everyone's watching, understand why they're trending, and catch the tokens behind the buzz — before it's obvious.
The token description, written by whoever launched it.
0/100
Nothing it points at claims it (yet).
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. 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 | leak.me | named
read |
| X account | x.com/leakmealpha | unbound
read |
Raw data for this file: 0x65b11792….json