> For the complete documentation index, see [llms.txt](https://xdocs.ngd.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://xdocs.ngd.network/bridge/general.md).

# General

A cross-chain bridge is a software protocol that allows for the smooth transfer of data and/or assets between different blockchain networks. The transfer of data can be regarded as messages moving from one chain to another. These messages may include specific actions that facilitate the transfer of crypto assets, the invocation of contracts or simply writing data to the other chain.

In the context of Neo X, this project aims to bridge:

* From **Neo N3** to **Neo X** (*N3->NeoX*);
* From **Neo X** to **Neo N3** (*NeoX->N3*);

For both directions it supports bridging tokens and arbitrary messages.

In the following sections we will elaborate on the approach to bridging, the architecture, the roles with their responsibilities, and the involved smart contracts.


---

# 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://xdocs.ngd.network/bridge/general.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.