Intent types
The SDK exports three intent type sets, one per execution shape:Intent fields
Every intent carries:executorFeesHash, swapDataHash) bind the off-chain intent to the exact on-chain action. A solver cannot rewrite the swap and reuse your signature.
Lifecycle
1
Quote
Frontend asks
getZapQuote(). Response includes txId, candidate steps, and the typed-data structure to sign.2
Sign
User signs the EIP-712 typed data with their wallet. Output: a signature bound to the intent hash.
3
Submit
Signature + intent posted to the Fuse API (or directly to a solver).
4
Match + execute
A solver picks up the intent, verifies signature on-chain, executes the bundle.
5
Settle
User receives the final asset on the destination chain. Status visible via
getZapTxnStatus().Why intents instead of transactions?
- Gasless, solver pays gas; user pays only via the swap output.
- Atomic outcome, user signs the destination state, not the path.
- Composable, intents compose with bundles (multi-leg flows).