🌅
Sunrise / Gluon Docs
  • Home
    • 👋Sunrise
  • 📜Learn
    • 🌆Sunrise
      • Proof of Liquidity
      • Data Availability
      • Liquidity Pool
      • Swap
      • Liquidity Incentive
        • Gauges Voting
        • Bribes
      • TokenConverter
      • Fee
      • Lockup Account
      • Non-Voting Delegation
    • 💴$RISE
      • Allocations
    • 🏦Gluon
    • 💴$GLU
    • 🎓Thesis
      • App chain thesis
      • Interoperability
  • 🛠️Build
    • Client
    • L2 Blockchains
      • Rollkit
        • Sunrise Data
        • Rollkit L2 Chain
      • OP Stack
        • Sunrise Data
        • OP Stack L2 Chain
    • Validators
      • Proof of Data Availability
  • 🏗️Run a Sunrise Node
    • Networks
    • Types of Nodes
      • Consensus
        • Full Consensus Node
        • Validator Node (Genesis)
        • Validator Node
        • Setup Cosmovisor
      • IBC Relayers
    • Resources
      • Upgrade
      • Environment
  • 🏗️Run a Gluon Node
    • Networks
    • Node
      • Validator Node
  • 🔗Links
    • GitHub
    • Discord
    • X (Twitter)
    • Medium
Powered by GitBook
On this page
  1. Build

Validators

PreviousOP Stack L2 ChainNextProof of Data Availability

Last updated 3 months ago

  • Self Delegation

First, create a validator node. After the validator node is started, blocks are validated and generated.

In Sunrise, validators are responsible for validating data in the Data Availability Layer in addition to generating blocks. sunrise-data includes code to automate this process, allowing validators to perform the validation work.

Therefore, the validator node must run the following 3 daemons

  1. sunrised (Recommended to work with cosmovisor)

  2. sunrise-data validator

  3. IPFS Daemon

🛠️
Validator Node
Data Availability Proof