The Attester Network provides the Infinity Attest layer of Infinity Settlement. Attesters are staked, and their group key comes from an on-chain distributed key generation (DKG). Slashing is not active yet. Infinity Attest is in active development and devnet testing. See Terminology for the component and protocol definitions. An attester runs the engine’s verifier binary with a separate threshold signing daemon. The attester validates orders and fills. The daemon holds its Attester Network key share.

Validation sequence

  1. Observe the source order through the configured escrow.
  2. Validate the order identity and supported chains.
  3. Observe the destination fill through the configured output settler.
  4. Apply the configured confirmation depth.
  5. Match the fill to the required output.
  6. Derive the proof tuple from local evidence.
  7. Confirm the requested digest to the signing daemon.
  8. Participate in the threshold signing ceremony.
  9. Publish the resulting signature to the attestation registry.
Each output is verified and attested separately. The signed payload binds the solver identifier, order identifier, timestamp, token, amount, recipient, callback data, and context. The proof tuple also identifies the destination chain, remote oracle, and output settler.

Local confirmation

Each node reconstructs the requested digest from its own evidence. It does not accept an arbitrary digest supplied by another participant. Missing evidence, a failed reconstruction, or a confirmation timeout prevents signing. The signing request selects the signature curve and key generation explicitly.

Canonical fill evidence

For EVM and Solana fills, the engine checks the recorded solver and timestamp against the destination settler’s fill record. A replacement observation must satisfy confirmation requirements and match that record. The engine increments fill_revision when it adopts a replacement. Obsolete ceremony results cannot update the new revision. An unreadable fill record defers processing. It does not establish that a replacement is valid. Previously issued signatures cannot be revoked by a local record update. The protocol therefore still depends on its chain finality assumptions.

Missing observations

The engine can recover known unfinished orders from durable state. It can also search configured EVM and Solana origins when fill or Attester Network evidence identifies a missing source order. Incomplete RPC history can prevent recovery. An attester does not attest a fill without the required source order evidence. Infinity Hub’s observers provide application status data. Their observations do not replace the attester’s own validation.