Finalisation releases the origin escrow deposit after the required destination fills are proven. The solver performs finalisation. The Attester Network supplies fill attestations.

Procedure

  1. Collect the published attestations for each required output.
  2. Verify each signature against the order’s expected attestation key and signature suite.
  3. Submit the required proofs to the origin input oracle.
  4. Confirm that the oracle records every required output proof.
  5. Obtain the Infinity Solvers custody authorization required by the finalisation path.
  6. Submit the finalisation transaction to the origin escrow.
  7. Confirm the terminal settlement event at the configured observation depth.

Output ownership

In the engine’s normal settlement path, the first output’s recorded solver determines settlement ownership. The EVM escrow also supports recorded order purchases that can assign finalisation authority to a purchaser. Every output still requires its own valid fill proof. The engine does not treat a first-output proof as proof of the remaining outputs.

Separate authorizations

The Attester Network signs fill evidence. Infinity Solvers authorizes the settlement payout instruction where that path requires a signature. An attester signature cannot replace the Infinity Solvers custody authorization. The EVM escrow provides finalise and finaliseWithSignature entry points. The engine selects the chain-specific custody path and binds its payout destination. The escrow validates fill deadlines, proofs, and caller or signature authority before releasing the inputs.

EVM deadline and refund race

Each proven fill timestamp must be less than or equal to fillDeadline. Finalisation itself can occur after expires or the effective refund deadline. The order must still be deposited when finalisation executes. A watcher extension is not a prerequisite for finalisation. After the effective refund deadline, anyone can call refund(order) while the order remains deposited. The refund function does not check destination fills or published attestations. It can therefore refund a filled order before finalisation succeeds. Finalisation and refund compete for the same deposited state; the first successful transaction prevents the other. A refund returns the escrow deposit to the user without reversing destination delivery. An extension can delay refund eligibility while the solver obtains proofs and submits finalisation. It cannot recover a deposit after a successful refund.

Recovery and terminal state

An unavailable proof, pending receipt, or expired local timer does not prove that settlement failed. The engine preserves the paid order while it reconciles transactions and effective refund deadlines. An observed refund or finalisation establishes the terminal contract result. An Infinity Hub status response is a projection of upstream or chain evidence. Applications must distinguish destination delivery from origin finalisation. See order status for the API views.