Spicenet Validator Docs
  • Welcome to Spicenet Validator Documentation
  • Introduction to Spicenet Validation
    • 1.1 Role of Validators in Spicenet
    • 1.2 Validator Responsibilities in Detail
    • 1.3 Requirements for Effective Validation
  • Set Up Your Validator Node
    • 2.1 Validator Requirements
    • 2.2 Setting Up Your Environment
    • 2.3 Installing Spicenet
  • Configuring Your Validator Node
    • 3.1 Basic Configuration
    • 3.2 Advanced Configuration
    • 3.3 Security Best Practices
    • 3.4 Binaries Configuration
    • 3.5 Docker Configuration
  • Running Your Validator Node
    • 4.1 Starting Your Node
    • 4.2 Monitoring Your Node
    • 4.3 Performing Sanity Checks
  • Working with Transactions
    • 5.1 Understanding Transaction Structure
    • 5.2 Generating Transactions
    • 5.3 Submitting Transactions
    • 5.4 Verifying Transactions
  • Interacting with Your Node
    • 6.1 Using REST API
    • 6.2 Using sov-cli
  • Validator Economics
    • 7.1 Rewards and Incentives
    • 7.2 Slashing Conditions
  • Maintenance and Upgrades
    • 8.1 Routine Maintenance
    • 8.2 Upgrading Your Node
  • Troubleshooting
    • 9.1 Common Issues and Solutions
      • 1. Node Won't Start
        • Celestia Node Not Running
        • Outdated Spicenet Version
        • Incorrect Configuration
      • 2. Transactions Not Being Processed
        • Node Not Synced:
        • Low Peer Count
        • Insufficient Gas
      • Poor Performance
        • Insufficient Hardware Resources
        • Network Issues
        • Suboptimal Spicenet Configuration:
    • 9.2 Advanced Debugging Techniques
    • 9.3 Seeking Help
  • Community and Support
    • 10.1 Frequently Asked Questions
    • 10.2 Community Support
Powered by GitBook
On this page
  • Key Management
  • Node Security
  • Network Security

Was this helpful?

  1. Configuring Your Validator Node

3.3 Security Best Practices

Key Management

  1. Generate a new key pair for your validator:

./target/debug/sov-cli keys generate

  1. Securely store your private key. Never share it or store it in plain text on your server.

  2. Use hardware security modules (HSMs) for additional security if available.

Node Security

  1. Keep your operating system and all software up to date.

  2. Use a firewall to restrict incoming connections:

    sudo ufw allow 12346/tcp
sudo ufw enable

  3. Disable root SSH access and use key-based authentication.

Network Security

  1. Use a VPN or private network for communication between your nodes if running multiple.

  2. Implement DDoS protection if your node is publicly accessible.

  3. Regularly monitor your node for unusual activity or performance issues.

Previous3.2 Advanced ConfigurationNext3.4 Binaries Configuration

Last updated 8 months ago

Was this helpful?