Review SDK upgrades as execution changes
Review swap SDK dependency updates for transaction and signing changes, using locked builds and semantic payload comparisons.
Explore the reference
Handle precision, validation, reliability and the operating details behind a swap interface.
69 guides · Page 3 of 4
Review swap SDK dependency updates for transaction and signing changes, using locked builds and semantic payload comparisons.
Refresh an expired RFQ quote instead of retrying its old transaction payload, and distinguish expiry from transport uncertainty.
Include the actual taker in RFQ request identity and invalidate firm quotes when the execution account changes.
Separate discovery, execution and history controls so a paused or retired provider cannot strand pending attempts.
Rotate provider credentials while preserving quote attempt IDs, pending transactions and the separation from wallet authority.
Check head freshness and block identity when switching RPC endpoints so older state cannot undo a confirmed approval.
Map errors to actionable application states using separate HTTP, provider, wallet and receipt evidence.
Use a shared deadline for parallel quote requests and present partial coverage without implying every provider responded.
Expire quote review state predictably and separate a local countdown from the provider and settlement deadlines.
Build authenticated HTTP requests from one immutable serialized path and body so HMAC inputs match transmitted bytes.
Construct a meaningful preflight call from the actual sender, destination, calldata and native value of the proposed swap.
Check EIP-1271 and provider execution support before offering signature-based swaps to contract accounts.
Use state overrides for diagnosis while preserving the distinction between hypothetical and current-wallet simulation.
Combine input debounce, request cancellation and response identity checks to prevent old quotes replacing new trades.
Use chain-and-address keys for tokens, with a separate native-asset type and explicit metadata fallback rules.
Track permit nonce consumption, signature deadline and allowance expiration separately when diagnosing invalid signatures.
Follow the account and nonce when a pending swap is replaced, accelerated or cancelled under a new transaction hash.
Preserve encoded swap calldata while validating its envelope and use only version-matched decoders for inspection.
Represent proprietary AMM sources by documented routing and execution capabilities instead of assuming constant-product behavior.
Require explicit route support for transfer-tax tokens and reconcile received amounts instead of applying a guessed tax correction.