Skip to main content

Slashing Alerts API

TODO: Complete Alert Subscriptions Documentation

Subscribe to real-time slashing alerts and operator events.

Required Sections

  • Alert Types

    • slashing_event_confirmed (on-chain slashing occurred)
    • slashing_event_detected (off-chain prediction)
    • operator_suspended (temporary operator unavailability)
    • risk_score_threshold_breached (e.g., score > 70)
    • operator_registration_change (added/removed from AVS)
  • Subscription Methods

    • REST API webhook subscriptions
    • WebSocket live subscriptions
    • Email notifications
    • On-chain event logs
  • Webhook Configuration

    • Registering a webhook URL
    • Auth token for webhook validation
    • Retry policy (exponential backoff?)
    • Delivery guarantees (at-least-once?)
    • Webhook payload format
  • WebSocket Connection

    • Connection URL & authentication
    • Subscribe message format
    • Unsubscribe message format
    • Keepalive/heartbeat mechanism
  • Alert Payload Format

    {
    "alert_id": "uuid",
    "alert_type": "slashing_event_confirmed",
    "operator_address": "0x...",
    "avs_address": "0x...",
    "timestamp": "2024-01-21T14:32:00Z",
    "details": {
    "slashing_amount": "1000000000000000000",
    "reason": "equivocation"
    }
    }
  • Filtering Options

    • Subscribe to specific operators
    • Subscribe to specific AVSs
    • Subscribe to specific alert types
    • Subscribe by risk score threshold
  • Subscription Management

    • List active subscriptions
    • Pause/resume subscriptions
    • Delete subscriptions
    • Subscription history
  • Rate Limiting

    • Max subscriptions per API key
    • Max alert delivery rate
    • Burst handling
  • Error Handling

    • Invalid subscription requests
    • Connection drops & reconnection
    • Webhook failures & retries
    • Alert delivery failures
  • Examples

    • Subscribe to slashing events for specific operator
    • WebSocket subscription for risk score threshold
    • Webhook integration for insurance protocol
    • Email alerts for stakers

Use Cases

  • Restakers: Immediate notification of operator slashing
  • AVSs: Monitor operator health changes
  • Insurance: Price premiums based on slashing events
  • Dashboards: Real-time operator status updates

Status: NOT STARTED — Requires alert system design & API specification