Nethermind Docs
Github RepositoryHome Page
Search…
English
Welcome to Nethermind
Contact
Social Media
Contact us
First steps with Nethermind
Getting Started
Migrating From Geth
Running Nethermind Post Merge
Supported platforms
Firewall Configuration
Hardware Requirements
Security
Manage Nethermind with systemd
Nodes and The Merge
The Merge
Nethermind Changes
Installing Nethermind
Downloading Releases
Building From Source
Docker
Ethereum client
Running Nethermind
Sync modes
JSON RPC
Using Docker
Networks
Private Networks
Database
Metrics
Logging Configuration
Configuration
Plugins
Monitoring Node's Health
MEV
MEV Plugin
Nethermind utilities
CLI
Guides and Helpers
FAQ
Upgrades
Custom Analytic Tools
Deploy Nethermind with Monitoring stack
Known Issues
Web3.py
Validator setup
ETH2 <-> Nethermind
Coding Style
Powered By GitBook
Security
Security measures that should be taken before running Nethermind Node on Ethereum Mainnet
​
📢
 DO NOT use Nethermind wallet / signers for mainnet ETH handling!
​
📢
 JSON RPC endpoint (port 8545) should NOT be exposed publicly (should be behind the firewall).
​
📢
The private key from which the node ID is derived is stored on disk (NOT protected by password).
Nethermind is thoroughly tested but the more popular it will get the more likely it will be the target of client-specific attacks. Generally you should always consider running backup client nodes implemented by a different team for any critical operations.
For non-mainnet signing you can use dev wallet configurations.
First steps with Nethermind - Previous
Hardware Requirements
Next - First steps with Nethermind
Manage Nethermind with systemd
Last modified 2yr ago
Copy link