Squid Intents
Squid's Intent Swaps Protocol
Squid Intents is Squid's intent-based settlement protocol transforming how regular crosschain swaps are executed. It turns user intent into simple onchain transfers and handling complex execution offchain using Trusted Execution Environment (TEE)-verified settlement. Squid Intents offers unparalleled reliability, better pricing, and a smoother user experience across EVM and non-EVM chains alike.
As crosschain logic is handled by TEEs, it delivers efficiency while maintaining the decentralized and non-custodial nature of the protocol while ensuring that Squid can expand to any chain and any token, including chains that don’t have smart contracts.
Squid’s TEEs are powered by Cubist, who we chose for their formidable security background, having secured over $10B USD already, and their commitment to crypto's original values: decentralization and privacy. Their approach ensures high availability, censorship resistance, and decentralized upgrade and deployment pathways for protocols developing on their platform.
Why Squid Intents?
Sub-5 second execution for most transactions
Zero slippage guaranteed through direct market maker integration
90% reduction in gas costs compared to traditional AMM-based routing
MEV protection built into the protocol architecture
No route expiry: routes don't expire, submit your transaction at any time after receiving a quote
15-minute refunds: if a transaction fails, funds are automatically returned on the source chain
Integrator fee support built in
Squid Intents Competitive landscape
TEE-Verified Settlement
✅
❌
❌
❌
✅
❌
Post-Deposit RFQ Auctions
✅
❌
❌
❌
❌
❌
Native Bitcoin Support
✅
❌
❌
❌
❌
❌
Native Solana Support
✅
✅
✅
❌
❌
✅
Native XRPL Support
✅
❌
❌
❌
❌
❌
Guaranteed 15-Min Refunds
✅
❌
❌
❌
❌
❌
No Route Expiry
✅
✅
✅
✅
✅
✅
Multisig Compatibility
✅
✅
✅
✅
✅
✅
Zero-TVL Architecture
❌
❌
✅
❌
❌
❌
MEV-Resistant Privacy
❌
❌
❌
❌
✅
❌
How It Works
Squid Intents uses the /v2/route endpoint as all Squid transactions. For EVM-to-EVM swaps, the flow is identical to a standard Squid integration — request a route, execute it, and poll for status.
The route response's transactionRequest object will include a transaction_request_type field that indicates how to execute:
"ON_CHAIN_EXECUTION"— standard on-chain transaction (EVM)"DEPOSIT_ADDRESS_CALLDATA"— submit a deposit to the provided address with the specified calldata (non-EVM)"DEPOSIT_ADDRESS_WITH_SIGNATURE"— submit a signed deposit to the provided address (non-EVM)
Getting Squid Intents Enabled
Squid Intents is not enabled by default. To get started:
If you don't already have a Squid integration, apply for an integrator ID
Contact the Squid team to enable Squid Intents on your integrator ID
Follow the Integrating Squid Intents guide
Widget Users: Coral V2 requires @0xsquid/widget version 6.5.0 or newer. Please ensure your widget is updated before enabling Coral V2.
Supported Chains
Squid Intents currently supports the following chains:
EVM Chains: Celo, BNB Chain, Citrea, Peaq, HyperEVM, Avalanche, Optimism, Arbitrum, Linea, Berachain, Polygon, Gnosis, Base, Sonic, Hedera, XRPL EVM, Soneium, Blast
Coming Soon: Bitcoin, Solana
Last updated