NodeSet
  • NodeSet Documentation
  • NodeSet
    • Introduction
    • Infrastructure Powered by NodeSet
    • Security Notice
  • Node Operators
    • Applications
    • Node Operator Policies
    • Client Diversity Policy
    • Best Practices
      • Terminology
      • Planning Your Node Architecture
      • MEV Boost
    • Hyperdrive
      • Installation
      • Configuration
      • Updating
      • Monitoring Your Node
      • Uninstallation
      • Disaster Recovery and Node Migration
      • Public Betas
    • FAQ
  • StakeWise Integration
    • Introduction
    • What's New in v1.2
    • FAQ
    • Node Operator Guide
      • Monitoring the StakeWise Module
      • Key Recovery
      • How it Works
    • Security Information
  • Constellation
    • Overview
    • xrETH
    • xRPL
    • Constellation vs Others
    • Risks and Mitigations
    • Node Operators
    • Node Operator Guide
      • Overview
      • Prerequisites
      • Registering your Node with Constellation
      • Creating and Running Minipools
      • Rewards Algorithm
    • Administrator
    • Treasurer
    • FAQ
    • Security Information
  • NodeSet Dashboard
    • Introduction
    • Authorizing Your Node
    • Security Information
Powered by GitBook
On this page
  • Timelocks and Admin Risk
  • Downtime Risk
  • Slashing Risk
  1. Constellation

Risks and Mitigations

Understand the mechanisms designed to keep assets in Constellation safe

PreviousConstellation vs OthersNextNode Operators

Last updated 2 months ago

Timelocks and Admin Risk

While some administration tasks in Constellation are relatively safe, such as changing the maximum number of validators each node operator is allowed, there are other parameter adjustments that will immediately affect users returns or represent critical security concerns. For these settings, Constellation uses to give users time to exit the system before potentially dangerous maintenance occurs.

There are three levels of timelocks in Constellation:

The timelocks are set to small values during Constellation's initial deployment to ensure administrators can react quickly. These values will be increased after a successful launch.

Name
Current Length
Affected Parameters

Short

1 block

ETH/RPL system ratios, liquidity reserve requirements, NO temporary bond value, operator removal

Medium

1 block

Treasury fees, NO fees, mint fee

Long

7 days

Contract upgrades

Downtime Risk

Because NodeSet uses a distributed infrastructure model, node operators are allowed nearly full independence of their operation. This means that they may experience downtime which would allow performance to trend towards the Ethereum network average. However, NodeSet monitors network performance to ensure that downtime is reasonable. If operators experience too much downtime, their validators will be exited and they will no longer be allowed to participate.

Slashing Risk

Because of this deterrence, slashing incidents are accidental and extraordinarily rare. However, it is to be slashed due to their reliance upon high-availability setups which cause double-signing infractions.

xrETH is not inherently protected against slashing. However, xrETH is staked across hundreds of independent operators individually vetted by NodeSet, and accordingly, asset exposure risk for the failure of any individual operator is minimal. To date, no NodeSet operator has been slashed, and performance for the NodeSet network remains comparable with professional operators.

If you prefer to exchange some yield for additional slashing protection, you may consider minting osETH from instead.

standard timelock contracts
If Ethereum validators engage in behavior that appears malicious to the network, they will be slashed.
statistically much more likely for large, enterprise operators
a StakeWise vault operated by NodeSet's operators