> For the complete documentation index, see [llms.txt](https://monoprotocol.gitbook.io/monoprotocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://monoprotocol.gitbook.io/monoprotocol/architecture/liquidity-lock-and-fast-path.md).

# Liquidity Lock & Fast Path

The **Liquidity Lock** concept, introduced by Mono Protocol, has significantly enhanced multichain transaction efficiency. More specifically, it allows asynchronous execution of a multichain intent, separating intent fulfillment from settlement, which makes multichain transactions feel like same-chain transactions for the user.

Applications enable Liquidity Locks via the Toolkit. Once enabled, all user transactions are co-signed (sequenced) by Mono Protocol, preventing double-spending during asynchronous multichain executions.

**How Liquidity Locks Work:**

Liquidity Locks are managed by Mono Protocol's LL Service, which performs four critical functions:

1. **Verifies**: Validates user on-chain and locked balances
2. **Co-signs**: Adds signatures to operations, ensures control over account state transition and prevents double-spending
3. **Provides Guarantees**: Issues security attestations to solvers for immediate delivery, given delayed settlement
4. **Tracks Positions**: Ensures not yet settled balance follows risk policies to maintain system integrity

**Key Benefits:**

* **Speed**: Execute cross-chain transactions in seconds instead of minutes
* **Reliability**: Cryptographic guarantees ensure 100% transaction success
* **Cost Efficiency**: Reduce gas costs by up to 40% through batched settlements


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://monoprotocol.gitbook.io/monoprotocol/architecture/liquidity-lock-and-fast-path.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.