September 2026/$DRAM on Robinhood Chain/Launchpad ponsfamily.com

Rented memory,proven every hour.

Dramnet turns idle RAM into a regional cache layer. Operators stake capacity, the coordinator challenges it three times an epoch, and settlement runs on-chain in $DRAM. Fail a challenge and the stake pays for it.

Rent memoryRun a node

Spot index$ / GB·h

Active operatorsnodes

Capacity heldTB

Replicationcopies · 99% / 7d

01Components at launch

Four pieces. All of them live on day one.

An order travels through them in order — reserved by an agent, placed by the coordinator, settled by the contracts, reached through the gateway.

01Docker image

Operator agent

Reserves the declared volume behind a cgroup limit and brings up an isolated Dragonfly instance. Nothing else on the box can take that memory back.

Heartbeat: every 15s
Reports: region · free capacity
Reports: p99 latency

02Off-chain service

Coordinator

Matches an order to nodes, places it inside one region, runs the challenges, counts gigabyte-minutes and signs the epoch report.

Challenges: 3 per epoch
Meters: GB-minutes
Epoch: 60 minutes

03Robinhood Chain

Contracts

Buyer deposit in escrow, operator stake at risk, an epoch registry, and payout against a cumulative merkle root that an operator can claim at any moment.

Holds: buyer deposit
Pays: cumulative root
Claim: any time

04TLS endpoint

Gateway

One endpoint, one access token. Data encryption keys stay with the buyer and never reach the operator — the operator holds ciphertext it cannot read.

Keys: buyer-side only
Access: token per order
Sees: ciphertext

Together they make one claim checkable: this memory is held, right now, in this region.

02Proof of capacity

You cannot fake memory you are not holding.

Three times an epoch the coordinator writes a blob of the declared size, reads back one random offset and compares the hash. The answer has to come back inside 50 ms within the region. Disk cannot do that.

Failure has a price, not a warning

A missed challenge, or node metrics showing a slide into swap, costs 10% of the stake. Losing the blob outright costs 100%.

coordinator · epoch challenge

eu-central · p99 0.9 ms

Held blob

Idle — 3 challenges scheduled this epoch.

01queued—
02queued—
03queued—

03Placement

Sold inside a region, and held twice.

The coordinator matches an order to nodes in the buyer’s own region, and never across. Remote memory over the public internet loses to local memory on latency by a margin no routing fixes — and every blob it does place is held by two independent operators.

Regions

Operators

Capacity

330.5 TB

Copies / blob

eu-centralFrankfurt

Nodes

Capacity

83.0 TB

p99

Every blob is held 2 times

Two independent operators inside eu-central, each holding a full copy. Losing one is a slash, not an outage.

COPY 1

eu-central

operator 0x7f…a2

COPY 2

eu-central

operator 0x3c…e9

UPTIME TARGET 99% OVER 7 DAYS

Why it stops at the border

Inside eu-central0.9 ms

Challenge deadline50 ms

To ap-northeast195 ms

9,333 km of fibre puts the round trip at roughly 195 ms — 4× the challenge deadline. No amount of routing brings that under 50 ms, so the coordinator never places it.

04Parameters

The numbers, without the prose.

Unit of accountEpoch of 60 minutes

GB-minuteEpoch of 60 minutes

LotStep 1 GB, per node

1–512 GBStep 1 GB, per node

ChallengesAnswer within 50 ms in-region

3 per epochAnswer within 50 ms in-region

Operator stakePer 1 GB of declared capacity

Fixed $DRAM ratePer 1 GB of declared capacity

SlashFailed challenge / lost blob

10% / 100%Failed challenge / lost blob

ReplicationIndependent operators · 99% uptime over 7 days

2 copiesIndependent operators · 99% uptime over 7 days

05Price and forward

Indexed to the market, discounted by the network.

The spot price per GB-hour is the index of three public provider list prices minus a fixed network discount. Paying in $DRAM takes another cut, and part of what you pay is burned.

Provider index

$0.00620

Mean of three public list prices per GB-hour.

Network discount

− 34%

Fixed. Applied to the index, not negotiated per order.

Spot

$0.00409

What an order is metered at, per GB-hour.

Size an order

1–512 GB · step 1 GB

Allocation map12.5% of a node

Capacity64 GB

Term30 days

Settle in $DRAM−8% against the list, 15% of it burned

Metered

GB-min

List

USD

You pay

USD

Burned

USD

Forward credit

Lock the price for a term. The credit is its own token, so it can be resold before it is ever redeemed.

Locked price$0.00429/ GB·h

Term premium+4.8%

Held for90 days

Transferableyes · own token

Selling forwards puts the network short the price of memory. That position is hedged, and the limit on how much can be sold is voted each quarter.

See the hedge

06Hedging the short

A forward book is a short position. It gets covered.

Selling a fixed price for 180 days means the network is short the price of memory. The buffer is tokenised MU, because Micron tracks the DRAM spot.

DRAM spotTokenised MUResidual

ρ = 0.87 · illustrative

Every forward sold

opens more short exposure to the memory price.

Quarterly surplus

goes into buyback and burn of the token.

Quarterly shortfall

is closed by selling out of the MU buffer.

How much forward the network is allowed to sell in a quarter is not a parameter someone sets — it is voted by $DRAM holders, and the buffer sits behind a 3 of 5 multisig.

07Forward book

A credit you can sell on. A cap you vote on.

Locking a price issues a token, and that token has a life of its own until someone redeems it against rent. How many of them the network may write in a quarter is not a policy — it is a number on a ballot, and it is the number that sets how short the network is.

Buy the term

Pay today to fix a GB-hour price for 30, 90 or 180 days. The payment issues a credit as its own token.

Hold it or sell it

The credit is transferable. Once spot runs above the locked price it carries a spread, and that spread is what a buyer pays.

Redeem against rent

Whoever holds it at the end spends it on memory at the locked price. The credit burns on redemption.

What the credit is worthspot $0.00409

Term locked

Spot moves+28%

Locked at

Spot now

Credit marks

Spot is 28% above where the term was written, so the credit buys memory $0.00095 per GB-hour under the market. That spread is the secondary price — the holder never has to use it themselves.

This quarter’s cap

61.4Mof 88M GB·h written

OPEN NOTIONAL $264,649 · BUFFER $117,000 · COVERAGE 111%

Cap for next quarter

IF THAT CAP IS WRITTEN IN FULL

Buffer required: $151,720
Coverage at today's buffer: 77%

Excess $11,141 buys back and burns

Each quarter the buffer is checked against what is actually open. Raising the cap does not change that arithmetic — it changes which side of it the network lands on.

Book size, buffer and ballot options are illustrative. The mechanism is not: a forward sale is a short position, the cap bounds it, and holders of $DRAM set the cap. Blended forward price across the three terms is $0.00431 per GB-hour, stress-tested against a 40% rise in the memory price.

08For operators

Idle RAM, metered and paid every epoch.

Reserve capacity behind a cgroup limit, stake against it, and earn on every gigabyte-minute the coordinator places on your node. Payout accrues to a merkle root you can claim whenever you want.

Run the agent

One container. It holds the volume with a cgroup limit, brings up an isolated Dragonfly, and heartbeats every 15 seconds.

Stake the capacity

A fixed rate per declared GB. The stake is your admission to orders and the collateral a slash comes out of.

Claim when you like

Each epoch report adds to a cumulative merkle root. Nothing expires and nothing needs claiming on a schedule.

Operator agent

docker run -d --name dramnet-agent \
  --memory=128g --memory-swap=128g \
  -e DRAMNET_REGION=eu-central \
  -e DRAMNET_DECLARED_GB=128 \
  -e DRAMNET_OPERATOR=$YOUR_ADDRESS \
  ghcr.io/dramnet/agent:1

Heartbeat: 15s
Answer within: 50 ms
Placed in: eu-central

What a node earnsspot $0.00409 / GB·h

Declared capacity128 GB

Utilisation68%

Region

Stake required

$DRAM

Per epoch

USD

Per 30 days

USD

Stake paid back

days at 68%

What a mistake costs at this size

Missed challenge · 10%−$65

Lost blob · 100%−$645

Three inputs above are assumptions, not published figures+

Stake rate12 $DRAM / GB

Token price$0.42

Protocol fee12%

The concept fixes the stake as a rate per declared GB but does not publish the rate, the token price or a network fee. Move them and the figures above move with them.

09$DRAM

Four jobs. Each one is required for the network to run.

Operator stake

Admission to orders and collateral against slashing. Capacity you have not staked for cannot be sold.

Access + collateral

Rent settlement

Pay for memory at a discount to the list price. 15% of every payment settled this way is burned.

−8% · burn

Forward credits

Buying a locked term price. The credit is issued as its own transferable token against the payment.

30 / 90 / 180 days

Governance

Voting the quarterly cap on how much forward the network may sell — the one number that sets its risk.

Quarterly vote

Launching September 2026 on Robinhood Chain via ponsfamily.com. Figures shown across this page are illustrative and derived from the published parameters — they are not a live feed.

10Limits

What this does not do.

Four constraints are structural. They are on the page because anyone who evaluates the network seriously will find them anyway.

There is no durability guarantee on anything placed here. Replication across two independent operators and the slashing rules reduce the odds of loss, they do not eliminate it. Data is encrypted buyer-side, so an operator holds ciphertext it cannot read — and losing it costs the operator its entire stake.

Over the public internet, a round trip to someone else's RAM cannot compete with the RAM in your own box. That is why placement is regional, why the challenge deadline is 50 ms in-region, and why the product is a cache tier rather than a replacement for local memory.

Micron tracks the DRAM spot closely enough to buffer the forward book, but it is an equity with its own drivers — earnings, supply decisions, the wider market. Some residual exposure always remains, which is why the quarterly forward cap exists and is voted rather than fixed.

TrendForce and DRAMeXchange are the reference prices for DRAM, and both are behind a paywall and lag the market. The oracle is therefore built on public provider list prices, which are timely and verifiable but coarser than a true spot index.

Phase 01 · Build

The parts that hold memory

Agent, coordinator and the challenge harness that makes capacity checkable at all.

GB of capacity ready

Two ways in.

Buy a regional cache tier you can verify, or put the RAM you are already paying for to work and get paid every epoch.

Rent memory Run a node

11Before launch

Legal review

The forward module goes through legal assessment before launch. A tokenised, resellable price lock is the part of this network that needs an opinion, not an assumption.

Independent audit

Escrow, stake and the merkle payout contracts are audited independently before any deposit is taken.

Multisig 3 of 5

The MU buffer and the network parameters sit behind a 3-of-5 multisig from day one, not added later.