Slashing Protection
The following are the primary controls Ebunker uses to mitigate slashing risk:
Validator Key Management
- Strict permission isolation across the entire lifecycle of key generation, storage, and use
- The same validator key is never deployed across different environments
- Complete isolation between production and test environments
Slashing Protection Mechanism
- A slashing protection database records the full history of proposals and attestations
- Mandatory validation on migration or restart to prevent loss of historical state
- Guarantees that no double vote or double propose can occur in any failover scenario
Migration and Operations Process
- Validator migration follows a standard SOP with an approval workflow
- All migration operations are single-point controlled to avoid parallel execution
- A new instance is only allowed to start after the old instance is fully decommissioned
DVT Architecture
- Distributed Validator Technology (DVT) reduces single-point-of-failure risk
- Mitigates the risk of duplicate signing caused by single-node anomalies
- Improves overall fault tolerance and stability
Runtime Security Controls
- Continuous monitoring of validator status and signing behavior
- Alerts on anomalous behavior (e.g. duplicate proposal risk)
- Conservative failover strategy to avoid risk amplification from rapid switching