RIGSTACK
RACK A1 ONLINE LOAD 0%
Decentralized compute · part-level rental

Rent the part.
Hold the key.

RigStack splits a machine into rentable layers — CPU, GPU, memory, storage, bandwidth, power, cooling. Each layer is its own coin. To rent one layer you have to be holding a slice of the layer it depends on: 1% of your rental value, in the gating coin. Mount what you need, hold what unlocks it.

Rentable layers
6 online
Platform token
$RIG
Hold requirement
1% of rental
Settlement
SOL escrow

// Rack A1 — mounted units

green = rentable · amber = gating dependency
Browse the marketplace ▸live offers across every layer
// Marketplace

Rent by the layer

Live offers across every rentable layer. No KYC, no account — connect your wallet, hold the gating coin, mount in seconds. Pay only for what you use, settled in SOL.

// Wallet holdings

Not connected
Connect to load balances. RigStack reads your part-coin holdings to verify gating before any rental is escrowed.
‹ All layers
// Mechanics

How RigStack works

Three moving pieces: the part coins you rent against, the gating rule that ties them together, and $RIG sitting underneath as the platform layer.

01 Parts are coins

Each rentable layer of a machine is its own token. Holding it isn't required to rent that layer — it's the key that unlocks the layers that depend on it. Demand for a part's compute pulls demand into its key coin.

02 The 1% gating rule

To mount a rental you must hold at least 1% of the rental's SOL value in the gating coin for that layer. Rent 10 ◎ of GPU time → hold 0.1 ◎ worth of $CPU. The hold stays in your wallet; it's never spent.

rent_value = 10 ◎ → required_hold = 0.10 ◎ in $CPU

03 Hold deeper, rank higher

Meeting the 1% minimum makes you eligible. Holding multiples of it raises your scheduling priority and shaves the protocol fee — so the key isn't just a gate, it's a throttle on how good your rental terms get.

04 $RIG is the floor

$RIG is the platform token. It gates full-machine ($NODE) rentals, sets your base fee tier, and routes a share of every layer's protocol fee back to holders. Part coins are the keys; $RIG is the lock everything mounts into.

// Dependency wiring

arrow = "renting this requires holding that"

The core loop

$CPU, $SSD and $RAM form a closed triangle — renting $CPU needs $SSD, $SSD needs $RAM, $RAM needs $CPU. The base compute layers gate each other, so the keys stay liquid even when nobody's renting the flashy stuff. $GPU and $NET both key off $CPU; $NODE keys off $RIG.

Priority tiers

Eligibility is binary; terms are graded by how deep you hold past the minimum.

1×  STANDARD  — eligible, 0.5% fee
5×  PRIORITY  — front of queue, 0.35% fee
20× DEDICATED — reserved slot, 0.2% fee
// Documentation

RigStack docs

Overview

RigStack is a part-level compute rental protocol on Solana. Instead of renting a whole server, you rent a single hardware layer — a block of GPUs, a slab of memory, a bandwidth allocation — and pay per unit, per hour, in SOL held in escrow for the rental window.

Every layer is represented by a utility coin. Renting a layer requires holding a position in that layer's gating coin: the part it physically depends on. This is what couples the token economy to real usage — you can't pull compute out of a layer without holding the key to the layer beneath it.

Token layers

Eight rentable layers, plus the $RIG platform token. Rates are per unit, per hour, denominated in SOL.

CoinLayerUnitRate (◎/unit·hr)Gating coinContract

Each coin's contract address is its SPL mint. Contract links open the live Pump.fun coin page, and the rack, wallet balances, and gating checks read the mint directly from the COINS map. Unlaunched layers display AWAITING DEPLOY.

Gating formula

The mount check is deterministic and runs client-side before any escrow is opened:

// all values in SOL terms
rental_total = rate × quantity × hours
required_hold = rental_total × 0.01 // 1%

gating_coin = DEPS[layer]
held_value = wallet[gating_coin].sol_value

eligible = held_value >= required_hold
tier_mult = held_value / required_hold // 1× / 5× / 20×

The required hold is never transferred or locked — RigStack only reads the balance at mount time and at settlement. Sell below the threshold mid-rental and the slot is released at the next scheduling tick.

Priority tiers

Holding past the 1% minimum upgrades your terms. Tier is recomputed every scheduling tick from the live ratio of held value to required hold.

TierHold ≥SchedulingProtocol fee
STANDARD1× minBest-effort queue0.50%
PRIORITY5× minFront of queue0.35%
DEDICATED20× minReserved slot0.20%

Rental lifecycle

1 · Configure

Pick a layer, set quantity and duration. The bay computes rental_total and required_hold live.

2 · Verify

RigStack reads your gating-coin balance. If held_value ≥ required_hold, the mount button unlocks and your tier is set.

3 · Escrow

The rental total moves into a per-rental escrow PDA. Compute is provisioned against your tier's scheduling priority.

4 · Settle

At expiry, escrow releases to the provider minus the protocol fee. Hold-below-threshold during the window forfeits the slot but never the held key coin.

Fees & $RIG

Every settled rental pays a protocol fee (0.20–0.50% by tier). Fee flow:

ShareRoutes to
60%$RIG holders (pro-rata)
30%The rented layer's coin — buy pressure on its key
10%Protocol treasury / provider incentives

$RIG also gates $NODE (full-machine) rentals and sets your base fee tier independent of any single layer's hold.

FAQ

Is the held coin spent?

No. The 1% is a balance check, not a payment. It stays in your wallet the entire rental.

What if I rent a layer that gates itself indirectly?

The dependency graph is fixed per layer — see the wiring diagram. You only ever need to hold one gating coin per rental.

Which layers are live?

Every layer marked with a green LED on the rack is rentable now. Amber-tagged dependencies show which key each one needs.