Cascadia
  • Welcome to Cascadia
    • Brand Guidelines
    • Official Links
  • Artificial Intelligence
    • Incentives
  • Developers
    • Addresses
    • CosmWasm
      • Smart Contracts
      • Install Requirements
      • Set your Environment
      • Optimization
      • Deployment
      • Multi-Chain Contracts
        • The Actor Model
      • CW1 Subkeys Contract
        • Guide
      • CW20 Base Contract
        • Guide
      • C721 Base Contract
        • Guide
      • Upload Contract
        • Create a WASM File
      • Sign and Verify
        • Guide
    • Solidity
      • Deployment
      • Verification
        • Block Explorer
        • Hardhat
  • Directory
    • Address
    • API
    • Applications
    • Explorer
    • Faucet
    • Genesis
    • Governance
    • GRPC
    • Guide
    • Peers
    • RPC
    • Snapshot
    • State Sync
    • Website
    • Websocket
  • Governance
    • Align
      • Cooldown Period
      • Functions
    • Off-Chain
    • On-Chain
      • Voting
    • Proposals
      • On-Chain Voting via CLI
      • Proposal (Example)
    • VeTokenomics
      • Model
      • Voting Power Calculation
    • Analytics
  • Network
    • ChainID & Address Prefix
    • Configuration
    • Consensus
    • Denomination
    • Distribution
      • Block Rewards
      • Gas Fees
    • ESG
    • Faucet
    • Modules
    • Parameters
    • Peers
  • Security
    • Disclosure Policy
    • Multisignature
  • Staking
    • Claim
    • Delegate
    • Manual
    • Redelegate
    • Undelegate
  • Use Cases
    • Business Development and Marketing
    • Consumer Relationship Management
  • Node
    • Cloud Platforms
      • Amazon Web Services
      • Google Cloud Platform
    • Snapshot
    • State-Sync
    • Upgrade
      • Automated
      • Manual
  • Validators
    • System Requirements
    • Installation
    • Reference
      • Customization
  • Community
    • Discord
    • Telegram
    • Twitter
  • Legal
    • Privacy Policy
    • Terms & Conditions
Powered by GitBook
On this page
Edit on GitHub

Validators

Nodes are computers running the Cascadia software that contribute to the network by relaying information. Each node needs to stake at least 1 CC to become a Validator. Validators play a role in the consensus mechanism by adding new blocks and disseminating encrypted/authenticated votes using the unique key of each validator. Validators and their delegators receive tokens from transaction fees and CC as block rewards.

Validators also collect fees collected from the deployed ve-contract using functions in the bank module of Cosmos SDK to receive a portion of these fees. An additional share of validator rewards and gas fees go to CC lockers and nProtocols, which will be adjustable via governance.

Being a validator requires more than adhering to instructions. It presents a challenging yet rewarding opportunity to explore decentralization. It's vital to have a firm understanding of network administration and the ability to resolve technical issues that may arise.

Basic Principles to Become a Validator

  1. Validators must run the most up-to-date version of Cascadia software.

  2. Validators must ensure their servers are accessible and private keys are secure.

  3. Validators must actively participate in governance.

  4. Validators are expected to be active within the community and be aware of Cascadia's state to quickly adapt to any changes.

PreviousManualNextSystem Requirements

Last updated 1 year ago