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

#### Deployment Fast-Lane

The following process outlines the safest and fastest way to bootstrap a standalone Nexus Node connected to the L1 Bitcoin Network and Nexus Composer.

{% stepper %}
{% step %}
Step 1: Infrastructure Provisioning

Deploy a secure environment for the Nexus Node binary. Recommended minimum specifications:

* 8 Core CPU
* 32GB RAM
* High-IOPS SSD (crucial for UTXO tracking and mempool synchronization).
  {% endstep %}

{% step %}
Step 2: One-Command Installation

For first-time deployments and fast bootstrapping, execute the official installation script directly on your target server. This script fetches the necessary Docker topologies and environment scaffolds:

```shell
curl -fsSL https://on.nexus/install.sh | bash
```

{% hint style="info" %}
For production environments, institutional operators are encouraged to review the script payload prior to execution.
{% endhint %}
{% endstep %}

{% step %}
Step 3: Wallet Initialization

During initialization, you must configure the operational wallets required by the Nexus Coordination Network. These variables will be injected into your `.env` configuration:

* `POOLS_BTC_TOKEN`: Assign specific UTXO subsets to power your passive Yield/Maker curves (e.g., FPSSL or CPMM).
* `TAKERS_BTC_TOKEN`: Assign separate, highly-liquid UTXO subsets to power your high-frequency Arbitrage routines.
* `DOTSWAP_ACCOUNT_PRIVATE_KEY_HEX`: The cryptographic credential proving node ownership to the Nexus Composer.

*Note: In an Independent Nexus Node setup, these Trading Wallet keys sit in a hot/warm environment to enable millisecond response times. For enterprise cold-storage controls, refer to* [*Institutional MPC Integration*](/deployment-and-integration/institutional-mpc.md)*.*
{% endstep %}

{% step %}
Step 4: Security Hardening (Critical)

Last but not least. Once your Nexus node is running stably and actively communicating with the Composer, you must perform the following critical security mitigation:

* Remove SSH Access: Return to your cloud firewall settings and disable rule 22 (SSH).
* Switch to Secure Tunnels: You should no longer connect via public SSH. Instead, rely exclusively on secure, in-browser identity management tools provided by your cloud host (e.g., AWS Session Manager, Linode Lish Console).
  {% endstep %}
  {% endstepper %}

#### 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>


---

# Agent Instructions: 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:

```
GET https://docs.on.nexus/deployment-and-integration/node-setup.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.