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 Doppelganger protect?
  • How it works?
  • Doppelganger protection is optional. You can choose Yes or No based on your preference
  1. Node Operator
  2. Permissionless node operator
  3. Node registration and adding validators
  4. Step 4: Configure Stader services

Step 4.7 Enable Doppelganger protection

PreviousStep 4.6 Add checkpoint URLNextStep 4.8 Add fallback clients

Last updated 1 year ago

What is Doppelganger protect?

In Ethereum proof-of-stake (PoS), validators can face slashing if multiple validators operate with the same identity. Doppelganger Protection serves as a safeguard, preventing validators from being slashed and removed from the Beacon Chain in the event that a node operator unintentionally runs their validator keys on multiple machines simultaneously.

How it works?

Whenever a validator client is restarted, Doppelganger protection intentionally skips 2-3 attestations. It actively monitors the network during this process to ensure that attestations are not being transmitted using your validator keys. Ideally, there should be no attestations, indicating that no other machine is utilizing your validator keys.

After the brief waiting period, the validator client will resume its regular validation operations. However, if it detects another machine using your validator keys, it will immediately terminate and generate an error message in its log files.

In most cases, doppelganger detection results in only a few missed attestations after restarting the client. However, when you're transferring your validator to a new machine or switching to a different Beacon client, doppelganger detection becomes essential to prevent accidental double attesting and potential slashing.

Doppelganger protection is optional. You can choose Yes or No based on your preference

Learn more