ETHGlobal Mumbai · Hedera x402 · Arkiv · ENSv2

Your agent pays. Leash checks who it is paying.

A shared, proof-of-payment-backed safety registry and guard for AI agents paying over x402. One agent's loss protects every other agent, no verdict is permanent, and a merchant coming out of a block earns trust back through probation.

Happening on Hedera now

Live audit trail

    Three verdicts, before anything is signed

    ALLOW Pay now

    A known merchant, an amount inside its limit and a low risk score. The agent pays with no human in the loop.

    ESCALATE Ask the owner

    An unknown merchant, a price above the limit, a medium score, probation or an outage. Only the owner's wallet can release it.

    DENY Never pay this

    A blocked merchant, a spoofed payTo, a replay or a price above what the merchant declared. Nothing is signed.

    How a payment is checked

    Read the docs
    1. Identify

      The merchant's ENSv2 name declares its payTo, network, asset, maximum price and domains. A 402 that contradicts it is denied.

    2. Read the history

      Arkiv holds reports from every agent that paid this merchant, each signed by its payer and written only after settlement.

    3. Re-verify

      Each report is checked on Hedera Mirror Node: a real USDC transfer from that payer to that payee, in that amount.

    4. Decide

      A five-factor risk score, the merchant's standing, spend caps and hard rules give ALLOW, ESCALATE or DENY before anything is signed.

    5. Report

      After delivery the guard files its own signed report, and an audit message to Hedera Consensus Service.

    The registry, live

    These counts fall as entities expire: on Arkiv, expiry is how the registry forgives.

    Open the explorer

    Why it holds up

    Proof, not points

    A report counts only with a settled payment behind it. Forged, flipped and flooded rows are ignored, and one funding cluster can never block a merchant.

    Forgiving by design

    Blocks end, strikes are forgotten after 60 days, and a blocked merchant can rebut once, pass a paid probe and recover through probation.

    Fails safe

    If ENS, Arkiv or Mirror Node fails, payments escalate to the owner. An outage never turns into a silent ALLOW.

    The LLM cannot approve

    There is no approve tool. Only the owner's signature, bound to one challenge for 120 seconds, releases an escalated payment.

    All fifteen failure modes in the spec were caused for real on the testnets, from spoofed merchants to cut connections and flooded registries. See what was tested.

    Built on

    Hedera x402

    Agents pay merchants in test USDC through the Blocky402 facilitator. Mirror Node gates every report, and every decision goes to an HCS audit topic.

    Arkiv

    The registry itself: wallet-owned entities with attribute queries, and expiry as the way a merchant is forgiven.

    ENSv2

    Merchants declare themselves in leash.* text records on a Permissioned Resolver, with a per-key role for rebuttals.

    Put your agent on a leash

    One SDK call wraps your x402 client, or run the MCP server and let your LLM pay through it. Either way, the owner stays in charge.