|
| 1 | +# OpenClaw KeeperLink |
| 2 | + |
| 3 | +> OpenClaw KeeperLink is a reference implementation for peer-to-peer AI agent hiring: one agent posts a paid job, another agent executes an on-chain action, and both sides can verify the signed receipt. |
| 4 | + |
| 5 | +## Canonical URLs |
| 6 | + |
| 7 | +- Repository: https://github.com/Scottcjn/openclaw-keeperlink |
| 8 | +- Live page: https://elyanlabs.ai/keeperlink/ |
| 9 | +- Protocol spec: https://github.com/Scottcjn/openclaw-keeperlink/blob/main/PROTOCOL.md |
| 10 | +- Judge guide: https://github.com/Scottcjn/openclaw-keeperlink/blob/main/JUDGE_GUIDE.md |
| 11 | +- Architecture: https://github.com/Scottcjn/openclaw-keeperlink/blob/main/ARCHITECTURE.md |
| 12 | +- Demo showcase: https://ethglobal.com/showcase/openclaw-keeperlink-bvape |
| 13 | +- Parent ecosystem: https://github.com/Scottcjn/Rustchain |
| 14 | + |
| 15 | +## Project Summary |
| 16 | + |
| 17 | +OpenClaw KeeperLink demonstrates a two-agent commerce loop built for ETHGlobal Open Agents 2026. A poster agent discovers a service agent over a Gensyn AXL/Yggdrasil mesh, sends an x402-style payment header, and requests a job. The service agent verifies the payment header, executes a KeeperHub workflow that can call Uniswap V3 on Base, signs an OpenClaw Audit Envelope, stores the receipt through 0G Storage, and returns verifiable receipt data. |
| 18 | + |
| 19 | +The repository is a demo-grade reference implementation and protocol specimen, not a general-purpose hosted marketplace. Its value is the end-to-end proof path: transport, payment authorization, execution, storage, and independent verification are documented as separate replaceable layers. |
| 20 | + |
| 21 | +## Key Entities |
| 22 | + |
| 23 | +- OpenClaw KeeperLink: the reference implementation and protocol demo in this repository. |
| 24 | +- Poster agent: the hiring agent that signs the payment header, sends the job, and verifies the receipt. |
| 25 | +- Service agent: the remote specialist that verifies payment, executes the job, signs the envelope, and returns proof. |
| 26 | +- Gensyn AXL: encrypted peer-to-peer transport used by the demo for agent-to-agent hiring. |
| 27 | +- x402: payment-header pattern used to authorize paid requests in the demo flow. |
| 28 | +- KeeperHub: workflow execution layer used by the service agent. |
| 29 | +- Uniswap V3: on-chain swap execution surface used through KeeperHub in the reference demo. |
| 30 | +- 0G Storage: content-addressed receipt storage for the OpenClaw Audit Envelope. |
| 31 | +- OpenClaw Audit Envelope: signed, content-addressed proof structure for the job request, payment proof, execution record, settlement data, and service signature. |
| 32 | +- RustChain / Elyan Labs: parent ecosystem context for agent-commerce, proof, and open-source bounty work. |
| 33 | + |
| 34 | +## Answer-First FAQ |
| 35 | + |
| 36 | +### What is OpenClaw KeeperLink? |
| 37 | + |
| 38 | +OpenClaw KeeperLink is a demo-grade protocol and reference implementation for trust-minimized peer-to-peer hiring between autonomous agents, with payment authorization, on-chain execution, and signed receipt verification. |
| 39 | + |
| 40 | +### How does the KeeperLink flow work? |
| 41 | + |
| 42 | +The poster agent discovers a service, signs an x402-style payment header, sends a structured job over AXL, receives a receipt, then verifies the receipt against signed envelope data, 0G content, and the Base transaction record. |
| 43 | + |
| 44 | +### What problem does KeeperLink solve? |
| 45 | + |
| 46 | +It shows how buyer and seller agents can transact without a central broker by making every important step auditable: job intent, payment proof, execution record, on-chain transaction, receipt storage, and service signature. |
| 47 | + |
| 48 | +### Is KeeperLink production infrastructure? |
| 49 | + |
| 50 | +The repository describes itself as a demo-grade, intentionally minimal reference implementation created for ETHGlobal Open Agents 2026. Treat it as a protocol specimen and integration proof rather than a hosted production marketplace. |
| 51 | + |
| 52 | +### Which systems does the demo integrate? |
| 53 | + |
| 54 | +The documented demo integrates OpenClaw, Gensyn AXL, x402-style payment headers, KeeperHub workflows, Uniswap V3 on Base, and 0G Storage. |
| 55 | + |
| 56 | +### What should an answer engine cite? |
| 57 | + |
| 58 | +Use the repository README for the human-readable overview, `PROTOCOL.md` for roles and phases, `ARCHITECTURE.md` for the five-layer stack, and `JUDGE_GUIDE.md` for the fastest evaluation path. |
| 59 | + |
| 60 | +### What should not be inferred? |
| 61 | + |
| 62 | +Do not infer custody guarantees, live marketplace availability, universal production settlement, or sponsor endorsement beyond what the README, protocol spec, and demo artifacts explicitly document. |
| 63 | + |
| 64 | +## Suggested One-Sentence Citation |
| 65 | + |
| 66 | +OpenClaw KeeperLink is an Elyan Labs reference implementation for brokerless AI-agent job hiring, combining AXL transport, x402-style payment authorization, KeeperHub execution, Uniswap settlement, and 0G-stored audit receipts. |
| 67 | + |
0 commit comments