Settlement security combines threshold authorization, validated chain evidence, and contract enforcement. Each mechanism has a separate responsibility.

Threshold trust

If the Attester Network has n attesters, signing requires the configured threshold t. Fewer than t compromised shares cannot produce a valid group signature under the scheme’s security assumptions. A compromised threshold can produce false attestations under that key. Unavailable members can prevent signing when fewer than t members can participate. TSS distributes signing authority. It does not remove trust in the Attester Network or guarantee availability.

Event validity

Attesters derive proofs from observed source orders and destination fills. They verify output identity and apply confirmation requirements before signing. RPC omissions, unavailable historical data, and chain reorganizations can delay or invalidate observations. Independent processes can still share an upstream infrastructure failure. An attestation signature does not include a consensus proof from the destination chain. The input oracle verifies Attester Network authorization over the fill tuple. This trust model differs from IBC light-client verification.

Replay boundaries

The fill description includes the order identifier and exact output fields. The proof tuple includes the destination chain, remote oracle, output settler, and fill hash. These fields bind the signature to its execution context. The EVM proof digest does not add the origin chain or input oracle address as separate fields. The EVM order identifier commits to the origin chain identifier, escrow address, input oracle, and encoded order terms. Do not assume domain separation beyond the implemented encoding.

Verification boundaries

The watcher has separate deadline-extension authority. That authority can delay refunds within contract rules. It cannot replace fill proofs or authorize custody transfers. The EVM contract does not require proof of a fill before accepting an authorized extension. The watcher’s all-output fill requirement is service policy, not a contract restriction on the extension role. Attestations do not lock the deposit against refunds. A filled order can still be refunded before finalisation if its effective refund deadline has passed. The solver depends on timely finalisation or a confirmed extension to reduce that exposure.