Stader - ETHx
  • Introduction
    • Explore ETHx
    • ETHx Tech blogs
    • ETHx Governance
  • Launch Incentives
    • ETHx Stakers
    • ETHx Node Operators
      • ETHx Boosted Commission
      • 13000 $SD top-up pool
      • $65000 Reward pool for AVADO user
  • ETHx Staking
    • Guides
    • FAQs
  • Node Operator
    • Staking on Ethereum
      • What is Ethereum staking?
      • ETH staking rewards and penalties
      • Solo-staking vs ETHx
    • Permissionless node operator
      • Responsibilities of a node operator
      • Pre-requisite
      • Node registration and adding validators
        • Step 1: Hardware and platform
          • DIY kit
          • Cloud services
          • VPS services
          • AVADO
          • Allnodes
        • Step 2: Download Stader node
        • Step 3: Install Stader node
        • Step 4: Configure Stader services
          • Step 4.1 Network selection
          • Step 4.2 ETH client configuration
          • Step 4.3 ETH1 - Execution client selection
          • Step 4.4 ETH2 - Consensus client selection
          • Step 4.5 Add a graffiti
          • Step 4.6 Add checkpoint URL
          • Step 4.7 Enable Doppelganger protection
          • Step 4.8 Add fallback clients
          • Step 4.9 Enable monitoring
          • Step 4.10 MEV Boost
          • Confirmation and configuration settings
        • Step 5: Execution and Consensus client sync
        • Step 6: Wallet setup
        • Step 7: Register your node on the Stader network
        • Step 8: Deposit SD collateral
        • Step 9: Deposit ETH bond
        • Validator States
      • ETHx rewards for permissionless node operators
        • Socializing Pool
        • SD rewards
        • Claim CL rewards
        • Claim EL and SD rewards
      • Node Monitoring
      • Node Migration
      • Validator exits and node termination
      • Latest update
      • CLI Command sheet
    • Permissioned node operator
      • Pre-requisite for permissioned node operators
      • Web3Signer setup guide
      • Node registration and adding validators
        • Step 1: Download Stader node
        • Step 2: Install Stader node
        • Step 3: Configure and start Stader services
        • Step 4: Wallet setup
        • Step 5: Set the fee recipient of your validator client to Stader socializing pool
        • Step 6: Check Docker and node status
        • Step 7: Operator address whitelisting
        • Step 8: Register you node on the Stader network
        • Step 9: Add validators to your node
        • Step 10: Check your node and validator status
      • ETHx rewards for permissioned node operators
        • Claim CL rewards
        • Claim EL rewards
      • Node Migration
      • Latest update
    • FAQs
  • Smart Contracts
  • Oracles
  • ETHx Security
    • Immunefi Bug Bounty
    • Audit Reports
    • Public Repositories
  • ETHx Integration
  • Connect with us
Powered by GitBook
On this page
  • What is an consensus client?
  • If you have chosen the "Locally Managed" option during the ETH client configuration step, you can now select a Consensus client from the provided options.
  • If you have chosen the "Externall Managed" option during the ETH client configuration step, you can now select a Consensus client from the provided options.
  1. Node Operator
  2. Permissionless node operator
  3. Node registration and adding validators
  4. Step 4: Configure Stader services

Step 4.4 ETH2 - Consensus client selection

PreviousStep 4.3 ETH1 - Execution client selectionNextStep 4.5 Add a graffiti

Last updated 1 year ago

What is an consensus client?

A consensus client plays a pivotal role within the Ethereum network, facilitating the establishment and maintenance of consensus among network participants. This client is responsible for validating and verifying transactions, ensuring agreement on the state of the blockchain across the entire network. Commonly known as the Beacon Node, CL client, or formerly the Eth2 client, the consensus client implements the consensus algorithm. This algorithm enables the network to reach consensus by leveraging validated data from the execution client. Consensus clients with other network nodes to propagate and validate transactions, thereby bolstering the security and integrity of the Ethereum blockchain. Through active participation in the consensus process, these clients enable decentralized decision-making and enhance the overall trustworthiness of the Ethereum network.

If you have chosen the "Locally Managed" option during the ETH client configuration step, you can now select a Consensus client from the provided options.

  • System-recommended: Let Stader node arbitrarily choose from a wide range of network clients . This will enhance the network diversity and resilience of the Ethereum ecosystem.

If you have chosen the "Externall Managed" option during the ETH client configuration step, you can now select a Consensus client from the provided options.

Since each consensus client has its own unique behavior, Stader Node must be informed of the specific client you are using externally. This way, it can adjust its behavior accordingly. Select the consensus client that you are managing externally. If your preferred client is not listed here, it may not be compatible with the Hybrid mode of Stader node.

After choosing the externally managed Consensus client, input the appropriate HTTP URL or JSON RPC URL according to your client selection. Keep in mind that if you are running this client on the same machine as the Stader Node, utilize your machine's LAN IP address instead of using "localhost" or "127.0.0.1".

Lighthouse: Lighthouse is a software client for the Ethereum 2.0 blockchain that is developed by Sigma Prime, a blockchain engineering firm based in Australia. It is written in the Rust programming language and is designed to be fast, efficient, and secure.

Nimbus: Nimbus is an Ethereum consensus client that prioritizes minimal resource usage, and is written in Nim - a language with Python-like syntax that compiles to C. Its efficiency enables it to perform well on any system.

Prysm: Prysm, an Ethereum proof-of-stake client written in Go, is developed by Prysmatic Labs. It prioritizes usability, security and reliability in the implementation of its consensus protocol.

Teku: Teku is an Ethereum consensus client developed by PegaSys, a branch of ConsenSys that focuses on building high-quality clients for Ethereum. Written in Java, Teku offers impressive security and scalability features, although it requires substantial RAM and CPU resources to operate efficiently.

Learn more
Learn more
Learn more
Learn more
proof-of-stake
synchronize
Learn more