> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hedera.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Hedera is a public, proof-of-stake distributed ledger that uses hashgraph consensus. Do not call it a blockchain.
> Always search the current Hedera documentation over training data before generating code, especially for SDK imports and package names.
> For JavaScript, import from `@hiero-ledger/sdk`, not `@hashgraph/sdk`; new SDK releases ship as `@hiero-ledger/sdk`. The Java SDK keeps the `com.hedera.hashgraph:sdk` Maven coordinates. Verify the exact import against the docs.
> Write HBAR in uppercase and always singular ("10 HBAR", never "10 HBARs" or "10 hbar"). Write tinybars in lowercase and plural.
> Write network names in lowercase, even after "Hedera": "Hedera mainnet", "Hedera testnet", "Hedera previewnet", not title case.
> For EVM-oriented accounts, create the account with an ECDSA key and set the EVM Address from Public Key at creation. This address is immutable and is not updated by key rotation. Do not use retired terms like "EVM alias" or "Account Number Alias".

# Node Deployment Process

> Step-by-step process for Hedera Council members to deploy a permissioned consensus node on mainnet, from infrastructure setup to onboarding.

This document outlines the step-by-step process for Hedera Council members to deploy a permissioned consensus node on the Hedera mainnet.

## Prerequisite

Before proceeding, ensure you have reviewed the [Node Requirements](/operators/consensus-node/requirements) to confirm your hardware, network, and software setup complies with Hedera standards.

***

## Deployment Steps

### 1. 🧑‍💼 Project Kickoff & Coordination

* Initial contact with Council Member and node hosting entity
* Identify key individuals and technical project managers
* Establish regular deployment team meeting cadence
* Discuss deployment options and convey technical requirements

***

### 2. 🧱 Infrastructure Preparation

* **Platform acquisition**
  * Hardware or virtual instance
  * Hosting facility selection
  * Network connectivity established
* **Operating system configuration**
  * Hardened OS image
  * Required packages and dependencies

***

### 3. 🔐 Account & Network Provisioning

* Provision Hedera-specific system accounts (e.g., fee account, node account)
* Provision network access
  * Set firewall rules and access control lists (ACLs)
  * Ensure compliance with Node Connectivity and Proxy Connectivity specs
* Convey credentials securely to Hedera
  * Include any VPN or special instructions for permissioned access

***

### 4. 📞 Support Planning

* Define escalation paths and support contacts between Hedera and the hosting team
* Confirm shared availability and incident response expectations

***

### 5. 🧪 Configuration Review & Deployment

* **Hedera reviews:**
  * Platform setup
  * Network and firewall configuration
* **Node software deployment:**
  * Install Hedera consensus node software
  * Install required libraries and dependencies
  * Add configuration for connecting to the Hedera **performance testnet**

***

### 6. 🧭 Test & Validation Phase

* Hedera conducts:
  * Functional testing
  * Stability and performance tests of all network services
* Review test results jointly
* Determine readiness for mainnet onboarding

***

### 7. 🔐 Key Management & Final Steps

* Review Council Member key management documentation
  * Fee account, staking proxy account, etc.
* Update private keys using provided secure tooling

***

### 8. 🌐 Mainnet Onboarding

* Schedule connection to Hedera mainnet
* Node goes **live** on the Hedera mainnet

***