Robinhood Chain · $ORBZ

Use it,
or it burns.

Trading fees pay for your AI every hour. Credits you skip for a week burn $ORBZ.

[ simulation of the mechanism ]

  • fresh credit
  • aging
  • last hours of the fuse
  • spent on AI

Epoch clock · pre-launch

--:--:-- UTC · next hour in --:--

Grants land every hour on the hour, from epoch 0 at launch.

Hold $ORBZ and one key opens every major AI model. Your credits arrive every hour, paid by trading fees. Whatever you leave unused for seven days buys $ORBZ back and burns it, on-chain, with a receipt.

Follow the build

Contract address · $ORBZ

pre-launch

Not launched yet.

$ORBZ has no contract address yet. When it launches, the address appears here and on our own channels, nowhere else. Anything claiming to be $ORBZ before then is not us.

Where it will trade

Launchpad soonGMGN soonDEX Screener soonExplorer soonRelay soon

Verify the address here and on our official channels before you buy. Fake contract addresses spread in the first hour of every launch.

Credits granted
$0

starts at epoch 0

$ORBZ burned
0

first burn: launch + 168h

Current epoch
—

one per hour after launch

Chain tip
…

Robinhood Chain, read live

Honest zeros: nothing has been granted, spent or burned because $ORBZ has not launched. The first three go live with epoch 0; the chain tip is the real block, read from the chain in your browser.

Why Orbz

The first fee-to-credit tokens proved the demand. Then the data showed the leak.

Paying holders in AI credits works as a story. The trouble starts when you ask what happens to the credits nobody uses.

13–18%

of issued credits ever spent on inference

The other 82–87% was listed for sale below face value.

An incumbent's own public analytics, read on 29 September 2026.

Fig. 1Share of issued credits ever spent on inference, from an incumbent's own public analytics, read on 29 September 2026.
  1. 1

    AI is a monthly bill

    Seats, API keys, top-ups, overages. For anyone who builds with AI, the bill only goes up.

  2. 2

    Token utility is usually a sticker

    Holding a coin rarely changes anything a holder does on an ordinary Tuesday.

  3. 3

    Idle credits become sell pressure

    When most credits go unused, holders sell them below face value. Holders get paid in something they dump.

  4. 4

    Five moving parts

    Stake one token, mint a second, list it on a book, settle in a stablecoin, activate it into a balance. Most people leave at step two.

Where does the unused value go?

Every credit token has to answer that question, and there are only two answers. Pay it out as a sellable token, and idle credits become sell pressure. Burn the project token with it, and idle credits become buy pressure. Orbz takes the second answer and makes it automatic.

  • pay it out as a token

    ↓ sell pressure

  • burn $ORBZ with it

    ↑ buy pressure

Fig. 2Where unused value can go. There are only two roads, and Orbz takes the second.

Them and us

  • Credits nobody uses sit in wallets

    Unused credits buy back and burn $ORBZ after 7 days

  • Idle credits are dumped on a book at up to 30% off

    Nothing is dumped: idle value becomes buy pressure

  • Stake, mint a second token, list it, settle, activate

    One token. Hold it and the credits arrive

  • AI subscriptions: $20 a seat, used or not

    No subscription, no top-up needed while you hold

  • Prepaid gateways keep your unused balance

    Unused value goes back to every holder as a burn

  • Reserves you have to take on trust

    Public vault, public receipts, burns anyone can trigger

Orbit

From one trade to your editor, or into the burn.

Eight stations, one loop, every hour. Nothing in it waits on a person.

Fig. 3The fee's ring. Eight stations and one ember. Click a station, or let it run.

Station 01 of 08

Someone trades $ORBZ

2% per trade

The launchpad charges 2% on every buy and sell: its 1% base fee plus the Orbz 1% creator tax, fixed at launch and immutable.

Decay

Every credit carries a countdown.

Spend it and it becomes AI. Leave it, and at hour 168 it becomes a buyback. Drag the hour to watch one credit's life.

hour 0 of 168

$1.00

spendable

spent on AI
$0.00
bought + burned
$0.00
spent on AI ↑
0hd1d2d3d4d5d6d7
Fig. 4One credit's life, hour 0 to 168. Drag the hour.

Oldest first

Grants are spent in the order they arrived, so a holder never loses a fresh credit to an old fuse. The dashboard shows every bucket with its own countdown.

  • Not transferableA credit is tied to the wallet that received it.
  • Not cashIt buys model usage. It is never redeemable for ETH, USDG or anything else.
  • Not revivableAn expired bucket is already buying $ORBZ. It does not come back.

Three buckets, oldest first

Sample dashboard
  • $3.10burns in 6h
  • $4.20burns in 2d 4h
  • $7.32burns in 6d 19h
Fig. 5Seven marble credits on the rail. The last one is on fire.

Nobody's allocation is wasted.

Almanac

The same arithmetic the vault runs, printed as a tape.

Turn a dial and the tape re-prints. Every figure comes from the locked fee split, not from a guess. Switch to the sample to see what a real epoch's receipt will look like.

Daily $ORBZ volume$100,000
Your $ORBZ1.0M $ORBZ

above the 100k floor: grants apply

Supply held by eligible wallets55%

the curve, pool, vault, treasury and burn address never count

Share of credits holders actually spend15%

incumbent data suggests 13–18%

Fig. 7Four dials. The tape is the answer.
ORBZ · DAILY MODELmodel
  • volume traded$100,000
  • traders pay 2%$2,000
  • launchpad keeps$300
  • vault receives 1.7%$1,700
  • treasury 30%$510
  • credit pool 70%$1,190
  • your share 0.18%
  • credits per hour$0.09
  • credits per week$15.15
  • the pool at 15% spend
  • becomes AI$179
  • buys and burns $ORBZ$1,012

reserves check: vault = open credits

A model, not a forecast. Grants follow real volume, hour by hour, and are never promised.

USDG in OrbzVault

$0.00

Open credits in every dashboard

$0.00

Pre-launch, both sides are zero. After launch this page reads the vault balance straight from the chain every block.

  • 01

    Pre-funded

    A grant is written only after its USDG is in the vault. No IOUs, ever.

  • 02

    Two exits only

    Vault USDG can pay a model provider for used credits, or buy and burn $ORBZ. Nothing else.

  • 03

    Checkable

    Every settlement carries a Merkle root of the requests it pays for, so usage can be verified later.

Burn

Three pipes feed the burn.

All three use one public path: USDG to ETH to $ORBZ, then burn(). Total supply drops by exactly the amount burned, and every burn prints a receipt.

  1. 1

    Expired holder credits

    from launch + 168h

    Every epoch past hour 168 burns whatever is left in it.

  2. 2

    Paid top-up margin

    V2

    Non-holders will pay list price + 5%. The 5% buys and burns $ORBZ.

  3. 3

    Idle treasury budget

    V2

    Demo budget the funnel did not use can be routed into the same burn.

$ORBZ burned so far

0

pre-launch

Nothing has expired, because nothing has been granted yet. The first burn happens 168 hours after launch.

// callable by anyone once epoch + 168h has passedOrbzVault.burnExpired(epoch)  → swap remainder USDG → ETH → $ORBZ    (reverts if price is > 3% off the 30-min TWAP)  → $ORBZ.burn(amount)      // totalSupply drops  → tip the caller 0.25%, capped at $2

Our keeper calls it every hour. If it ever stops, a stranger can call it and collect the tip. Nobody can stall a burn.

Fig. 8The burn path, in the lines that matter.

Nobody can stall a burn, including us.

Gravity

Hold it. That's the whole setup.

No staking, no locking, no second token. The token buys access, never priority: every holder's credit is worth the same $1.00 of usage, and grants are strictly pro-rata.

Holding ruler

1.7M $ORBZ · Ring

Visitor

0

Orbit

100k

Ring

1.0M

Sun

10M

Fig. 9Where a bag lands on the ruler. Slide to try one.
  • Visitor

    hold 0

    • 20 demo messages a day on a small model
    • Receipts, reserves and docs
  • Orbit

    100,000 · 0.01%

    • Hourly credit grants, pro-rata
    • 60 requests / min, 8 concurrent
    • Usage dashboard and fuse view
  • Ring

    1,000,000 · 0.1%

    you'd be here

    • Everything in Orbit
    • 120 requests / min, 16 concurrent
    • Ring badge on share cards
  • Sun

    10,000,000 · 1%

    • Everything in Ring
    • 240 requests / min, 32 concurrent
    • First look at new models
    • Name on the holder wall

Tiers raise rate limits and unlock cosmetic badges. They never change what a credit is worth or how grants are split.

What $ORBZ never does

  • Pay out cash, ETH or stablecoins to holders
  • Make one holder's credit worth more than another's
  • Need staking, locking or a second token
  • Let the team move the credit pool: vault USDG can only pay a provider or buy-and-burn
  • Promise a fixed amount: credits track real volume

Contract facts

Supply
1,000,000,000 $ORBZ, fixed, no mint
Launch
100% fair launch on the Robinhood Chain launchpad bonding curve
Graduation
4.2 ETH on the curve, then a Uniswap v4 pool
Team allocation
None. No presale, no private round
Dev buy
At most 2% of supply, wallet disclosed before launch
Trader fee
2%: the launchpad's 1% base fee + 1% creator tax
Creator tax
1%, fixed at launch, immutable
Fee recipient
OrbzVault: no owner, no upgrade, source verified
Grant floor
100,000 $ORBZ held (0.01% of supply)
Chain
Robinhood Chain, chainId 4663

Fee split

Per $100,000 traded, to the cent.

Trading fees are the engine. Two later streams feed the same burn margin.

per $100,000 traded

Traders pay 2%$2,000
OrbzVault$1,700
Launchpad$300
Credit pool 70%$1,190
Treasury 30%$510
Becomes AI$179
Buys + burns$1,012
Fig. 10Where $100,000 of trading goes. Tune how much holders spend.
  1. 1at launch

    Trading fees

    0.7% creator share of the base fee + 1% creator tax: 1.7% of every trade reaches OrbzVault, before and after graduation.

  2. 2V2

    Paid top-ups

    For people who do not want a token: list price + 5% in ETH or USDG. The 5% buys and burns $ORBZ.

  3. 3V2

    Agent and team plans

    Shared pools with sub-keys and spend caps, on the same 5% burn margin.

Treasury 30%

  • Operations35%

    servers, indexing, monitoring

  • Provider float20%

    prepaid balance, so credits never wait

  • Free demo15%

    the chat on this page, capped by budget

  • Growth20%

    creators, dev communities, bounties

  • Reserve10%

    reviews, incident fund

Published monthly on the reserves page, with transaction links.

Clockwork

One ownerless vault, six small services around it.

The chain holds the money and the rules. Our servers only meter, allocate and publish, and every step they take leaves a public trace.

The full drawing opens on a larger screen. The parts, in order, are listed below.

Robinhood Chain

Money and rules

  1. 1

    Launchpad escrow

    Creator fees wait here until harvest() pulls them.

  2. 2

    OrbzVault

    The USDG pool per epoch. harvest · withdrawForUsage · burnExpired. No owner, no upgrade.

  3. 3

    $ORBZ and its pool

    Where trades happen and where every burn lands.

Orbz servers

Meter, allocate, publish

  1. 4

    Indexer

    Reads $ORBZ transfers block by block into balance timelines.

  2. 5

    Allocator

    At :00 every hour: time-weighted shares, then grants.

  3. 6

    Gateway

    Keys and metering: reserve, call, settle, oldest credits first.

  4. 7

    Settlement

    Pays providers for used credits, with a usage Merkle root.

  5. 8

    Keeper

    Calls harvest() and burnExpired() every hour.

  6. 9

    Publisher

    Prints the hourly receipt row and image.

Outside

Holders and providers

  1. 10

    Holders and editors

    Sign once, paste the key, keep working.

  2. 11

    Model providers

    Every major model family, list prices re-read every hour.

base_url = https://api.orbz.app/v1api_key  = sk-orbz-…   # signed by your wallet, no transaction

Chat-completions compatible: the tools you already use keep working with a new base URL and key. The API opens at launch.

Safeguards

Tested on a mainnet fork before a single real dollar arrives.

Seven invariants hold in every test run, and the gaming playbook is closed before launch.

  1. I1vault USDG equals the sum of open epoch remainders
  2. I2usage withdrawn from an epoch never exceeds what it booked
  3. I3burnExpired reverts before hour 168
  4. I4a burned epoch can never be withdrawn again
  5. I5every harvest splits exactly 70 / 30
  6. I6swaps revert beyond 3% of the 30-minute TWAP
  7. I7total supply drops by exactly the amount burned
Fig. 12Seven invariants. Each holds in every test run on a mainnet fork.

Attack · defence

  • Buy right before the hour, sell right after

    Time-weighted balances: five minutes of holding gets 1/12 of the hour's share.

  • Wash trading to farm grants

    A round trip costs 4% in fees and only part of it returns, pro-rata to every holder. Always a loss.

  • Splitting a bag across wallets

    Pro-rata math gains nothing from splitting, and the 100,000 floor keeps dust out.

  • Sharing an API key

    Allowed. It spends the owner's own credits.

  • Junk requests to dodge the burn

    Provider cost is real money: junk only moves value from the burn to the provider.

  • A compromised operator key

    It can only pay one fixed settlement address, capped per epoch, and a guardian can freeze it.

  • The indexer falls behind

    Grants pause. The allocator never guesses a balance.

Security model

  • Holders never deposit anything to receive credits
  • API keys are stored as hashes; rotation takes a new signature
  • The keeper key holds only ETH for network fees, and every call it makes is permissionless anyway
  • Fail-closed: if settlement fails, spending pauses

Your AI bill

Badges for using it. Walls for burning it.

Both paths are celebrated, and none of it touches allocation, rate or price.

Orbz
Sample card

My AI bill this month

$38.40

of AI used

$0

paid

$ORBZ · Use it, or it burns.

Every wallet gets this card once a month, ready to post. The product is the ad.

  • Spark

    First credit spent

  • Full Orbit

    Credits spent seven days in a row

  • Ember

    Idle credits fed ten burns in a month

  • Night Shift

    1,000 requests between 00:00 and 06:00 UTC

  • Ring · Sun

    Tier held through a full calendar month

  • Free-AI board

    at launch

    Top wallets by AI used at zero cost, from settled usage only.

  • Ember wall

    at launch

    Top wallets whose idle credits fed the most burns this month.

First light

From the first sketch to the first burn.

Five phases from the first sketch to the first burn, and the first week drawn as one turn of a dial.

D1D2D3D4D5D6D7T+24hT0 launch · T+168h first burn168hours · one turn
Fig. 13One turn of the dial is one fuse. Launch and the first burn are the same mark.

Launch day, hour by hour

  1. T-24h

    the fuse animation and the vault address

  2. T-1h

    contract source and fork test report

  3. T0

    launch; the vault is the fee recipient

  4. T+1h

    first harvest, first epoch, first grants

  5. T+2h

    first receipt printed

  6. T+24h

    day-one report: volume, fees, grants, usage

  7. T+168h

    FIRST BURN: epoch 0 expires, live

Five phases

  1. Phase 0

    done

    Foundation

    • Mechanism locked: hourly credits, 7-day fuse, burns
    • Name, logo and brand kit
    • Blueprint and this page
  2. Phase 1

    building now

    MVP

    • Gateway: keys by signature, metering, oldest-first grants
    • Indexer and allocator on a mainnet fork
    • OrbzVault fork-tested against all seven invariants
    • Keeper, publisher, receipts and reserves pages
  3. Phase 2

    next

    Launch

    • Vault is the fee recipient from block one
    • Hourly receipts and the first-burn countdown
    • $0 AI bill cards, boards and badges
    • Editor integration server and paid top-ups
  4. Phase 3

    later

    Scale

    • Sub-keys with spend caps for teams and agent fleets
    • Web search and page reads on the same credits
    • Redundant providers with automatic failover
    • Third-party security review of OrbzVault
  5. Phase 4

    later

    Ecosystem

    • Orbz keys as a payment rail inside other apps
    • Fee-to-credit partnerships with Robinhood Chain projects
    • Agent SDK with budget planning built in

Design choices

Every number has a reason.

  • Creator tax 1% (traders pay 2%)

    A round trip stays near the incumbent's cost, and the vault still gets 1.7% of volume.

  • 70% credits, 30% treasury

    Most of the fee goes back to holders, as AI or as burns.

  • 168-hour expiry

    Long enough for weekly users, short enough to burn often.

  • Vault on-chain from day one

    The burn has to be provable, not promised.

  • One token, no staking

    Complexity is the incumbent's weakness. Hold means done.

  • Credit pool in USDG

    A credit's dollar value never drifts with ETH.

  • Oldest credits first

    Holders never lose a fresh credit to an old fuse.

  • List price, no markup

    A credit is worth exactly what it buys.

  • Time-weighted + 100,000 floor

    Ends flash holds and dust wallets.

  • Permissionless burn + tip

    Nobody can stall a burn, including us.

  • No pay-in-token discount

    A bonus paid for a burned token would be funded by nobody.

  • Product live before the token

    Ship the product, then the curve.

Six-dimension moat

  1. 1

    The honest mechanism

    Idle credits burn instead of being dumped. Most credits go idle, so the burn is the product working.

  2. 2

    One token, zero setup

    Hold it and credits arrive. Simplicity is a moat when the competition needs a diagram.

  3. 3

    Provable reserves

    Every credit on every dashboard is backed 1:1 by USDG in an ownerless vault.

  4. 4

    Built-in distribution

    $0 AI bill cards and hourly receipts turn every user and every hour into content.

  5. 5

    Switching costs

    Keys live inside editors, agents and apps. Once a workflow runs on an Orbz key, it stays.

  6. 6

    First to the phrase

    "Use it, or it burns" is the mechanism. Anyone copying it reads as a copy.

What we watch

  • Daily volume and fees harvested
  • Credits granted, used and burned per day
  • Utilization, 7-day rolling
  • Wallets at or above the floor, and wallets with an active key
  • Requests per day and the latency we add
  • $ORBZ burned and the supply change
  • 7-day key retention

What we ignore

  • Follower counts
  • Price targets
  • Anything we cannot show on a receipt

Straight talk

What works, and what could hurt.

What works

  • Credits are pre-funded in USDG: no debt, no promised amount, nothing to run on
  • Idle value burns the token instead of becoming sell pressure
  • One token and one key: the whole product fits in a sentence
  • Burns are permissionless and every hour prints a receipt
  • Credits spend at list price, so a credit is worth exactly what it buys

What could hurt

  • Grants follow volume. If trading fades, every hourly grant shrinks with it
  • The launchpad's operator keeps a timelocked power to redirect creator fees. We watch for that event and will alert publicly within minutes
  • Metering runs on our gateway, and usage is reported by an operator key: bounded per epoch, freezable, with Merkle roots, but still trust
  • Model providers can change prices or access; we keep more than one
  • At launch the vault is fork-tested, not externally reviewed; that review is in Phase 3
  • An incumbent can copy the burn. Our answer is being live first with the simpler design

Questions, briefly

What do I get for holding $ORBZ?

AI credits every hour, paid by trading fees, spendable on every major model through one API key. You need at least 100,000 $ORBZ, and your share is pro-rata to your time-weighted balance.

Is this cash or a return?

No. A credit is a grant of product access to model usage. It is not transferable, not redeemable for cash or any digital asset, and never a fixed amount.

What happens to credits I don't use?

Each credit lives 168 hours. After that, whatever is left in its epoch buys $ORBZ on the market and burns it. You still gain from it through the supply drop.

Who triggers the burns?

Anyone. burnExpired(epoch) is permissionless after hour 168 and pays the caller a 0.25% tip, capped at $2. Our keeper calls it every hour.

Where does the money sit?

In OrbzVault, in USDG, booked per hourly epoch. It can only pay a model provider for used credits or buy and burn $ORBZ.

Which models can I use?

Every major model family, at each provider's list price, through one chat-completions compatible API. The catalogue page lists them with prices.

Do I need to stake or lock anything?

No. Hold $ORBZ in your own wallet, sign one message to create a key, and the credits arrive on their own.

Can I buy credits without the token?

Paid top-ups arrive in V2: list price + 5% in ETH or USDG, and the 5% buys and burns $ORBZ.

When does it launch?

After the MVP is live and the vault passes its fork tests. The product ships first, then the token.

Use it, or it burns.

Everything you spend becomes AI. Everything you skip becomes a burn. Nothing sits idle.