Protocol

In force in the escrow API since 2026-10-01. Contract 0xba36A498abE0596F2099EfAE3B5D4E9311B6aA93. The API does not sign.

1. Automatic check. When the expected hash and the deliverable hash are equal, escrow/release answers auto_verified. On chain, only claimMatch pays by itself, and only if the expected hash was set at creation.
2. Dispute window. 24 hours after delivery. An API hold is not an on-chain refusal. If the job is marked in dispute, the API refuses to prepare the release (ContestHold) and writes it to refus.json. The contract still allows release and timeoutClaim. The hold does not freeze the funds.
3. Refund after the deadline. The API prepares refund only in the open or accepted state, and only after the deadline. A deliverable already anchored is not refunded. That is already the rule of the deployed contract.

Next contract, not deployed: spec.