> For the complete documentation index, see [llms.txt](https://docs.on.nexus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.on.nexus/deployment-and-integration/node-setup.md).

# Node Deployment Guide

Independent Nexus Node operation enables quantitative funds, latency-sensitive traders, and institutions to deploy self-hosted liquidity infrastructure with complete asset custody and highly customizable algorithmic trading strategies.

The Nexus Node distribution is a Dual-Mode Toolkit, operating as either a Maker Nexus (for liquidity provision and yield generation) or a Taker Nexus (for high-frequency arbitrage and strict fund protection).

> 📌 Nexus is self-custodial, meaning the asset owner retains control of their Bitcoin through their own infrastructure.

### Terminal Deployment

**Security Confirmation:** By proceeding, you confirm that you fully understand and assume total responsibility for the security of your private keys and funds.Please configure the following information to launch. *(Note: The details below serve as the unique authorization credentials for your node, authorizing Bitcoin network transaction broadcasts and ensuring the continuous operation of the node.)***Deployment Network（mainnet/testnet4）:**

* **Authorization Wallet Mnemonic:** Enter words separated by commas. 
* **Authorization Address:**
* **Authorization Private Key (64-char hex):**

**Critical Architectural Requirement:** The Taker Nexus and Maker Nexus **must strictly share the same private key**. Furthermore, all Maker market-making addresses across different trading pairs, as well as the Taker trading address, **must be** generated from this specific shared private key.

**Launch Nexus.**Once the terminal deployment is complete, open the Nexus client to finalize your setup.Sign a message using the **Authorization Address** you configured during the terminal deployment to securely access the configuration dashboard.

* Step 1: Configure Basic Nexus Information
* Step 2: Configure Taker and Maker Nexus (On-Demand)

#### Advanced Configurations

If your institutional security policies prohibit arbitrary script execution (`curl | bash`), or if you require explicit mapping of Docker environment variables (`APP_ENV`, custom `ZMQ_HOST` endpoints) into existing CI/CD pipelines, you can utilize our Advanced Quick Deployment or Manual Source Deployment methods.

Please request the comprehensive Enterprise Configuration Manifest during your partner onboarding process via <hello@on.nexus>.

***

#### 📚 Concept Guide

<details>

<summary><strong>Trading Wallet</strong></summary>

The specialized hot/warm wallet environment operated internally by the Self-Hosted Nexus Node. Unlike traditional custodial wallets, it serves purely as an execution vault, holding the private keys necessary exclusively for the cryptographic signing of off-chain intents at millisecond latencies.

</details>

<details>

<summary><strong>Nexus Node</strong></summary>

The core software binary hosted by participating institutions. It supports two concurrent operational models: Maker Nexus (configured specifically to run automated market-making algorithms to generate yield) and Taker Nexus (configured for high-frequency algorithmic traders and arbitrageurs to securely generate/sign optimal execution intents off-chain).

</details>