Bridges and continents

Forming a continent

Every member's owner signs the EIP-712 message Bridge(members, nonce). Anyone then calls Continents.form(ids, sigs). The contract checks that each member is lit, outside any other continent, bonded at 50,000 $GPU (house islands excepted) and that the members span at least two distinct hosts as observed by the probes.

A continent on one machine would promise redundancy it does not have, so the contract refuses it with OneHost(). When a sink or a departure leaves a continent on one host, it dissolves.

Jobs

A buyer opens a job with openJob(continent, specHash) and pays the escrow with x402 payments that name the job instead of an island. Typical jobs: a transcription batch longer than one GPU's day, a dataset build (crawl, transcribe, embed, publish onto a dataset island), a sharded embedding run.

When the job is done, the keeper closes it with a Merkle root of (owner, amount) lines, where each island's amount is the escrow times its uptime share times its units over the sum. Owners claim with Meter.claimJob(job, account, amount, proof).

The house continent

The house islands Coral, Reef and Lagoon share one server, so they cannot form a continent alone. The house continent is Coral plus Key, a CPU island on a separate host, and it runs one standing daily job: transcribe a fixed slice of LibriVox audio and stock the transcripts on Lagoon.