slashr

Data

Every validator penalty event we have observed, as monthly CSV partitions. 120,503 events across 7 chains.

What this covers

Counts are events Slashr observed, bounded per chain by monitoring_since. A chain's history before that date is not covered and must not be inferred from these figures.

Coverage begins when we started watching a chain, which is not when the chain started. Each chain states its own anchor below. A count here is what Slashr observed in that window, and nothing more should be read into it.

Coverage by chain

ChainMonitoring sinceFirst eventLast eventEventsMonths
Avalanche26 Apr 202627 Apr 20269 Oct 20261,4697
Celestia24 Apr 202625 Apr 20269 Oct 20263117
Cosmos Hub23 Mar 202626 Mar 202610 Oct 20265408
Ethereum23 Mar 202612 Mar 202610 Oct 202698,7417
Polkadot24 Apr 202625 Apr 202610 Oct 20262,3980
Solana23 Mar 202628 Feb 202610 Oct 202616,8919
Sui23 Mar 20262 Mar 202610 Oct 20261538

Releases

Each month has a dated release: the headline figures for that window at a permanent URL. A closed month is marked final and never changes.

Monthly partitions

A closed month never changes, so its URL is permanent and safe to cite. The current month is still accruing.

Avalanche

Celestia

Cosmos Hub

Ethereum

Solana

Sui

Schema

Columns are append-only: existing columns are never reordered or renamed, so a parser written today keeps working.

  • event_id
  • network
  • validator_address
  • validator_moniker
  • event_type
  • severity
  • started_at
  • resolved_at
  • penalty_amount
  • penalty_token
  • estimated_loss_usd

Licence and citation

Licensed CC BY 4.0. Quote it, republish it, build on it. Attribution is the only condition.

Cite as:

Slashr validator penalty dataset, NullRabbit. https://slashr.dev/data

How we classify an event, and what each severity means, is set out in the methodology.

slashrLive validator incident feed.
AlertsMethodologyCheck a walletInsightsDevelopersBy NullRabbit