Idle Devices Earn On The Distributed Cloud

🪩 The Disco Party is MATA's distributed cloud.

Idle devices are the inventory of a distributed cloud. A laptop that is not encoding, a NAS with empty platters, a home fiber line that is asleep at 2 a.m. — centralized cloud treats that capacity as waste and sells you a slice of a rack instead. Disco treats it as supply. The Incentive primitive pays contributors for storage, CPU, and bandwidth. The SpaceDB Settlement seam is where that payment becomes $MATA through Iron Bank. You are not "donating." You are selling spare work to a mesh that would otherwise rent it from Virginia.

That is the economic inversion. AWS bills you for leaving. The distributed cloud pays the people who stay. What Is A Distributed Cloud is the architecture. This article is the payout. The Disco Party is the name on the door.

Why Idle Devices Are The Distributed Cloud's Inventory

A data center is a building full of machines that exist only to be rented. A distributed cloud is a party full of machines that already exist. Idle devices are not a side hustle bolted onto a product. They are the product: ShardStore places erasure shards on homes; compute jobs land on spare cores; iroh moves bytes across spare uplink. If nobody contributes, the mesh is a chat app. If idle devices earn, the mesh is a cloud.

Incentive is the third Digital Freedom primitive, and it is the one centralized cloud deleted on purpose. Trust is identity — mID so a host can prove who gets paid. Security is encryption — the host stores ciphertext it cannot read. Incentive is the payout that makes those two primitives scale past friends-and-family. The Federal Trade Commission has spent years on markets where the only paid party is the platform. Idle devices on a distributed cloud put a second paid party on the ledger: the person whose disk did the work.

Read The Importance of Remade With Rust for why the binary that earns must be remade. Paying a C blob to hold shards is how you fund an incident.

How Idle Devices Get Paid On The Distributed Cloud

SpaceDB's library is open. The network is disco. Settlement is a seam: an application meters use, Iron Bank settles $MATA. You do not invent a second token economy. You implement the trait. SpaceDB is the database. This page is the bill — except the bill points the other way.

Storage — Idle Devices Hold Ciphertext Shards

Erasure coding cuts sealed entries into k-of-n shards. Idle devices that keep those shards warm earn for capacity and durability. They do not earn a right to read. Security stays on the key. The Electronic Frontier Foundation has the case against "we need the plaintext to host it." A distributed cloud does not.

CPU — Idle Devices Run Jobs The Mesh Will Pay For

OCR, transcode, a vector search against a local replica — work that used to be a Lambda line item lands on a spare core. Idle devices that finish attested work get paid. Idle devices that lie get dropped. Trust is the capability that authorized the job. Incentive is the receipt. Deputy keeps the worker graph remade so the core you rented out is not a C RCE with a wallet.

Bandwidth — Idle Devices Move Bytes Peers Already Wanted

Iroh prefers LAN, then encrypted tunnels. Relays and well-connected homes carry traffic for peers behind bad NAT. Idle devices with uplink earn for that carry. The NIST Zero Trust Architecture still applies: the relay sees scramble, not vaults. A distributed cloud that pays for bandwidth is not paying for surveillance.

Idle Devices Versus The AWS Bill

Centralized cloud prices every byte that leaves, every second a vCPU exists, every GB-month you forgot to delete. Idle devices invert the meter: the capacity was already bought by a human for their own life. The distributed cloud buys the leftover. The Freedom Guide is how a person joins. Digital Freedom Era 3 is where Incentive shows up as a lifestyle, not a whitepaper. What Is Digital Freedom is the frame.

You Do Not Need A Data Center To Run Idle Devices

A home computer and a phone are already a mesh. Add a NAS and you have a storage class. The home page and Learn index are the on-ramps. The Privacy Rights Clearinghouse is the graveyard of "we consolidated everyone's leftover in one breachable barn." Idle devices stay in many barns.

Incentive Does Not Mean You Owe The Mesh Your Life

Cap the CPU. Cap the disk. Cap the uplink. Settlement honors budgets the same way capability tokens honor scope. Idle devices earn. They do not get drafted. The NIST Secure Software Development Framework wants user control in the software, not in a terms-of-service paragraph. A distributed cloud that cannot cap is a parasite.

Remade Primitives, Disco Party, Digital Freedom

Settlement, SpaceDB, mID, and the remade runtimes are Remade-With-Rust primitives. They become a disco party when idle devices earn on the peer-to-peer distributed cloud. They become Digital Freedom when Trust, Security, and Incentive — identity, encryption, payouts — show up as a balance, not a bill. Start at the Disco Party and Remade With Rust. Leave the AWS invoice for people who like renting their own spare time.

The bill this replaces is no egress bill. The machines doing the earning are Rust edge nodes. Why they cannot run C is why a distributed cloud needs memory-safe Rust.