# From zero to a signed contract Pick a side. Both paths assume you already have an AT Protocol identity: a DID and a PDS that will hold your records. The fastest way is the one binary, `socialweb-computer`: `run request` for the requester side and `install bidder` for the provider side. Each automates the full flow in one process. ## Install ## I need compute ### Run the requester (automated path, recommended) One command writes the VM record and the RFP, collects bids, signs the accept, waits for the guest, runs your command (or drops you into a shell) and releases the VM: everything in steps 1-4 below, automated. Sign-in modes (QR code, browser, app password), holding a VM, ssh, sizes and the long-lived requester: [quickstart-prod.md](../../docs/quickstart-prod.md). ### Step 1 (what it does): describe the machine A `compute.vm` record: cpus, mem, disk, network, a role and the cloud-init user data. ```yaml $type: com.publicdomainrelay.temp.compute.vm cpus: 2 mem: 4G disk: 40G role: ml-inference-worker ``` ### Step 2: publish the RFP A strong reference to the VM record in a `market.rfp`, sent to every bidder it discovered through the relays. ```yaml $type: com.publicdomainrelay.temp.market.rfp payload: {uri: at://did:plc:you/com.publicdomainrelay.temp.compute.vm/3mm3d, cid: bafyrei...vm} ``` ### Step 3: wait, score, accept The bid window runs, the policy decides, the first allowed free bid (else the lowest cost) wins, and a signed `market.accept` goes to the winning provider's `submitAccept`. ### Step 4: get your receipt The provider provisions the machine and mints a `market.receipt` anchoring the whole chain. That is your proof the contract happened: check the NSID, the author DID, and that the CIDs bind straight through ([security](security.md)). ## I have machines ### Run a bidder (automated path, recommended) One service subscribes to the relays, takes RFPs, places bids, takes accepts and provisions VMs: everything in steps 1-4 below, automated. Builds and channels, who it serves, upgrade and self-update: [bidder.md](../../docs/bidder.md). ### Step 1 (what it does): pick a policy, then watch the market Choose who is even allowed to reach you (`bidder-tangled-vouch` by default; `bidder-only-me`, `bidder-mutuals`), then take `market.rfp` records from `submitRfp` and from the relays. See [trust & policy](trust.md). ### Step 2: bid it Publish a `market.bids.free` payload, then a `market.bid` that binds it to the RFP. ### Step 3: take the accept Check that the accept references your bid's exact uri and cid, comes from the RFP's own author, and that you still have room, before provisioning anything. ### Step 4: provision, then mint the receipt Provision the VM and sign a `market.receipt` anchoring rfp, bid and accept. ### Need the field-by-field detail? Every record type and validation rule is written up in the spec. - [Read the spec](docs.md) - [Try a whole market on one machine](../../docs/quickstart-local.md)