> For the complete documentation index, see [llms.txt](https://docs.wanchain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wanchain.org/wanchain-bridge-nodes/deploy-a-bridge-node.md).

# Deploy a Bridge Node

To ensure the best operational experience and long-term maintainability, Wanchain provides two distinct paths for node management. Please choose the method that matches your current status:

**🟢** [**How to deploy a Bridge Node via XStake (Recommended)**](/wanchain-bridge-nodes/deploy-a-bridge-node/deploy-a-bridge-node-via-xstake-recommended.md)

**Best for: All new node registrations and modern maintenance.**

* Why choose this: This modern, web-based solution supports popular wallets like MetaMask and utilizes the Ethereum derivation path for addresses, offering superior compatibility and easier management for most users.

**⚪** [**How to deploy a Bridge Node via WanWallet Desktop (Legacy)**](/wanchain-bridge-nodes/deploy-a-bridge-node/how-to-deploy-a-bridge-node-via-wanwallet-desktop-legacy.md)

**Best for: Existing operators who previously created nodes via the Desktop wallet.**

* Why choose this: This guide is intended as a technical reference for users who already have nodes running on the desktop client. 
* Note: We do not recommend this method for creating new nodes. It utilizes the Wanchain derivation path for addresses.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.wanchain.org/wanchain-bridge-nodes/deploy-a-bridge-node.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.