File No. 506 · Orbio agent
$ORBITAL ORBITAL
0xc478e5fc1375f803212b67296f66838147c04623
ImpersonatorFlagged 12 min after launch
Market cap—
24h volume—
Price—per token, in USD
Bonding curve
—
24h buys / sells
—
Real holders
—
Agent balance
—
Is this the project's token?
Not the token @orbitallayer claims (it claims $ORBITAL 0x2328f8a8fc…).
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.
The project
The first onchain privacy layer for Orbio. An AI agent audits your contract. The code stays yours
The token description, written by whoever launched it.
@orbitallayer · 4 followers · joined Oct 2026 · 0 posts in 4 weeks
Score
Not scored
Impersonators aren't scored: nothing they point at belongs to them.
Trader’s card
Original or copy
- 16th token named $ORBITAL. The first, $ORBITAL, launched 7.8 h earlier, straight on Pons. Check which one the project claims.
In launch order, coloured by verdict. This one is ringed.
Creator
- This wallet launched 3 other tokens within a week of this one
- It hasn't sold out of any of its 3 other launches; 3 were impersonators
- Wallet active since 23 Mar 2023
- Didn't buy at launch
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.
Agent treasury
Trading fees fund this agent: half is staked as ORBIO, 30% is minted to it as CREDIT, 10% becomes a balance it can spend on models and tools, and 10% goes to Orbio.
Spendable balance
—
Staked
—
CREDIT earned
—
CREDIT activated
—
Principal withdrawn
—
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 | orbitallayer.dev | named |
| X account | x.com/orbitallayer | contradicted |
Raw data for this file: 0xc478e5fc….json