> 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/token-bridge.md).

# Token Bridge

The TokenBridge is the on-chain component responsible for securely transferring tokens between Neo N3 and Neo X. It processes token deposits and withdrawals, locks or releases assets accordingly, and maintains a per-token, per-direction hash chain that records the ordered history of all token-bridging operations.

Each token direction (N3 → Neo X and Neo X → N3) has its own independent `(nonce, root)` state. This state provides a verifiable cryptographic commitment to all operations processed in that direction. Validators observe these events, reconstruct the hash-chain state, and attest to the new top root, enabling the relayer to submit authenticated batches to the destination chain.

By enforcing deterministic hash-chain reconstruction and requiring validator threshold signatures, the TokenBridge ensures that all token transfers across chains occur transparently, securely, and without relying on any trusted off-chain party.


---

# 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/token-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.