# Introduction

Most Bridge is a cutting-edge L2<>L1 bridging solution, currently supporting unidirectional transfers from Optimism and Starknet Sepolia to Ethereum Sepolia. Our innovative approach achieves unprecedented bridging finality, setting a new standard in cross-chain asset transfers.

<figure><img src="https://2030143235-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FH64ds1IpNEIOngYzWI0t%2Fuploads%2Fgit-blob-342d9a8baaacf58a3d1319783880889152f4d2f5%2Fmost%3C%3Estarknet.png?alt=media" alt=""><figcaption><p>Market Maker CLI</p></figcaption></figure>

### The Problem

Despite being advanced technologies, blockchains still can't communicate with one another seamlessly. Their native messaging systems either aren't compatible or can take an extended amount of time—sometimes up to a week—to process. With the growing number of blockchains available, users don't want their funds locked on a single network, especially when they could benefit from lower gas fees offered by L2s, for instance. At the end of the day, users should have the freedom to move their assets across networks as they see fit, without unnecessary delays or complications.

### Key Features

* **Blazing Fast**: Complete bridging in less than a minute.
* **Cost-Effective**: Only three transactions required.
* **Highly Secure**: Leverages Zero Knowledge Proofs and the Herodotus Data Processor(HDP).
* **Simple Architecture**: Minimizes attack vectors.
* **Modular Design**: Adaptable to various blockchains.


---

# 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.most.wtf/readme.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.
