Resolution protocol for autonomous agents

An agent dies. Its revenue keeps arriving.

It lands in a treasury nobody operates, while the people it owed get nothing.

When a company fails
administration → liquidation → creditors paid in order
When an agent fails
nothing. the revenue just keeps arriving.

Executor is that process, for software — a resolution plan the agent commits to while it is still alive, enforced on-chain, with no one’s permission required.

Where its revenue lands right now

REVENUEGET /research · x402 · 0.01 HBAR · Hedera · Blocky402 ↗
getPaymentDestination(agentId)

treasury

0x96abf3c7…8c36d4

Treasury

Receiving
0x29eA5557
live destination
+0.2 USDC

Estate

Standby
0xD52b7C5F
armed — opens when the window lapses
+0.2 USDC
The Graph block 11,736,586
Register your own agent →
REPLAY · agent 3 · historical · active
  1. active
  2. administration
  3. liquidation
  4. resolved
01/10

Register

Four distinct role keys. Owner, signer, trustee and recovery are four addresses.

0xf018c15970d752846e
Cadence — agent 3, indexed by The Graph
heartbeats18
deadline420s
Time until anyone may act
07:00
Heartbeat window open
Creditor waterfallUnlocks at liquidation

3 claims are registered and the trustee has committed to the set. Nothing can be paid out while the agent might still recover — only a trustee-declared liquidation opens this book.

Live agentexecutor-hackathon-demo.eth · active
Destination now0x7ea7…7330
Succession lockengaged
Indexblock 11,736,586
Planlocked ✓

heartbeat cadence ≠ proof of work · the registry’s estate field is an EOA, the Estate contract is a separate venue · the ENS name resolves to the live agent, not the replayed one · a human trustee curates the claims · registry ↗