Skip to content

Escrow deployment settings ​

Use Deploy a new instance, substituting the escrow app prefix. This page covers Escrow's choices and acceptance checks, not a second release procedure.

Choose who controls publication

ContractAuthority after deployment
CamEscrowImmutable business rules; no owner, pause, upgrade, fee, sweep or administrator recovery.
CamEscrowUIRead-only projection with an immutable backing contract. No write-forwarding or ownership role.
CamRootThe current owner controls the manifest URI/hash and contract bindings.

Choose INTENDED_CAM_ROOT_OWNER deliberately. The publication signer can nominate a different owner; that nominee must separately call acceptOwnership() on the root address in the final CAM publication artifact. There is no CAM acceptance delay. The current owner remains authorized until acceptance.

The client chooses contractor, arbitrator, terms and durations when creating each agreement; these are not deployment-wide default authorities. An arbitrator never acknowledges participation on chain before funding.

Business creation, projection deployment and CAM publication can use separate actors and source selections. Keep their retained inputs and artifacts. Host the prepared files before approving their root publication, using the shared procedure's hosting pause.

Accept the instance, not just its records

Run escrow/release/verify with the same selected context and instance to check historical deployment evidence. It sends no transaction and preserves final records. A recorded pending nomination is valid evidence, not proof that today's handover completed.

For current acceptance, confirm the intended root's owner() and zero pendingOwner(), its exact publication/resources, and the expected business/projection bindings. Open a known read in a compatible viewer. Never infer agreement status or solvency from a successful historical verifier.

To change the projection or workflow later, use the appropriate update path. A missing artifact after successful execution belongs in recovery, not another contract creation.

Observe the boundaries that can change

Monitor root ownership nominations/acceptance and CamUpdated/ContractAddressSet. On the business contract, track agreement creation/state changes, withdrawals, outstanding deadlines and totalLiabilities() against its native balance.

No component automatically executes expired agreements. Someone must send the appropriate timeout transaction; disputes also depend on the selected arbitrator being available before their deadline. Settlement credit still requires a beneficiary withdrawal.

User workflow · Host the viewer · Publish original sources. Implementation: source 04a18763.