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. Running Your Validator Node

4.1 Starting Your Node

To start your Spicenet validator node:

  1. Navigate to your Spicenet directory:

cd /path/to/spicenet
  1. Ensure that a Celestia node is running, as Spicenet uses Celestia for data availability. If you haven't started a Celestia node, you can do so with:

make start

This command starts a Celestia node as a container and creates the necessary configurations for your Spicenet node to connect to it.

  1. Start the Spicenet node:

cargo run
  1. When your node starts running, you'll see output similar to the following:

2023-10-02T15:30:10.123Z INFO  sov_rollup::runner] Starting Spicenet node...
2023-10-02T15:30:10.234Z INFO  sov_rollup::runner] Connecting to DA layer...
2023-10-02T15:30:10.345Z INFO  sov_rollup::runner] Successfully connected to DA layer
2023-10-02T15:30:10.456Z INFO  sov_rollup::runner] Initializing state...
2023-10-02T15:30:10.567Z INFO  sov_rollup::runner] State initialized. Current state root: 0x1a2b3c...
2023-10-02T15:30:10.678Z INFO  sov_rollup::runner] Node is ready to receive and process transaction batches
2023-10-02T15:30:15.789Z INFO  sov_rollup::runner] Received batch of 5 transactions
2023-10-02T15:30:15.890Z INFO  sov_rollup::runner] Processing transactions...
2023-10-02T15:30:16.001Z INFO  sov_rollup::runner] Batch processed. New state root: 0x4d5e6f...
2023-10-02T15:30:16.112Z INFO  sov_rollup::runner] Waiting for next batch...

This output indicates that:

  • Your Spicenet node has started successfully

  • It has connected to the Celestia Data Availability (DA) layer

  • The initial Spicenet state has been set up

  • The node is processing incoming transaction batches received from Celestia

  • After processing each batch, a new Spicenet state root is calculated

  1. Your Spicenet node will continue to run, receiving transaction batches from Celestia and processing them. The output will show ongoing activity, including:

  • Receipt of new transaction batches from Celestia

  • Processing of these batches on Spicenet

  • Updates to the Spicenet state root after each batch is processed

  • Any potential errors or warnings that might occur during the operation

Keep this terminal window open to maintain your Spicenet node's operation. You can open new terminal windows for interacting with your node or performing other tasks.

Previous3.5 Docker ConfigurationNext4.2 Monitoring Your Node

Last updated 8 months ago

Was this helpful?