# Liquidity Locks

Liquidity Locks are Mono Protocol's innovative solution that transforms cross-chain transactions by delivering three critical improvements: **speed**, **reliability**, and **cost efficiency**.

Liquidity Locks enable cross-chain transactions to execute at the speed of the destination chain while providing cryptographic guarantees and reducing operational costs through optimized settlement patterns.

**Evolution of Cross-Chain Bridging:**

**Classical Bridge**

* **Critical Path**: Source chain finality + Destination chain inclusion
* **Typical Duration**: 3 minutes or more

**Intent Bridge**

* **Critical Path**: Source chain inclusion + Routing + Destination chain inclusion
* **Typical Duration**: 15-45 seconds

**LL-enabled Bridge**

* **Critical Path**: Lock verification + Routing + Destination chain inclusion
* **Typical Duration**: 5-10 seconds

**Key Technical Innovations:**

**Advanced Locking Protocols:**

* Cryptographic commitments for cross-chain operations
* Time-based and condition-based unlock mechanisms
* Fail-safe mechanisms for network disruptions
* Mathematical guarantees for execution completion

MEV Protection Layer:

* Pre-trade privacy through commit-reveal schemes
* Optimal execution routing to minimize value extraction
* Protection against front-running and sandwich attacks
* Fair sequencing and execution for all transactions


---

# 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://monoprotocol.gitbook.io/monoprotocol/architecture/liquidity-locks.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.
