Uptime is theproduct.
Every GPU marketplace quotes you an availability number. None of them post anything against it. Nines makes providers bond their own promise: stake to list, stream to rent, slash on downtime.
- within tier8× B20099.99% · 0s down
- −2,468 NINE8× H100 SXM599.99% · 203s down
- −30 NINE2× L40S99.90% · 57s down
Three moves
Stake to list. Stream to rent. Slash on downtime.
No reputation scores, no dashboards to trust. A provider's uptime claim is only as good as the collateral standing behind it, and settlement moves that collateral automatically.
Stake to list
Listing a GPU means posting NINE worth 7 days of that listing's own revenue, multiplied by the tier it sells. Sell stricter uptime, post more. If the bond ever stops covering the price, the listing goes dark on its own.
Stream to rent
Renting opens a per-second payment stream against escrow — no invoices, no monthly minimum. Stop whenever; the unspent deposit walks back out with you. Providers can only withdraw earnings older than 24 hours.
Slash on downtime
Attesters report downtime each hour and the median is finalised on-chain. You never pay for a second the GPU was missing — and if the provider blew past its tier's allowance, the bond pays for the difference.
- Renter60%
- Insurance pool30%
- Burned10%
capped at 5% of bond per settled epoch
Settlement
One hour, four moves, no discretion.
Nothing about settlement asks anyone to be trusted. The epoch closes, a staked quorum reports, the median wins, and the contracts move the money — including against the people who run the network.
T+0
The epoch closes
Settlement runs on hourly epochs. Anything shorter is noise; anything longer lets an outage sit unpaid.
T+0 → T+1h
Attesters report
Staked attesters submit the downtime seconds they observed. At least 3 reports are needed before the epoch can close.
T+1h
The median is finalised
Anyone can finalise. The median report becomes the number of record, and any attester more than 60s away from it loses stake.
T+1h…
Settlement moves money
The renter stops paying for every missing second. Past the tier allowance, the bond pays the penalty on top.
function settle(uint256 listingId, uint256 epoch)
external
returns (uint256 penalty)
{
uint256 down = oracle.downtimeOf(listingId, epoch);
// the renter never pays for missing seconds
rebated = streams.dock(streamId, down);
uint256 allowed = tier.allowedDowntime(1 hours);
uint256 excess = down > allowed ? down - allowed : 0;
if (excess == 0) return 0;
// past the allowance, the bond pays
penalty = registry.slash(listingId, _penaltyFor(...));
_distribute(penalty); // 60 / 30 / 10
}Why the provider waits 24 hours
Earnings younger than the challenge window are not withdrawable. A downtime report that lands late can still be taken out of money the provider has not touched yet — which is why the protocol never needs a clawback, and never needs to ask a provider to give anything back.
SLA tiers
Pick how many nines you are willing to pay for.
A tier is not a badge. It sets three numbers at once: how much downtime is free, how much collateral the provider posts, and how fast that collateral drains when the promise breaks.
Batch work. An hour missing overnight costs you nothing but the hour.
- Free downtime / hour
- 36s
- Free downtime / month
- 7h 12m
- Bond required
- 10,282 NINE
- Max slash / epoch
- 514 NINE
Training runs. Checkpoints survive a blip; they do not survive a night.
- Free downtime / hour
- 3s
- Free downtime / month
- 43m
- Bond required
- 20,563 NINE
- Max slash / epoch
- 1,028 NINE
Inference in front of users. There is no free second at this tier.
- Free downtime / hour
- none
- Free downtime / month
- 4m
- Bond required
- 41,126 NINE
- Max slash / epoch
- 2,056 NINE
What does an outage cost?
One hour of an 8× H100 listing at 61.2 NINE/hr. Drag to break it, and watch the same outage price differently in each tier.
Illustrative · last 30 days
What the collateral actually did.
Slashing is not a threat the protocol makes. It is a line item, and it is meant to be small — a network where the number stays near zero is a network where the promise is holding. The figures below illustrate that shape; the network is not live yet.
Attesters
The measurement is staked too.
An uptime oracle is only as honest as what it costs to lie. Attesters probe listings, submit downtime per epoch, and are paid from the insurance pool — and the same median that convicts a provider convicts an attester who invents a number.
Below it, your reports are not counted. Reporting is a bonded job like providing.
Report further than that from the finalised median and you lose 5% of stake, on the spot.
Long enough that you cannot report, exit, and be gone before the epoch is finalised.
$NINE
One billion, fixed, and mostly locked up as collateral.
NINE has one job: to be worth more than the uptime promise a provider is tempted to break. There is no mint function after deployment.
Allocation
1,000,000,000 NINE- Provider incentives34%
Emitted to bonded capacity that stays up, over 4 years.
- Community & airdrop18%
Renters, attesters, testnet operators.
- Treasury16%
Governed by NINE holders. Funds the insurance backstop.
- Core contributors18%
1-year cliff, 4-year vest.
- Investors10%
1-year cliff, 3-year vest.
- Liquidity4%
Paired at listing, protocol-owned.
The bond asset
Every listing is collateralised in NINE. Demand for listed capacity is demand for locked NINE — the token is the thing at risk, not a fee coupon.
The unit of rent
Streams are denominated in NINE per second, escrowed up front and released as the hours actually happen.
The attester stake
Reporting uptime requires stake, and bad reports burn it. Measurement is bonded on the same asset as the thing being measured.
The sink
10% of every penalty is burned outright. Supply only moves one way, and it moves when someone fails.
Stop buying availability numbers. Start buying collateral.
Rent a bonded GPU by the second, or post a bond against the fleet you already run.