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. Introduction to Spicenet Validation

1.2 Validator Responsibilities in Detail

Let's delve deeper into each of these responsibilities:

  1. Receiving and Verifying Batches of Transactions

    • Your node will continuously receive batches of transactions from the network.

    • You must verify each transaction in these batches to ensure they adhere to Spicenet's protocol rules.

    • This includes checking for correct signatures, sufficient balances, and adherence to any smart contract conditions.

  2. Maintaining Network State

    • As transactions are processed, you'll update your local copy of the network state.

    • This state includes account balances, smart contract states, and other relevant blockchain data.

    • Ensuring your state matches that of other honest validators is crucial for network consensus.

  3. Detecting Fraud

    • You'll need to run checks to identify any suspicious or invalid transactions.

    • This might involve looking for double-spends, invalid state transitions, or other protocol violations.

    • Prompt detection of fraud is vital to prevent any potential damage to the network.

  4. Producing Fraud Proofs

    • If you detect fraudulent activity, you're responsible for creating a fraud-proof.

    • This proof is a cryptographic demonstration of the invalid state transition or transaction.

    • You'll submit this proof to the network, allowing other validators to verify the fraud and take appropriate action.

Previous1.1 Role of Validators in SpicenetNext1.3 Requirements for Effective Validation

Last updated 8 months ago

Was this helpful?