$CLOAK Cloak CapitalAI
0xd373e3fda9bf39ca2de55e7152fef4961105f386
0xd373e3fda9bf39ca2de55e7152fef4961105f386
No. Not the token @cloakcapitalai claims (it claims $CLOAK 0xcc4556bed2…).
An official channel lists a different contract, or says this token isn't theirs.
Wrong verdict? Report it. A person reads every report, and it triggers a fresh check.
Stock tokens. Research. Onchain execution. Built on Robinhood Chain. Planning to launch on @Orbiodotso . Your market, Your business.
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. 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 | cloakcapital.ai | unbound
read |
| X account | x.com/cloakcapitalai | contradicted
read |
Raw data for this file: 0xd373e3fd….json