Squid

• Name: Squid
• URL: https://www.squidrouter.com/
• Tags: ethereum-ecosystem bitcoin-ecosystem solana-ecosystem
• Category: cross-chain execution / swap-and-bridge aggregation / integrator-focused interoperability infrastructure
• Summary: Squid is route-and-hook middleware for cross-chain apps. The interesting part is not the bridge breadth; it is the managed execution surface — hooks, integrator gating, status APIs, and an operator-run intents path — that lets integrators outsource route construction and post-bridge actions.
• What it does:
  • Offers a single integration surface for cross-chain swaps, bridges, and contract calls across 100+ chains
  • Ships multiple developer-facing integration options including widget, API, and TypeScript SDK flows for wallets and applications
  • Lets integrators attach pre-hooks and post-hooks so one user-signed transaction can include follow-on actions like staking, minting, withdrawing, or exchange deposits on the source or destination chain
  • Exposes an intent-based settlement surface, Squid Intents, which the docs frame as handling complex crosschain execution offchain with TEE-verified settlement while preserving non-custodial execution semantics
  • Supports route/status tracking, integrator IDs, fee collection, and chain/token support discovery through its docs and API surface
• Key claims:
  • The docs homepage describes Squid as “a single integration for seamless cross-chain swaps, bridges, and contract calls across 100+ chains” including EVM, Bitcoin, Solana, Ripple, Hedera, and Cosmos
  • The official docs say Squid supports widget, API, and SDK integration paths, which is a strong signal that it should be cataloged as integrator-facing execution infrastructure rather than only as a consumer bridge frontend
  • The hooks docs make clear Squid is doing more than asset transfer: it is explicitly bundling additional source-chain or destination-chain contract interactions into the route lifecycle
  • Squid Intents is framed as a newer execution model with sub-5 second execution for most transactions, zero-slippage guarantees through direct market-maker integration, MEV protection, and no route expiry
  • The docs require an integrator ID and, for Squid Intents, explicit enablement, which suggests a managed routing/control-plane posture rather than a purely permissionless protocol-only surface
• Whitepaper: No classic standalone whitepaper or litepaper was found in this pass. The strongest first-party source surface was the official site plus the Squid docs index, hooks docs, and Squid Intents technical/integration pages; see ../whitepapers/squid-primary-sources-2026-04-26.md.
• Sources:
  • https://www.squidrouter.com/
  • https://docs.squidrouter.com/
  • https://docs.squidrouter.com/llms.txt
  • https://docs.squidrouter.com/api-and-sdk-integration/key-concepts/hooks
  • https://docs.squidrouter.com/api-and-sdk-integration/coral-intent-swaps.md
  • https://docs.squidrouter.com/api-and-sdk-integration/coral-intent-swaps/integrating-squid-intents.md

Internal linkages

• Best upward reads for execution packaging and route-control comparisons: across, skip, and li-fi.

• Keep this note on integrator enablement, hooks, managed intent paths, and route-default policy rather than treating Squid as peer to every underlying bridge or solver system.

• Last reviewed: 2026-06-05 UTC