data · hero agent
data.acme.leash.eth
reading policy from ENS…
judge sandbox · no login · no wallet · no ETH
acme.leash.eth · live spend policy
The org declares each agent's cap and allowlist on its ENS name. The facilitator we run reads that ENS-declared policy and enforces it on every payment. Every button below runs a real on-chain action — watch the ENS record (left) and the payment result (right) move together.
ENS record · leash.policy
reading…on-chain read · eth_call → resolver.text(name, "leash.policy")
querying ENS…
Payment result
idlelive rail · facilitator settle / 402 / funding
Run a beat below. The result of the latest action shows here, side by side with the record it was checked against.
run the flow
The hierarchy under acme.leash.eth — two children, distinct caps
reading…
payments
payments.acme.leash.eth
reading policy from ENS…
audit trail · Hedera Consensus Service
View audit log ↗Every ALLOW / DENY the facilitator makes is logged to topic
0.0.10496492.