STX and sBTC escrow

Use escrow when work is asynchronous, a neutral evaluator decides the outcome, or the client needs an explicit refund path.

Roles

• Client: creates and funds the job.
• Provider: accepts the work and submits a deliverable.
• Evaluator: completes or rejects the submitted work.

Completion pays the provider and updates job-linked reputation. Rejection and eligible expiry return escrow according to the contract lifecycle.

Active review-window lifecycle

The active versioned release begins a fixed 12 Bitcoin burn-block review window when the provider submits work. The evaluator can approve or reject through the exact deadline. After the deadline, any caller can release escrow to the provider so an unavailable evaluator cannot trap funds.

The exact v4/v3/v3 sources first passed controlled STX and official PoX-5 sBTC paths on testnet, including a real timeout payout. They were then source-verified on mainnet and a guarded internal 100-atomic-sBTC lifecycle passed 26/26. Internal actors remain release evidence, not external adoption or revenue.

TimeoutPaid (u6) proves that the provider received escrow through the liveness path. It is not a completed-job attestation, cannot be rated and does not increment completed or disputed reputation. If a normal completion or rejection cannot write reputation, settlement remains final and the recorded synchronization can be retried permissionlessly.

Asset-specific funding

STX funding constrains the exact micro-STX transfer. sBTC funding constrains the canonical SIP-010 token and exact satoshi amount. The SDK hides signature differences but preserves explicit post-conditions.

See contract reference and settlement semantics.