RPC Node
Access the Neutron network, run applications, or provide RPC services to others
Validator Node
Participate in consensus, earn rewards, and help secure the Neutron network
This guide covers the basic node setup that serves both purposes. If you want to become a validator, refer to our becoming a validator section.
System Requirements
CPU
Minimum: 4 or more cores
Recommended: 8 or more cores
Recommended: 8 or more cores
RAM
Minimum: 16GB
Recommended: 32GB or more
Recommended: 32GB or more
Storage
Minimum: 500GB SSD
Recommended: 1TB or more NVMe SSD
Recommended: 1TB or more NVMe SSD
Network
Minimum: 100Mbps
Recommended: 1Gbps or more with low latency
Recommended: 1Gbps or more with low latency
Installation Process
1
Install Dependencies
2
Install Go
3
Build or Download Neutron
- Build from Source
- Download Binary
4
Initialize the Node
Configuration
Download Genesis and Address Book
RPC and API Endpoints
For connecting to the Neutron network, you can use the following official endpoints:Official Neutron RPC
RPC: https://rpc-lb.neutron.org
Load-balanced RPC endpoint maintained by Neutron
Load-balanced RPC endpoint maintained by Neutron
Official Neutron REST APIs
Solara: https://rest-solara.neutron-1.neutron.org
Vertexa: https://rest-vertexa.neutron-1.neutron.org
High-availability REST API endpoints
Vertexa: https://rest-vertexa.neutron-1.neutron.org
High-availability REST API endpoints
For a comprehensive list of community-maintained endpoints, visit Cosmos Directory which provides real-time status and performance metrics for various RPC and API providers.
Configure Your Node
Edit app.toml to set minimum gas prices:For a complete list of available seeds and peers, check the Peers page.
State Sync or Snapshot (Optional)
To speed up the initial sync process, you can use state sync or a snapshot.- State Sync
- Snapshot
Set Up SystemD Service
Create a systemd service file for Neutron:Monitor Node Status
- Check Logs
- Check Sync Status
- Check Peers
Performance Monitoring
Set up comprehensive monitoring to ensure your validator meets performance requirements:Essential Monitoring Stack
Metrics Collection
Prometheus: Collect system and validator metrics
Node Exporter: System resource monitoring
Cosmos Exporter: Neutron-specific metrics
Node Exporter: System resource monitoring
Cosmos Exporter: Neutron-specific metrics
Visualization & Alerts
Grafana: Create dashboards for metrics visualization
Alertmanager: Configure alerts for critical issues
TenderDuty: Validator-specific monitoring tool
Alertmanager: Configure alerts for critical issues
TenderDuty: Validator-specific monitoring tool
Key Metrics to Monitor
Configure alerts for these critical metrics:- Block Signing: Track missed blocks and signing percentage
- Oracle Performance: Monitor oracle price update success rate
- System Resources: CPU, memory, disk usage, and network connectivity
- Node Health: Sync status, peer count, and consensus participation
Alert Configuration
Set up alerts for:- Critical Alerts
- Warning Alerts
- Validator jailed or tombstoned
- Node not signing blocks (greater than 5 missed blocks)
- Node falling behind sync (greater than 10 blocks)
- Oracle service failures
Security Recommendations
Firewall Configuration
Firewall Configuration
Configure your firewall to only allow necessary ports:
SSH Hardening
SSH Hardening
Improve SSH security with these steps:Make these changes:Restart SSH:
Sentry Node Architecture
Sentry Node Architecture
For production validators, consider implementing a sentry node architecture:
- Set up separate sentry nodes that connect to the public network
- Configure your validator to only connect to your sentry nodes
- This protects your validator from DDoS attacks
Internet <-> Sentry Nodes <-> Private Network <-> Validator
Key Management
Key Management
Secure your validator keys:
- Store validator keys on hardware security modules (HSM) when possible
- Use separate signing keys and never expose private keys
- Implement proper backup and recovery procedures
- Consider multi-signature setups for additional security
Best Practices
Infrastructure Redundancy
Implement redundant systems, backup power, and multiple network providers to avoid single points of failure.
Upgrade Preparation
Maintain testing infrastructure and participate in testnet upgrades to ensure smooth mainnet transitions.
Performance Optimization
Regularly monitor and optimize system performance to maintain greater than 99.5% uptime and greater than 98% oracle success rates.
Documentation
Maintain detailed operational procedures, incident response plans, and recovery documentation.
Next Steps
Choose your path based on your intended use:RPC Node Operation
You’re Ready! Your node can now serve RPC requests, sync with the network, and support applications. Consider configuring:
- API endpoints for application access
- Monitoring for node health
- Backup and recovery procedures
Validator Path
To become a validator, continue with these additional steps:
- Set up the Slinky Oracle Service
- Review validator requirements
- Complete validator registration
Additional Configuration for RPC Nodes
If you’re running an RPC node for public or application use, consider these additional configurations:Only enable external access if you understand the security implications and have proper firewall rules in place.