🦆
D.U.C.K. - Knowledge Base
  • D.U.C.K. Knowledge Base
    • 🦆Introduction
    • 🤝Contributors
    • 🎯Journey ahead
    • ℹ️Structure Overview
  • Risk Framework
    • ℹ️Risk Framework
    • Risks
      • Slashing (SLS)
      • Downtime (DOW)
      • Key Compromises (KEC)
      • General Infrastructure (GIR)
      • Service Partner Specifics (SPS)
      • Reputation (RER)
    • Risk Management Procedures
    • Risk Assessment Procedures
    • Review & Audit Procedures
    • Templates
      • Risk Register
      • Incident Response Plan
  • Mitigation & Controls Library
    • ℹ️Mitigation & Controls Library
    • Mitigation Strategies
    • Controls Catalog & Best Practices
    • Implementation Guidelines
    • Collection of Tools, Scripts & Templates
  • Communications Toolkit
    • ℹ️Communication Toolkit
    • Stakeholder Strategy
      • Stakeholder Overview
      • Ecosystem Touchpoints
      • Stakeholder Management
    • Incident Communication Protocols
    • Templates & Toolkits
      • Stakeholder Map
      • Stakeholder Register
      • Post-Mortem Analysis
      • Tools
    • Ecosystem Blueprint
      • Large Node Operator
Powered by GitBook
On this page

Was this helpful?

Edit on GitHub
  1. Risk Framework
  2. Risks

Service Partner Specifics (SPS)

Risk related to running specific services.

PreviousGeneral Infrastructure (GIR)NextReputation (RER)

Last updated 1 year ago

Was this helpful?

ID
Risk Group
Risk Vectors
Risk Vector Description

SPS1

Process

Exit Risk - Deliguent state

  • No new stake will be allocated to the Node Operator (happens automatically)

  • the daily rewards sent to the Node Operator will be halved (with the remaining half sent towards that day’s rebase) (happens automatically)

  • reduced rewards will continue for the duration of a cooldown period long enough to determine whether, immediately after service restoration by the Node Operator, subsequently received validator exit requests are processed in a timely manner.

tbd