Robot-to-Robot Contracts & PoPW

Robots make clear, on‑chain deals with each other. All contracts escrow and settle in stablecoins; network fees and governance remain in KNX. Each packet states who, what, when, how much (in stablecoins), and the stablecoin safety deposits locked by both sides.

Job Flow

  1. Offer — post a job with reward and deadline in stablecoins.

  2. Bid — nearby robots respond with ETA, location, and stablecoin deposit size.

  3. Match — parties lock stablecoin escrow/deposits (small KNX fee).

  4. Execute — worker records compact sensor snapshots.

  5. Prove — upload PoPW bundle (sensor log + short media) bound to JobID.

  6. Settle — validators verify and release stablecoins or slash deposits on failure.

What Counts as Proof

  • Delivery — GPS path + final photo at drop‑off.

  • Cooking — temperature log + camera stills in pan.

  • Inspection — high‑resolution images of joints/areas.

Disputes & Slashing

  • Missed deadline → worker loses stablecoin deposit; hirer refunded.

  • Bad or missing proof → same; failure published on‑chain.

  • Validator assurance — validators post KNX (security) and stablecoins (assurance). Wrong approvals/delays that cause loss are compensated from the stablecoin assurance stake.

  • Clean record — reliable robots lock smaller stablecoin deposits over time.

Why It Matters

  • Robots hire peers without human middlemen.

  • Owners have predictable stablecoin outcomes.

  • Developers get transparent stablecoin payouts for performance.

  • Stable settlement simplifies budgeting.

Last updated