Infinity Settlement checks each cross-chain message through three independent layers: Infinity Attest, Infinity Checkpoint and Infinity Verify. A solver delivers the requested assets before it receives the user’s source deposit. Infinity Settlement helps establish that the delivery matches the order the user approved. This gives the solver the evidence it needs to collect payment.

Three layers of verification

Verification Policies, which will set which layers must approve a message, are not available yet. The rest of this section documents the Attest path: attesters check a delivery and sign it, and the solver submits the proof to the source chain’s contracts. An attester is a member of the Attester Network. It checks delivery records from the blockchain against the approved order. Attesters work together to create a signed statement about a verified delivery. The solver uses this statement as proof when it asks the source contracts to release the deposit.

From delivery checks to solver payment

The attester labels illustrate the process, not a fixed Attester Network size. The Attester Network configuration sets how many attesters must participate in signing.

Check what the user received

The approved order tells attesters what the solver must deliver. Each participating attester checks the recorded asset, amount, recipient, and destination network. It also checks that the delivery came through the expected contracts and met the order’s conditions. Attesters wait for the required network confirmations before they sign. These confirmations reduce the risk that the network later removes the delivery record. An application message saying “complete” is not enough. The checks use blockchain evidence. If an order requires several deliveries, each delivery needs its own verified evidence. A missing or incomplete record delays the proof for that delivery.

Sign the verified delivery

The Attester Network uses a threshold signature scheme (TSS) to share signing authority across its attesters. The required number of members must participate to create a valid group signature. Each participating attester checks the evidence before it approves signing. One member cannot sign alone when the required number is greater than one. The resulting signature acts as a signed receipt for that delivery. It identifies the delivery being confirmed, so the source contracts can check the proof against the order. The signature does not move the user’s deposit by itself.

Let the solver complete settlement

The source deposit waits in an escrow, a contract that holds assets until its release conditions are met. The solver collects the required signed proofs and submits them for verification on the source network. The solver then finalises the order: it asks the escrow to release the deposit to the approved payout address. The source contracts check the proofs and the solver’s authority before releasing the assets. The attesters confirm delivery; the solver completes settlement. The recipient can therefore receive the destination assets before the solver receives payment from the escrow.

When settlement takes longer

Network delays, unavailable attesters, or missing evidence can delay settlement after the recipient receives the assets. On supported source networks, an authorized watcher can give eligible delivered orders more time before a refund becomes available. This gives the solver more time to complete settlement, but also delays the user’s refund opportunity. A signed receipt does not guarantee payment to the solver. On EVM source networks, a refund can still succeed before the solver finalises if the effective refund deadline has passed. See finalisation and refund timing for the EVM contract rules.

Attester Network

How attesters check delivery and create signed proofs for the Attest layer.

Security model

What the checks protect and which assumptions they depend on.