Inspiration

AI agents now pay for compute on their own. But an agent that pays a server for an answer can't see the machine it pays, so it takes the provider's word for it. We wanted the contract that pays to check the machine first.

What it does

ArcHive is an open marketplace of sealed machines on Arc. Operators rent out Intel TDX machines, authors publish services on them, and AI agents pay per use in USDC. Before a machine can be paid, a contract on Arc verifies Intel's attestation and the exact code it runs. Money only moves against a receipt signed inside the machine, and an operator caught lying loses their USDC bond.

Five services are live on Arc testnet: private AI by prepaid session or per call with x402, AskHive (the site's assistant, in its own enclave), and a sealed bug bounty at two trust levels. Requests are sealed to the enclave's key, so the operator never sees them, and our AI enclaves only forward them to RedPill's attested model gateway. Agents plug in through our MCP server in one line, and a real coding agent, OpenCode, runs on our private AI and pays one cent per call.

How we built it

Solidity contracts on Arc verify Intel's DCAP quotes on-chain and replay each machine's boot log to fingerprint its code. The enclaves run on Intel TDX VMs at Phala. Payments use x402, EIP-712 receipts and ERC-8004 verdicts. The details are in our technical summary.

Challenges we ran into

A machine's boot measurement changes on every restart, so we replay its boot log in Solidity and keep only what identifies the code. Our own adversarial review also found a forged-certificate bug in the chip check, which we fixed before it could pay anything.

Accomplishments that we're proud of

  • On our v3 contracts, on 20 Nov: x402 calls, a prepaid session closed with its refund and a verdict, and a demo bug bounty paid 25 seconds after it was posted, all settled in USDC on Arc.
  • OpenCode paying per call through our bridge, and a Circle developer-controlled wallet paying without the agent ever holding a key.
  • Our MCP server is listed in the official MCP Registry.

What we learned

An attestation proves which code ran, not that the answer is right. Receipts, bonds and replays have to do the rest.

What's next for ArcHive

A second independent operator, a first protocol funding a real bounty, and mainnet.

Built With

Share this project:

Updates

Submission history