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

Was this helpful?

  1. Maintenance and Upgrades

8.2 Upgrading Your Node

When a new version of Spicenet is released:

  1. Check the release notes for any breaking changes

  2. Stop your node

  3. Backup your data

  4. Update the Spicenet software:

git pull
cargo build --release

  1. Restart your node

Always test upgrades on a testnet before applying them to your mainnet validator.

Previous8.1 Routine MaintenanceNext9.1 Common Issues and Solutions

Last updated 7 months ago

Was this helpful?