# Liquidity model

With the introduction of Squid Intents, Squids liquidity model has evolved to provide superior pricing and efficiency. By leveraging post-deposit RFQ auctions and TEE-verified batched settlement, Squid Intents minimizes onchain logic and maximizes execution quality. Squid Intents sources liquidity differently from traditional AMM-based bridges. Instead of routing through fixed liquidity pools, Squid Intents runs post-deposit RFQ auctions where market makers compete to fill your order at the best available price.

<figure><img src="/files/LxrVat1Rh8mfxDQPMOx6" alt=""><figcaption></figcaption></figure>

This approach allows for tighter pricing, reduced slippage, and a more robust liquidity provision across diverse chains. The system now supports a wider range of market makers and ensures that users consistently receive the best available market price at execution time. Squid supports swapping any to any token across all the chains it supports, utilising existing liquidity.

### Here is how it works:

RFQ Auctions When you submit a swap, Squid Intents opens an auction on the source chain after your deposit lands. Market makers bid to fulfill the order on the destination chain. The winning solver settles your tokens directly, hedging their position milliseconds after winning. You get the best market price at execution time, not a pre-quoted estimate padded for volatility.

### Offchain Coordination, Onchain Settlement

All execution logic runs offchain inside Squid's TEE-verified infrastructure. The only thing that touches the chain is what must be true in any trade: a token transfer. This keeps gas costs near zero and eliminates the slippage risk that comes with routing through AMM pools.

### Any Token, Any Chain

Squid Intents is not dependent on wrapped or synthetic assets to route liquidity. Market makers supply liquidity natively across chains, which means Squid can support any token on any chain, including chains without smart contracts like Bitcoin, Solana, and XRPL.<br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.squidrouter.com/additional-resources/architecture/liquidity-model.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.