Robinhood Chain · paired against tokenised NVDA

Fees in.
Hours out.

Every WARP buy and sell pays a 3% fee. Two thirds of it — the creator tax — is priced in dollars off the Chainlink NVDA feed and spent on RTX 5090 capacity. Once an hour that capacity is divided among holders as compute credits, measured in 5090 hours and fixed at the price of the hour they were credited.

Follow on X
settlement every hour· next in · this hour buys · 5090

Trading fee
3% per trade
2% creator tax, 1% Pons. On buys and on sells.
Funds compute
The creator tax
Two thirds of the fee. Nothing is minted to pay anyone.
Settlement
Every hour
Wallets holding 1,000 WARP or more are eligible.
You receive
RTX 5090 hours
Access to a machine. Not cash, not a rate.
01 · The loop

How trading funds compute.

Four steps, and none of them mint anything. The only inflow is a fee somebody already paid on a trade that already happened, and the only thing it ever buys is time on a graphics card.

The split

For every dollar traded.

Trading fee · 3%$2.00
Holder compute · 2%$1.00
Pons & operations · 1%$1.00
Bought at $0.89/hour1.12 h
Equivalent timeabout 1 h 07

        

The fee is charged in NVDA and converted at the Chainlink feed price, so the dollar figure is the same number the purchase is made against. Two thirds of it leaves as compute. The remaining third is not a rake on your credits — it never enters the compute pool at all.

02 · The estimate

Work out your own share.

Arithmetic on numbers you type. Not a rate, not a projection, and not read from anywhere. It opens at zero because nothing has traded yet — move the sliders and it works the rule through, including when the answer is close to nothing.

$120k
$0.89
Your compute · per 30 days
0.00RTX 5090 hours
about 0 min
Fees collected$0
Of which buys compute · 2%$0
Hours purchased, all holders0
Your share of eligible supply0%
Per hourly settlement0.000 h
Per 1,000,000 WARP held0.00 h

Nothing has traded yet, so the estimate starts at zero. Put in a balance and a market above and it works the rule through for you. The $0.89 is the going rate for a 5090 hour, not a figure of ours.

An estimate, not a fixed rate. What you actually receive depends on trading volume, on eligible supply at each snapshot, and on the 5090 price at the hour you are credited. Credits are access to compute — not cash, and no amount is guaranteed.

03 · The runtime

Two ways to spend an hour.

Claim credits from your ledger to create a key. The gateway speaks the OpenAI chat protocol, so an existing application needs a different base URL and nothing else. For work that wants the whole machine, the same credits launch a pod with a shell on it.

The gateway

Send the key as a bearer token. The seconds a request occupies a GPU are deducted from its balance.

curl https://gateway.warp.example/v1/chat/completions \
  -H "Authorization: Bearer $WARP_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"qwen2.5-7b","messages":[{"role":"user","content":"hello"}]}'
  • OpenAI-compatible — change the base URL, keep the SDK
  • each key holds up to 40 RTX 5090 hours
  • keys are revocable; revoking detaches a balance, never burns it
  • anyone with the key can spend it — keep it private

The pod

A whole 5090 with SSH. Bring an image, mount a volume, and it bills by the second it is up.

warp pod create --gpu 5090 --image pytorch:2.6-cu126
→ pod-9f2a1c  starting…  ready in 34s

ssh pod-9f2a1c@ssh.warp.example
→ NVIDIA GeForce RTX 5090 · 32GB · driver 570.xx
  • root shell, persistent volume, your own container
  • a stopped pod bills nothing
  • same credits, same ledger, different surface
04 · The variables

What sets your allocation.

Your compute is not fixed, and three things decide it. None of them is a dial anyone here can turn.

a

Trading volume

More volume collects more fees, so more capacity is purchased. A quiet month purchases little, and the split divides little.

b

Eligible supply

Capacity is divided across all eligible WARP. Your portion is your share of that supply at each hourly snapshot — not of total supply.

c

The 5090 price

When the price rises, each dollar buys fewer hours. When it falls, more. Hours already credited never change — they are fixed at the price of their hour.

Parameters

What is fixed, and what floats.

ParameterValueMoves?
Trading fee3% on buys and sells — 2% creator tax, 1% PonsNo
Holder allocationThe creator tax · two thirds of collected feesNo
Pons & operationsThe Pons fee · one third of collected feesNo
Minimum balance1,000 WARPPublished if it ever does
Balance snapshotOnce per hourPublished if it ever does
Pricing feedChainlink NVDANo
RTX 5090 priceUpdated weekly · hours fixed when creditedYes
Credit expiryNoneNo
Credit transferNot transferable between addressesNo
Key capacityUp to 40 RTX 5090 hours per keyPublished if it ever does
NetworkRobinhood Chain · 4663No
Tokens minted for rewards0 — compute is funded by fees, not issuanceNo

Selling changes your allocation from the next hourly snapshot onward. Compute already added to your ledger stays there. Nothing is staked, so nothing has to be unstaked, and there is no exit queue because there was never an entry.

05 · Questions

The ones people actually ask.

Documentation

How a trade becomes an hour.

Everything the system does, in the order it does it. If a sentence here and a number anywhere else disagree, this page is the one that is wrong, and it gets fixed.

The fee

WARP trades against tokenised NVDA on a Pons curve. Every buy and every sell pays 3% of its value, charged in NVDA. That 3% splits two ways: a 2% creator tax, which is the only thing that funds holder compute, and a 1% Pons fee, which funds the launchpad and operations.

Per side, not per round trip

A round trip is two events and the curve charges each. Someone who buys and later sells has paid twice. The headline number is the one people quote; the effective number is the one people feel, so both are printed.

The creator tax is the only inflow to compute. No tokens are issued to fund it, there is no treasury of WARP to sell, and there is no emission schedule. If nobody trades, nothing is collected and the hourly settlement divides zero.

Buying capacity

The 2% creator tax arrives in NVDA. It is priced in dollars using the Chainlink NVDA feed, so the figure the purchase is made against is the same figure anyone else can read, and it is then spent on RTX 5090 capacity at the current rate.

The 5090 price is updated weekly. Hours are fixed at the price in effect when they are credited — a later price change does not revalue an hour already in your ledger, in either direction.

Why compute and not cash

Paying holders cash in proportion to their holdings is the shape of a security nearly everywhere anyone is reading this. Compute is a good: you receive access to a machine, priced at what the machine costs. That distinction is not a wrapper around the same thing — it is the load-bearing wall of the entire design, and everything else is built to keep it true.

The hourly settlement

Once per hour, every wallet holding at least 1,000 WARP is recorded, and the capacity purchased in that window is allocated by each wallet's share of eligible WARP — the sum of balances at or above the threshold, not total supply.

Wallets under the threshold are not in the denominator. They neither receive nor dilute.

Why a snapshot rather than a stream

A balance that flickers inside the hour cannot be paid twice, and the arithmetic can be checked afterwards against a block. An hour is short enough that buying in does not mean waiting a week, and long enough that the distributor is not writing constantly.

Nothing is staked. No deposit, no lock-up, no escrow, no approval to sign. Balances are read at a block and left alone. Sell in the same minute if you want — you are simply not in the next snapshot, and what is already in your ledger stays there.

Eligibility

The threshold is 1,000 WARP, measured at the snapshot block. It exists so the ledger is not filled with wallets owed a millionth of a second, which costs more to record than it is worth.

There is no upper cap and no tier ladder. A wallet holding a hundred times more receives a hundred times more, because the allocation is a proportion and dressing it up as anything else would be a lie about what proportion means.

The ledger

Credits accrue to your address, denominated in RTX 5090 hours. They do not expire. They are not pushed anywhere. They are not transferable between addresses. They stay in the ledger until you claim them onto a key.

Keys

Claiming attaches credits to an API key. Each key holds up to 40 RTX 5090 hours. You can hold several, name them, and revoke any of them — revoking detaches a balance, it never burns one.

Anyone holding a key can spend its balance. There is no second factor on a bearer token. Treat it the way you would treat any other API key with money behind it.

The gateway

The gateway speaks the OpenAI chat protocol. If your application already talks to that shape of API, changing the base URL and the key is the whole integration.

curl https://gateway.warp.example/v1/chat/completions \
  -H "Authorization: Bearer $WARP_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"qwen2.5-7b","messages":[{"role":"user","content":"hello"}]}'

The seconds a request occupies a GPU are deducted from the key's balance. There is no card on file, no minimum and no monthly commitment, because there is nothing to bill — you are spending an hour a trade already paid for.

Pods

A pod is a whole 5090 with a root shell. Choose an image, it boots, you SSH in, and it bills by the second it is running.

warp pod create --gpu 5090 --image pytorch:2.6-cu126
ssh pod-9f2a1c@ssh.warp.example

A stopped pod bills nothing, and a persistent volume survives a stop so you are not re-downloading weights each session. Pods are the right surface when you want the card rather than an endpoint — training, a custom kernel, anything the gateway's model list does not cover.

What credits are not

They are not cash and cannot be redeemed for it. They are not transferable. They are not a yield, an APY, a dividend, or a claim on revenue. Nothing about them is minted, and none of them is an NFT.

They are a prepaid balance on a machine, funded by fees somebody already paid. The amount depends on trading volume, on eligible supply, and on the price of a graphics card — and all three can move to a level where the answer is close to nothing.

No APY appears anywhere on this site. Not in the docs, not in the estimator, not in a post. A rate implies a promise about the future and there is no mechanism here that could keep one.

Risks, stated plainly

Volume is the only inflow

A quiet month collects little and purchases little. That is the design working exactly as written, not a failure.

GPU prices move against you

The same tax buys fewer hours when 5090 rental gets more expensive. You are exposed to an input cost nobody here controls.

The venue holds a lever

A launchpad can generally redirect its own share of trading fees by an owner action on its factory. Where that is true it belongs here, with the notice period and who can execute it, rather than in a contract nobody reads.

The compute has to actually exist

An hour is only worth something if the gateway and the pods are up. That is an operational dependency on real machines, and it is the part of this system that is not on a chain and cannot be.

Glossary

TermMeans
Creator taxThe 2% of each trade that funds holder compute. Two thirds of the 3% fee.
Pons feeThe remaining 1%. Funds the launchpad and operations. It never enters the compute pool.
Eligible WARPThe sum of all balances at or above 1,000 WARP at the snapshot block.
SettlementThe hourly allocation of purchased capacity to eligible wallets.
CreditOne unit of prepaid compute, denominated in RTX 5090 hours, fixed at the price of its hour.
ClaimAttaching credits from your ledger to an API key. Your action.
GatewayThe OpenAI-compatible endpoint credits are spent through.
PodA dedicated RTX 5090 with SSH, billed by the second while running.
About

Why it is built this way.

Most tokens that promise holders something either print the thing they are promising, or pay it in cash and hope nobody asks what that makes it. This does neither, and the whole design falls out of refusing both.

It converts, it does not issue

No WARP is minted to fund compute. There is no emission schedule because there is nothing to emit — the only inflow is a fee on trades that already happened.

That makes the payout small when the market is quiet. It also makes it impossible for the payout to be a lie, because there is no printer to hide behind.

Compute instead of cash

Cash paid to holders in proportion to their holdings is the shape of a security, and pretending otherwise has ended badly for a long list of projects.

Compute is a good. You get access to a machine at what the machine costs. Different in kind, not in packaging.

Nothing leaves your wallet

No staking contract, no lock-up, no escrow, no approval. Balances are read at a block. Selling costs you the next snapshot and nothing that is already yours.

The floating parts stay visible

Volume, eligible supply and the 5090 price all move, and all three decide what you get. None is smoothed into a headline or expressed as a rate — the estimator asks you for them so the answer is yours, not marketing.

The moving parts

PieceStateWhat it means for you
Fee → computeAutomaticNo action from you. The tax is spent as it is collected.
SettlementHourlyBalances are read at a block. Nothing is staked.
WalletRead onlyReads an address and a chain id. Never asks you to sign or approve anything.
CreditsNon-transferableAttached to the address that earned them, and the keys it creates.

Not investment advice, and not an offer of securities. This describes a mechanism. It promises no return, prints no rate, and what it allocates is access to compute — an amount that depends on trading volume, eligible supply and the price of a graphics card, all of which can fall to where the answer is nothing.

Brand

The mark, the palette, the cards.

A graphics card seen head-on: the board, two fans, the bracket tabs, the PCIe fingers down the left edge. It is the thing the whole protocol buys, drawn small enough to be a favicon.

01 · Lockups
WARP
Primary · on void
WARP
On light
56 · 32 · 20 px — the small cut drops the tabs
WARP
Knocked out
02 · Palette
Violet#8A6BFF · accent
Void#0A0A0E · ground
Cyan#31D2E0 · data
Gold#F2B341 · caution
Green#3FD79A · pass
Ink#EDEDF3 · type

Violet is the only accent. Cyan, gold and green are semantic — they mean data, caution and pass, and none of them ever stands in for the brand.

03 · Typography
DisplayBricolage Grotesque 800 · width axis 82
TextPublic Sans — everything you read as a sentence.
DataJetBrains Mono · 0x9dd5…6302 · 2,697 h · $0.89
RuleIf it is a figure, it is monospaced. No exceptions anywhere on the site.
04 · Files

The mono cut takes currentColor, so it inherits from whatever it sits inside. Do not recolour the fans by hand — they are the only part that is ever violet.

Your ledger

What you hold, and what you can claim.

next settlement in
Wallet
not connected
$WARP balance
Credits added
Claimable

Your keys

A key holds up to 40 RTX 5090 hours. Anyone holding one can spend its balance, so keep it in a secret manager or an env file — never in code. Revoke a key and whatever is left on it returns to your ledger.

How a settlement works

01
Top of every hour

Every address holding at least 1,000 WARP is read from the chain at the first block after the hour.

02
Fees are converted

The fees collected in that hour are split. Two thirds — the creator tax — buys RTX 5090 hours at the current rate.

03
Credits are added

Each eligible address gets hours by its share of eligible WARP. No transaction is needed and nothing moves on-chain.

04
Claim when you want

Move up to 40 hours onto a key. Nothing expires, and revoking a key returns the remainder.

Reading your ledger asks your wallet to sign a short message. The signature proves you control the address and expires within the hour. It is not a transaction, it moves nothing, and it grants no approval — there is no contract here that could spend anything of yours.