> For the complete documentation index, see [llms.txt](https://docs.moremarkets.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.moremarkets.xyz/protocol-concepts/message-passing-systems/omni-bridge.md).

# Omni Bridge

### What is Omni-Bridge?

The [Omni Bridge](https://github.com/Near-One/omni-bridge) is a multi-chain asset bridge that facilitates secure and efficient asset transfers between different blockchain networks. It solves key challenges in cross-chain communication by leveraging [Chain Signatures](https://docs.near.org/concepts/abstraction/chain-signatures) and its decentralized [Multi-Party Computation (MPC) service](https://docs.near.org/concepts/abstraction/chain-signatures#multi-party-computation-service) to enable trustless cross-chain asset transfers. How it works:

* Uses Chain Signatures, NEAR's transaction signing system, to enable trustless cross-chain asset transfers
* Uses decentralized Multi-Party Computation (MPC) to solve challenges in cross-chain communication
* Eliminates technical constraints of traditional bridge designs
* Delivers faster finality, lower costs, and enhanced scalability<br>

### **How Omni Bridge Works in MoreMarkets?**

Omni Bridge is used as a message passing layer between NEAR Protocol Chain Signature enabled vaults on the Principal Chain and Receipt Chain.

This includes forward messaging to signal the Receipt Chain BoringVault to mint Receipt Tokens and backward messaging to signal liquidation/slashing and minting of Positional Tokens.&#x20;


---

# 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://docs.moremarkets.xyz/protocol-concepts/message-passing-systems/omni-bridge.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.