File No. 111 · Orbio agent
$OCCLUS OCCLUSION NETWORK
0x5f677b1bb30eea51eb6fd37e5d0dd86cddf6d123
ImpersonatorFlagged 2 days after launch
- Market cap
- —
- Change
- —
- 24h volume
- —
- 24h buys / sells
- —
- Price
- —
- Curve
- —
- Real holders
- —
- Agent balance
- —
Is this the project's token?
Not the token @use_occlusion claims (it claims $OCLU 0x449ca622a0…).
An official channel lists a different contract, or says this token isn't theirs.
The project
Occlusion shields solver intents using a note-commitment scheme derived from Zcash's Orchard protocol. A Bittensor subnet audits the public trace after every execution for anything that still leaked
The token description, written by whoever launched it.
Score
Not scored
Impersonators aren't scored: nothing they point at belongs to them.
Creator and safety
- Only launch by this wallet around this time
- Creator didn't buy at launch
Holder counts are real end buyers, not routers or bots.
Agent treasury
Trading fees fund this agent: half is staked as ORBIO and earns CREDIT, and 45% becomes a balance it can spend on models and tools.
- Spendable balance
- — USDG for inference and tools
- Staked
- — —
- CREDIT earned
- — owed plus claimed
- CREDIT activated
- — spent into the gateway balance
- Principal withdrawn
- — taken out of the stake
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.
| Kind | Link | Claims it? |
|---|---|---|
| Website | occlusion.network | contradicted |
| X account | x.com/use_occlusion | contradicted |
Raw data for this file: 0x5f677b1b….json