Energy Web Documentation
  • Energy Web Ecosystem
  • Launchpad by Energy Web
  • EWC Validator Documentation
  • Community Ressources
  • Legacy documentation
  • Start here
    • EWC Validator Documentation Overview
  • EWC Governance
    • Governance process
    • Proof-of-Authority Consensus Mechanism
    • EWC Validator Node Operational Functions
    • EWC Validator Roles & Responsibilities
    • Validators eligibility
    • Validators code of conduct
  • Guides
    • Set-up your Validator node in minutes with EW Launchpad
    • Installing a Validator Node
      • Host Machine Requirements
      • Recommended Security Settings
      • Operating System Requirements
      • Validator Node Installation Instructions
    • Maintaining a Validator Node
      • Validator Node Architecture
      • Validator Node Service Commands
      • Updating the Client
      • Changing the Validator Config File
      • Checking node status & logs
      • Migrating a validator node to a new environment
      • How To Transfer EWT from a Validator Node
      • Problems connecting to peers
  • Secure Your Validator Node
    • Changing validator payout address and setting up multi-signature
Powered by GitBook
On this page
Export as PDF
  1. EWC Governance

EWC Validator Node Operational Functions

PreviousProof-of-Authority Consensus MechanismNextEWC Validator Roles & Responsibilities

Last updated 5 months ago

EWC validator nodes can:

  • Establish consensus about the state of the network by verifying the work / behavior of other validator nodes;

  • Reject blocks / transactions that violate input/output protocols defined by AuRa and the EVM state transition function;

  • Implement permissioning functions as described (note: permissoining functions can only be implemented via a majority governance decision).

EWC validator nodes CANNOT:

  • Inspect or approve the contents of individual transactions;

  • Unilaterally verify transactions (any given transaction is only finalized after n/2 blocks, with n=total validators);

  • Associate identities with on-chain accounts;

  • Unilaterally modify account permissions, network topology, or network state.

here