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
  • Code Security
  • Economic Security
  • Oracle Security
  • Protocol Health Security

ETHx Security

PreviousOraclesNextImmunefi Bug Bounty

Last updated 1 year ago

In this section, we will delve into the security and reliability of ETHx for both node operators and end users. For better understanding, we have divided ETHx security into four sections: code security, economic security, protocol health security, and oracle security.

Code Security

  1. Public testnets Stader has launched two public testnets to test out various components of ETHx. Over 10 weeks, around 400 node operators and 600 validators tested different components of the ETHx codebase.

  2. Stader testing Internally, the Stader team has extensively tested the entire tech stack over several months, covering all code flows. Our smart contract test coverage is 99%+ and is being improved actively.

  3. Immunefi bug bounty Stader is launching a $1M bug bounty program with Immunefi to identify critical bugs in the ETHx smart contracts.

Economic Security

  1. Improper validator setup An operator can front-run the first deposit transaction to set a malicious withdraw credential to steal the 28 ETH lent to them. Stader solves this by checking if the validator’s appropriate withdraw credential is set before lending 28 ETH to a node operator. Moreover, if frontrunning is detected, a 3 ETH penalty is imposed on the operator with no loss to staker ETH. Similarly, a node operator can incorrectly sign the first deposit transaction. Like the frontrunning case, Stader ensures that a valid signature is provided before lending 28 ETH, avoiding losses for staker ETH.

  2. Reward loss prevention

  3. Slashing loss protection A validator’s 4 ETH security collateral compensates for any loss of funds due to slashing or other ETH network-imposed penalties. When a validator exits, a node operator only gets any remaining collateral (a portion of the 4 ETH) after accounting for all of staker’s ETH and their rewards.

  4. Node operational risk management An operator can run a validator with ETHx only after pre-recording an exit message that Stader securely stores. Stader broadcasts this pre-signed exit message to stop a validator from reaching dangerous penalty levels, thereby force-exiting a validator.

  5. ETH network degradation risk management A safe mode ensures fair penalty distribution between node operators and stakers under extreme network conditions. A Safe Mode disables withdrawals until the conditions stabilize. Once the network conditions return to normal, the DAO will disable safe mode and re-enable withdrawals. The monitoring manager imposes Safe Mode in two cases: - A percentage of all ETH validators are slashed, leading to unsafe correlation penalty levels. - More than 50% of ETHx validators are facing downtime.

Oracle Security

  1. Consensus mechanisms ETHx Oracles require a strict majority of Oracle operators to function. If a subset of Oracles cannot fulfill duties due to malintent or malfunction, ETHx Oracles would continue functioning as usual. Critical updates like Exchange Rates have built-in guardrails, enabling inspection mode if two subsequent rates deviate significantly.

Protocol Health Security

Stader has implemented a range of health metric alerts to ensure the proper functioning of ETHx. The following alerts are currently active and serve to monitor the system's performance according to its intended design.

  • ETHx circulating supply increase

  • Roles & permissions change on any deployed ETHx contract

  • Lack of Oracle consensus

  • Safe Mode conditions

  • Frontrunning detection

  • Invalid signature detection

  • Exchange Rate Inspection Mode

  • Privileged user address monitoring

  • Unusual reward behavior for validators

Audits ETHx has been audited by three renowned auditors: SigmaPrime, Halborn, and Code4rena. The audit reports are available . With multiple rounds of expert audits, ETHx is one of the most thoroughly audited ETH liquid staking protocols.

Upgradability and pausing Stader’s smart contracts are pausable and upgradable to protect against any bugs identified post-launch. In case of contract upgrades, assumes ownership of all deployed ETHx contracts.

1 ETH penalty for MEV misappropriation - Stader has partnered with to identify MEV misappropriation. Any time an ETHx validator proposes a block with a fee recipient different from Stader’s recommended address, an MEV misappropriation penalty is imposed. DAO penalty for other loss of rewards - The Stader DAO can add penalties for validators in the case of any other deviant behaviors causing significant loss of rewards to stakers.

Collateral backing Each Oracle operator provides security collateral to back their Oracle performance. The list of Oracle operators is . All the accumulated collateral is managed by a 3-on-5 multi-sig operated by reputed ETH ecosystem members.

Dispute mechanism Stader leverages as an MEV misappropriation Oracle partner. A dispute mechanism powered by UMA prevents unfair erroneous reports impacting node operators.

here
the timelock contract
Rated Network
here
Rated Network