Repository avatar
Developer Tools
v0.0.5
active

archive

xyz.arc-hive/archive

Pay-per-use USDC marketplace of Intel TDX enclaves verified on Arc testnet: read, check, prepare

Documentation

ArcHive

CI · Main track: Agentic Payments and AI · Chain award: Best use of Arc

Sealed machines, open market. AI agents pay per use in USDC for compute on Intel TDX machines. Arc checks the machine before anyone is paid. A proven lie costs its operator's bond.

The problem. An AI agent that pays for AI or compute today cannot check which machine served it, or what that machine did with its data. ArcHive lets it pay only machines Arc has checked, and makes a proven lie cost the operator money.

The business. Buyers: AI agents and apps (private AI) and protocols (bug bounties). Sellers: operators of Intel TDX machines, who post a USDC bond and earn 95 % of each paid call or session. The network keeps 5 %, and 10 % on top of each bounty payout.

Why Arc. USDC is both the price and the gas, so a 0.01 USDC call settles on Arc with its split in one transaction, and the agent never holds another token. It signs one USDC authorization (EIP-3009, as in x402) and pays no gas.

Live: https://arc-hive.xyz · For AI agents: /llms.txt and the MCP server, https://arc-hive.xyz/mcp

ArcHive's home page: sealed machines, open market ArcHive's Services page: a rack whose sleds are the products, each with its live state

Menu

Try it in two minutesthree checks, no wallet needed
The track, point by pointwhat Agentic Payments and AI asks for, and where ArcHive does it
Servicesthe five products, who pays and how much
Architecturethe diagram, in four steps
How an AI agent paysthe agent's loop, x402 per call and prepaid sessions, the limits that cap its losses
ArcHive on Arc, with Circle's toolswhat we use from Arc and Circle, why, and what we left out
How it workshow Arc verifies an enclave, AskHive in its enclave, the economics
Use it from your toolsthe MCP server, the SDK, OpenCode (opencode-arc), Claude Code
Proofs and contractsevery transaction and contract address on Arc testnet
Run itbuild, test, and the repository map

Try it in two minutes

  1. Arc refuses a wrong machine. On https://arc-hive.xyz, in the Arc check section, press Change one byte: Arc recomputes the image fingerprint and refuses the machine. It's a read-only call, with no wallet.
  2. Ask AskHive, in the Ask AskHive bar on the home page: "Is this chat sealed in an enclave?" It answers from its own enclave, admitted by Arc.
  3. Plug your agent in: claude mcp add --transport http archive https://arc-hive.xyz/mcp, then ask it what runs on ArcHive.
OpenCode on ArcHive's private AI calls the ArcHive MCP: five enclaves Arc verified right now, one per product

OpenCode runs on ArcHive's private AI (0.01 USDC per call) and reads the live network through our MCP server, added to its config.

With a wallet: get test USDC at https://faucet.circle.com, then pay one 0.01 USDC call or open a prepaid session on the site.

The track, point by point

Agentic Payments and AI asks forArcHive
A marketplace agents can discover and pay in USDCArcHive is that market. Services are listed in a registry contract on Arc, agents find them through the MCP server or /llms.txt, and they pay in USDC. Operators can rent out machines and authors can publish services.
Agents that pay for compute per request (x402)Service 3: an agent pays 0.01 USDC per private AI call, x402 style, with one EIP-3009 signature and no gas. OpenCode, a coding agent, pays each of its own AI calls this way, and so did a Circle developer-controlled wallet.
Spending controls and guardrailsA per-call cap, a session budget with the rest refunded, admitted enclaves and allowed images only, and no signing tool in the MCP: the limits.
Tools that let LLMs read and act on the chain safelyThe MCP server: 16 tools read Arc and prepare transactions, and the person signs them in their own wallet.
Agents execute onchain transactions or read the chainThe agent's USDC authorizations settle on Arc (X402Settler, event CallSettled), and the MCP reads Arc live.
Document the agent's decision loop and safety limitsAgent decision loop and safety limits

Services

Anyone can publish a service. These five are ours, live on Arc testnet.

#ServiceWho paysPrice on testnet
1Private AI, prepaid sessionan app or a user0.10 USDC per 1,000 tokens, the rest refunded
2Sealed Bountya protocol funds a poolpaid only for an exploit a sealed machine replayed
3Private AI, pay per call (x402)an AI agent, one signature, no gas0.01 USDC per call
4AskHive, the site's assistant in its own enclavefree—
5Sealed Bounty, verified levela protocolas #2, on chips Arc and the Proof of Cloud alliance verified

On each paid AI session or call, 95 % goes to the operator whose enclave served it and 5 % to the network. On a bounty payout, the hunter gets the whole tier, and the pool adds 10 % for the network and 5 % for the operator.

Architecture

ArcHive architecture: who pays, the services, the operator's enclaves on Phala, the contracts on Arc testnet, steps 1 to 4
  1. Arc admits the machine. A contract checks Intel's signature on the machine's quote and the fingerprint of the exact image it runs.
  2. The agent pays per call. It reads the enclave's key on Arc, seals its request to it, and signs one USDC authorization.
  3. The enclave answers with a signed receipt. USDC moves only against that receipt, split in the same transaction.
  4. A lie costs the bond. Two conflicting receipts, or a bounty claim that other enclaves refute by replay, seize the operator's USDC bond.

What's next

  • A second, independent operator, with our enclave images published.
  • A first protocol funding a real Sealed Bounty.
  • Mainnet: Intel's verifier first, then our contracts behind a multisig.

Team

Jean-Baptiste Durand (@JeanBaptisteDurand) and Florent Belotti (@FlorentBelotti), for UBC 2026. MIT license.

No installation packages available.

Remote