// staking · infrastructure railEARLY-STAGE — GENESIS PLAN

STAKING AT SUPERCOMPUTE

Community-backed Ethereum validators that buy the cluster. Supercompute's staking rail turns validator rewards into owned hardware — starting with one DGX Spark and one validator node, scaling to five machines and three validators (96 ETH bonded). The launch node is the funding vehicle for the first DGX Spark purchase.

// at a glance

System Sheet

// project
Staking at Supercompute — [PLACEHOLDER: final name]
// status
Early stage — genesis plan (not yet live)
// compute genesis
1x NVIDIA DGX Spark
// compute target
5x NVIDIA DGX Spark
// validator genesis
1x Ethereum validator node
// validator target
3x Ethereum validator node
// bond per node
32 ETH
// total bond at target
96 ETH (3 x 32)
// funding vehicle
Launch node → first DGX Spark purchase
// chain
Ethereum — [PLACEHOLDER: mainnet / testnet]
// timeline
[PLACEHOLDER: genesis date + milestones]
// participation
[PLACEHOLDER: how the launch node raises]
// dgx spark compute
0/ 5 units
genesis target · static until live
// validator nodes
0/ 3 nodes
genesis target · static until live
// eth bonded
0/ 96 ETH
genesis target · static until live
// dgx spark funded
0/ 1 via launch node
genesis target · static until live
// how it runs

The loop

Stake → own hardware → run the fleet. The loop is designed so the network's own rewards become the network's own machines — no cloud rent, no landlord in the middle.

// genesis
Genesis — one node, one machine

The cluster starts small: a single DGX Spark and a single Ethereum validator node online together. Enough to prove the loop end-to-end before anything scales. [PLACEHOLDER: genesis date]

// launch node
The launch node funds the first machine

The first validator node doubles as the funding vehicle — its launch is what pays for DGX Spark unit one. Hardware bought by the network, owned by the network. [PLACEHOLDER: instrument structure, target size]

// bond
Validators scale to three

Staking grows to three Ethereum validator nodes — 32 ETH bonded per node, 96 ETH at full strength. Rewards accrue to the network, not a landlord. [PLACEHOLDER: reward split, custody model]

// compute
Compute scales to five

As funding clears, the fleet grows from one DGX Spark to five. More owned hardware, no cloud lock-in — the cluster is a balance-sheet asset the community backs. [PLACEHOLDER: purchase milestones]

Early-stage honesty: nothing above is live yet. The numbers that are decided — 1 → 5 DGX Spark, 1 → 3 validators, 32 ETH per node, launch node as the funding vehicle — come from the project brief. Everything structural that is not yet decided is a labeled [PLACEHOLDER] below. No invented yields, dates, or addresses.

// roadmap

Four phases · gated

Built the same way every Supercompute project runs: in stages, each one verified before the next opens. [PLACEHOLDER: timeline for each gate.]

0
PHASE 0 — LAUNCH NODE DESIGN
CHECK-IN GATE

Funding vehicle structure for the first DGX Spark purchase — instrument, target, custody, entry mechanics

[PLACEHOLDER: structure doc + dates]
1
PHASE 1 — GENESIS NODE + FIRST MACHINE
CHECK-IN GATE

1x DGX Spark online · 1x Ethereum validator node online · launch node fills

Hardware purchased · validator signing
2
PHASE 2 — VALIDATOR SCALE
CHECK-IN GATE

1 → 3 Ethereum validator nodes (32 ETH each · 96 ETH bonded)

3x validators · rewards flowing
3
PHASE 3 — COMPUTE SCALE
CHECK-IN GATE

1 → 5 DGX Spark as funding clears

5x DGX Spark cluster
// ledger

Decided vs open

// decided — from the brief
genesis
1 DGX Spark · 1 validator node
compute target
5x NVIDIA DGX Spark
validator target
3x Ethereum validator nodes
per-node bond
32 ETH
funding logic
Launch node → first DGX Spark
// open — labeled slots
name / positioning
[PLACEHOLDER: final project name + one-line story]
timeline
[PLACEHOLDER: genesis date, milestone gates]
launch instrument
[PLACEHOLDER: how the funding vehicle raises (node sale / bond / allocation)]
reward split
[PLACEHOLDER: where validator + compute yield goes]
custody
[PLACEHOLDER: who signs, which wallet/multisig]
chain + contracts
[PLACEHOLDER: mainnet vs testnet, contract addresses]

This page is a scaffold, not a claim. The writer pass will turn it into final copy once the project has a name, a timeline, and a launch structure. Until then, the only promises on this page are the ones the brief made.

The network pays for the machines. The machines run the network.