Treat wallet error 4001 as a user decision
Handle EIP-1193 rejection as a cancelled wallet action and keep earlier confirmed steps intact.
Explore the reference
Integration engineering — page 4
Handle precision, validation, reliability and the operating details behind a swap interface.
69 guides · Page 4 of 4
Use a circuit breaker for a failing quote service
Temporarily pause new requests to a failing quote service while keeping pending trade reconciliation available.
Use a content security policy around wallet-facing code
Roll out a browser content security policy around swap scripts, network connections and embedded frames without treating it as transaction validation.
Use fork tests to reproduce a swap integration failure
Pin chain state and preserve the original transaction context when reproducing a swap failure on a fork.
Validate swap API responses at runtime
Add runtime validation at the provider boundary so malformed or newly changed response shapes cannot reach wallet execution.
Validate swap deep links before pre-filling a form
Parse swap deep links as untrusted form suggestions and validate chain, tokens, amount and recipient before use.
Validate the swap recipient separately from the sender
Treat sender, signer and output recipient as separate roles, and reject unsupported recipient combinations before quoting.
Validate typed-data domains before asking for a signature
Validate the signing domain and trade message before handing EIP-712 typed data to a wallet.
What can a swap quote cache safely reuse?
Choose cache keys and freshness rules separately for indicative prices, executable quotes and account-specific validation.