Skip to content

Slash Protection Policy

There are two types of slashings validator nodes might face:

  • Downtime (when the validator is unable to sign most of the blocks in the particular window)
  • Double signing (double signing occurs when a validating entity / private key submits two signed messages for the same block)
  • 100% downtime slashing coverage in a maximum of 14-28 days
  • 10% double signing coverage in a maximum of 14-28 days
    (we hope to increase this number in the future)

Because every network has different slashing parameters, we cannot give you estimates, but let’s take Juno Network as an example: if you delegate 100 $JUNO to GATA HUB and the validator gets downtime slashed you would be slashed 0.01 JUNO and 5 $JUNO in case of a double sign slashing.

  • 14-28 days depending on the network from where we are unbounding to cover the loss.
  • Cosmos Hub
  • Atom One
  • Akash Network

October 2023: unknown reasons, resulting in downtime slash.

⬇ PASG Slashing 2023-10

November 2023: node traffic got stuck and validator lost connection to peers, resulting in downtime slash.

⬇ AKT Slashing 2023-11

February 11, 2024: validator lost connection to peers during infrastructure upgrade, resulting in downtime slash.

⬇ ATOM Slashing 2024-02

March 5, 2025: Validator slashed because of Stride ICS chain downtime.

⬇ ATOM slashing 2025-03