Node Requirements
The Hedera Mainnet is currently comprised of permissioned consensus nodes operated by the Hedera Governing Council
Last updated
Was this helpful?
The Hedera Mainnet is currently comprised of permissioned consensus nodes operated by the Hedera Governing Council
Last updated
Was this helpful?
The following is provided to help members deploy their permissioned mainnet consensus node. Please note, this information is not intended to apply to Hedera's transition to a permissionless network.
Please note: this information does not apply to Hedera's transition to a permissionless network. Hedera Governing Council The following is provided to assist:
Currently, the Hedera Mainnet will perform at a rate determined by the lowest-performing node. To ensure a common level of performance minimum hardware, connectivity, and hosting requirements have been defined for the initial permissioned, Governing Council nodes.
To ensure accurate conformity with the minimum requirements, please provide node hardware, connectivity, and hosting details to Hedera prior to purchase (devops@hashgraph.com).
X86/X64 compatible (Intel Xeon or AMD EPYC); 24 cores/48 threads meeting or exceeding the following benchmarks:
Geekbench 6 single-core score
Minimum: 1000 or greater
Recommended: 1500 or greater
Passmark single thread rating:
Minimum to remain on Mainnet: 2300 or greater
Recommended: 2800 or greater
Sustained 1Gb/s internet bandwidth via a single 1-Gigabit / 10-Gigabit Ethernet interface
256 GB PC4-21300 2666MHz DDR4 ECC Registered DIMM or faster (minimum), 320GB or higher PC4-25600 3200MHz (recommended)
It is recommended to mount 240 GB SSD with Raid 1 as a root volume /
and then provide usable storage via different devices later mounted during installation. This may not be possible on your hardware, so alternatively all required storage may be allocated to the root volume.
Note: nodes must pass the Hedera performance test suite performed at installation time.
Linux
Minimum kernel mainline versions (not distribution version)
6.2.0
6.1.2
6.0.16
5.15.86
Actively Supported Long-Term-Support (LTS) 64-bit Linux Distributions
Ubuntu LTS 22.04
Red Hat Enterprise Linux (RHEL) 8 and 9
Oracle Linux 8 and 9
User Specification
Name: hedera
Unix UID: 2000
Group Membership
Primary: hedera
Secondary: admin
or wheel
(depending on Linux distribution)
Permissions:
Read, Write, and Execute Access to the entire /opt/hgcapp
folder tree
Group Specification
Name: hedera
Unix GID: 2000
Access to the node via public APIs must be mediated by an in-line proxy. Below are the specifications for establishing this proxy.
2- core-x86/x64 CPU
4GB RAM
100GB SSD storage
200Mb/s sustained internet network connectivity with public static IP address
Supported Docker (Hedera to provide Docker image with HAProxy)
Industry-standard hosting requirements for security and availability
Tier 1 Data Center Hosting facility
SSAE 16 /18, SOC 2 Type 2 compliant
Hedera will seek to avoid duplicating hosting providers across Council members
The following steps outline the process for Council Members to add their consensus node to the mainnet.
Initial contact with Council Member and node hosting entity
Identify key individuals and project managers
Establish regular deployment team meeting cadence
Conveyance of technical requirements and discussion of deployment options
Node platform acquisition
Hardware or virtual instance
Network connectivity
Hosting facility
Configuration of the operating system on platform
Provisioning of accounts as specified
Provisioning of network access (firewall rules/access control lists)
Conveyance of credentials to Hedera
Includes any special instructions for permissioned access such as VPNs
Discussion of support and escalation paths between organizations
Hedera undertakes configuration review
Platform
Connectivity
Deployment of Hedera consensus node software and required supporting libraries
Add connection configuration for a Hedera performance testnet
Hedera executes functional, stability and performance tests for all network services
Review of test results and determination of preparedness for mainnet connectivity
Review key management documentation related to Council Member's accounts including: fee account, proxy staking account, et al.
Update private keys using provided tools
Schedule mainnet connection
Mainnet live