See Terminology for the component and protocol definitions. Infinity Intents uses the Open Intents Framework (OIF) order model. An origin chain holds the input deposit. A destination chain records delivery of each required output.

Components

Infinity Hub does not hold signing-group key shares. The engine also holds no signing-group key shares. A separate threshold signing daemon, TSSD, holds each node’s share. The engine independently derives the requested signing digest before confirming it to the daemon.

Execution boundaries

The solver binary fills orders and finalises settlement. The verifier binary performs the attester role and participates in distributed key generation. The watcher binary extends eligible EVM and Solana refund deadlines. Each binary has separate configuration and durable state. Infinity Solvers is the TSS-powered committee that custodies solver funds. Infinity Solvers and the Attester Network use separate signing identities: SPEND and ATTEST. Transaction fee keys pay network fees. They do not replace the authorization of Infinity Solvers over custody.

Cross-chain execution

  1. Obtain a quote from Infinity Hub.
  2. Validate its executable payload against the user’s request and trusted deployment addresses.
  3. Authorize the intent through its selected execution mechanism.
  4. Deposit the input into the origin escrow.
  5. Track the destination fill.
  6. Track attestation and origin finalisation.
A same-chain swap has a different execution model. The wallet submits a router transaction without cross-chain escrow settlement or solver reimbursement. See same-chain swaps.

Availability and deployment scope

The catalog describes configured assets and chains. A quote establishes current route availability. Source support does not establish destination support, watcher support, or live deployment availability. Infinity Hub’s public gateway and direct service expose different authentication interfaces. See authentication before selecting an integration surface.