$CRYON Cryon
0xb3d7f4b565136b860c79b575f69df7e8ae0e2f89
0xb3d7f4b565136b860c79b575f69df7e8ae0e2f89
Unlikely. Launched from an impersonator's wallet: the same wallet launched $ORBITAL #506, a confirmed copy.
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.
Cryon is an AI game engine that helps anyone turn ideas into beautiful, playable web games
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. It has collected 212 ORBIO in fees so far.
An agent’s trading fees mint CREDIT to its wallet. Activating CREDIT turns it into compute, so this is $CRYON putting its budget to work, day by day.
$CRYON hasn’t put any of its CREDIT to work yet: its fees have minted 1.47 CREDIT to its wallet.
From the chain: CREDIT’s activations by its agent wallet, every wallet it has had included; a wallet shared with other agents is split by what each one’s fees minted. What it spends after activating only its own account can see. Which agents put CREDIT to work →
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 | app.usecrayon.ai | not checked |
| X account | x.com/usecrayon | not checked |
Raw data for this file: 0xb3d7f4b5….json