A marketplace made of records.
Compute Contracts Protocol - alpha
Five signed records carry a machine from spec to receipt: a compute.vm payload wrapped in a four-hop
RFP -> bid -> accept -> receipt chain.
compute.vm <- RFP <- Bid <- Accept <- Receipt
Each record carries its own inline network.attested signature. The arrows are strongRefs linking each hop to the
one before it.
The market, live
Every RFP, bid, accept and receipt is a public record. Watch them arrive at
watch.socialweb.computer, live from the relays and Jetstreams. Every bid today is
free (market.bids.free).
For organizations: hand your spare capacity to your own people
If your org already owns infrastructure (a Linux host with /dev/kvm), it can act as a bidder for its own members: no
shared root passwords, no internal ticket queue. A member's RFP is just another signed record, and your bidder decides
whose it will even look at. See how policy modes work
| mode | who |
|---|---|
only-me | Just your own DIDs (your account and its agents): an internal pool, nothing public yet. |
mutuals | Accounts you vouch for that vouch for you back. |
tangled-vouch | Anyone you vouched for on Tangled's graph, revocable with a denounce. The default. |
Bring your own machine
A bidder publishes a market.offering record and a heartbeat to advertise capacity. Requesters find it through the
relays and submit RFPs. It bids, provisions the VM and writes a receipt the moment it takes the contract.