
Squid Review
Named, linked audits and wide chain coverage for routed swaps
of 10
Squid scores 6.0 out of 10 in bridges: nine audits by four named firms with linked reports, and more than 100 chains claimed. Its router code carries no published licence, its frontend convenience fee has no published rate, and its TEE settlement model names no weak points. Desk research, checked November 6, 2026.
Fees
No protocol fee; convenience fee on some frontend routes, rate unpublished
Settlement
Squid Intents (RFQ + Cubist TEE), or Axelar, Chainflip, CCTP, LayerZero
Licence
No router-contract repository; Apache-2.0 only on audits/examples/assets
Chains
100+ claimed; 39-entry table; Intents on 18 EVM chains
Audits
Ackee (6), Consensys Diligence, Kaden, n-Var; June 2022 to Sept 2024
Scores
Each criterion carries equal weight. The overall score is the average of these 5 scores — (6.0 + 5.0 + 2.0 + 9.0 + 8.0) ÷ 5 = 6.0.
Pros
- Audit disclosure 8: nine audits by Ackee, Consensys Diligence, Kaden and n-Var, with dates, scope and reports
- Chain coverage 9: 100+ chains claimed, with a 39-entry supported-chains table by bridge type
- No protocol fee and no fee on CCTP legs, both stated in the docs
- Squid Intents settlement flow documented: deposit, RFQ auction, fill, TEE-verified release, 15-minute refund
Cons
- Licence 2: no public router-contract repository; SDK and widget repositories carry no licence
- Fee transparency 6: frontend convenience fee on some routes, with no rate or route list published
- Trust model 5: no TEE operator, failure case or per-route trust model stated
- Newest audit is from September 2024, and none covers the off-chain TEE system
How Squid scores in bridges
This entry rates Squid in our bridge ranking. Squid is a cross-chain router rather than a single bridge. It settles each request through its own intent auctions (Squid Intents) or through outside networks such as Axelar, Chainflip and Circle's Cross-Chain Transfer Protocol (CCTP). The basis is desk research of Squid's documentation, its terms and its GitHub organization, checked on November 6, 2026. No swap was made. The category uses five criteria, each marked 0 to 10 and weighted equally, as set out in our ratings methodology.
| Criterion | What the sources show | Mark |
|---|---|---|
| Fee transparency | No protocol fee, and no fee on CCTP legs. A frontend convenience fee applies on "certain routes," with no rate or route list published. Integrator fees are set by each app, and Squid takes a portion. | 6 |
| Trust model disclosure | Squid Intents is described step by step: deposit, an off-chain request-for-quote (RFQ) auction, a market maker fills on the destination chain, and a trusted execution environment (TEE) run on Cubist's platform verifies the fill and signs the release. No weak points, operator set or failure case beyond a refund is described. | 5 |
| Licence & code openness | No public repository for the router contracts. Apache-2.0 appears only on the audits, assets and examples repositories, and the SDK and widget repositories carry no licence. | 2 |
| Chain coverage | "100+ chains" claimed. The supported-chains table by bridge type lists 39 entries, and Squid Intents names 18 EVM chains, with Bitcoin and Solana marked "coming soon." | 9 |
| Audit disclosure | Nine audits on the audits page by four named firms (Ackee Blockchain, Consensys Diligence, Kaden, n-Var), with dates, scope and linked reports. The public repository holds ten PDFs, from June 2022 to September 2024. | 8 |
The overall score is the plain average: (6 + 5 + 2 + 9 + 8) / 5 = 30 / 5 = 6.0.
Four marks changed at this check, and the overall rose from 4.8 to 6.0. Audit disclosure rose from 2 to 8 because the audits page now names every firm and links each report. Trust model disclosure rose from 3 to 5 now that the architecture pages describe the Squid Intents settlement flow. Fee transparency fell from 9 to 6. The fees page and FAQ now say a convenience fee is charged on some frontend routes, without a figure, so the earlier "no fees beyond gas" reading no longer holds. Chain coverage rose from 8 to 9 under the single network-count scale the category now applies to every bridge, on which 25 or more documented networks score 9.
Strongest criteria: audits and chain coverage
Audit disclosure scores 8. Squid's audits page lists six Ackee Blockchain reviews, one by Consensys Diligence, one by Kaden and one by n-Var. Its records table gives each audit's date and the contracts in scope, such as SquidRouter.sol, SquidMulticall.sol and the deposit-service contracts, and the reports are on GitHub. The public repository holds a tenth report, a second n-Var review from 2024. The mark stops short of the top for two reasons: the newest report dates from September 2024, and no audit covers the off-chain TEE system that now settles Intents routes. An audit is not insurance.
Chain coverage scores 9 on a claim of more than 100 chains, backed by a 39-entry table in which some rows, such as "Cosmos - other chains," stand for several networks. The documentation is candid that availability differs by route type. Bitcoin and Solana appear in the table but are marked "coming soon" for Squid Intents, and Squid asks integrators to confirm availability with its team.
Weakest criteria: licence, trust model and fees
Licence & code openness at 2 is a deficiency, not an unchecked item. The 0xsquid GitHub organization publishes audit reports, examples and type definitions, but no repository for the router contracts the audits cover. The SDK and widget repositories carry no licence file. The rubric scores the licence on the code that moves funds, and none is published.
Trust model disclosure at 5 credits a clear description of how an Intents trade settles. Funds are released to the market maker only after a TEE has verified the fill, and a failed trade is refunded on the source chain within about 15 minutes. What is missing is the part the rubric values most: who operates the TEEs, what happens if the enclave or its signing key fails, and how users are protected against an incorrect release. Routes that use Axelar, Chainflip, CCTP or LayerZero inherit those networks' trust models. Squid does not state which applies to a given swap, and that is not visible from the docs.
Fee transparency at 6 reflects a clear zero with an unpriced exception. Squid states that it charges no protocol fee and that CCTP legs carry no fee, and gas is itemized by chain type. But the convenience fee on its own frontend has no published rate or route list. Integrator fees are elected by each app, and Squid takes an unstated portion of them. The same swap can cost different amounts in different wallets, and the figure to check is the service fee shown before signing.
What the score does not cover
- Security of the outside networks a route uses. Each has its own entry in this ranking.
- Past incidents. Squid's FAQ says it has never suffered a breach, and that is Squid's own statement. Under the category rule, we do not score incidents a protocol has not documented itself.
- Execution quality, solver competition or the speed and price claims on Squid's site, which are the company's figures.
- The QUID token, which is not needed to swap.
Our guide to how bridges work and why they are risky covers the failure modes that apply to routers and the networks beneath them.
Squid vs deBridge and Axelar
On current category marks, Axelar is first of nine at 8.6, deBridge fourth at 7.8 and Squid eighth at 6.0. deBridge is the closest intent-based peer. It publishes a flat per-chain fee plus 4 basis points and scores 9 on fees to Squid's 6, and it also leads on audits (9 to 8), trust model (6 to 5) and licence (8 to 2). Squid is ahead only on chain coverage, 9 to 7. Axelar, one of the networks Squid routes through, leads Squid on trust model, licence and audits, and the two are level on chain coverage at 9. Squid is one point ahead only on fees, 6 to 5.
Who this rating suits
The score helps a reader deciding whether to route a swap through Squid, often inside a wallet that has integrated it, rather than use a single bridge directly. Squid's audit record and breadth are documented. Its fee on any given route, its core contract licence and its TEE failure model are not. The rating is not a recommendation. For a large transfer, check the quoted service fee and which settlement network the route uses before signing.
How it compares

Axelar
Open-source code and the deepest dated audit archive among bridges

Wormhole
A numbered guardian quorum and a deep, named audit record

Celer cBridge
Open-source contracts with a stated fee range and threshold

deBridge
Per-chain flat fees and a dated audit archive

Chainflip
Native-asset swaps with a published custody threshold and fee table

Across
The clearest statement of a bridge's security assumption

Stargate / LayerZero
Broad chain list and named audits at every protocol stage

Synapse
MIT-licensed code and a documented optimistic relay network
Sources
Scored from published primary sources rather than hands-on use. Every figure above comes from one of the pages below, on the date shown. Manufacturers change prices and specifications without notice — if something here no longer matches the source, tell us and we will correct it.
- 1.Squid docs: Transaction times and fees — checked
- 2.Squid docs: FAQ — checked
- 3.Squid docs: Architecture — checked
- 4.Squid docs: Squid Intents — checked
- 5.Squid docs: Audits & Security — checked
- 6.Squid docs: Supported chains by bridge type — checked
- 7.Squid GitHub: audits repository — checked
- 8.Squid GitHub: 0xsquid organization — checked
Frequently asked questions
Why does Squid score 6.0?
It is the plain average of five equal marks: fee transparency 6, trust model disclosure 5, licence 2, chain coverage 9 and audit disclosure 8. Audits and coverage are strong; licence is the main drag.
What changed since the previous Squid review?
The overall rose from 4.8 to 6.0. Audits went from 2 to 8 because every firm and report is now named and linked, trust model went from 3 to 5 for the documented Intents flow, and chain coverage went from 8 to 9 under the category's single network-count scale. Fees fell from 9 to 6 because of an unpriced frontend convenience fee.
Does Squid charge a fee?
It says it charges no protocol fee and nothing on CCTP legs. A convenience fee applies on some routes in Squid's own app, with no published rate, and wallets that integrate Squid can add their own fee. The quoted service fee is the number to check.
What holds Squid's score back most?
The licence. Squid publishes no repository for the router contracts its audits cover, so the code that moves funds carries no licence anyone can read.
How does Squid compare with deBridge and Axelar?
At this check, Axelar reads 8.6, deBridge 7.8 and Squid 6.0. deBridge leads Squid on fees, audits, trust model and licence, and Squid leads it only on chain coverage. Axelar, which Squid routes through, leads on licence, trust model and audits.
Nothing here is financial advice. Editorial policy · How we score · How we're funded.