# Slash Protection Policy

### Types of Slashing

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) 

### **Coverage of Slashing**

* 100% downtime slashing coverage in a maximum of 14-28 days
* 10% double signing coverage in a maximum of 14-28 days \
  \&#xNAN;*(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.

### **Slashing Refund-Time**

* 14-28 days depending on the network from where we are unbounding to cover the loss. 

### **Eligible Chains**

* **Cosmos Hub**
* **Atom One**
* **Akash Network**

### **Past Slash/Refund Events**

#### **Passage validator** 

October 2023: unknown reasons, resulting in downtime slash. 

{% file src="/files/lZBAQgIwvmIkIjvSi9Ug" %}
PASG Slashing 2023-10
{% endfile %}

#### **Akash validator**

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

{% file src="/files/MyFb13ONO658pZ2Y3tjG" %}
AKT Slashing 2023-11
{% endfile %}

#### Cosmos HUB

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

{% file src="/files/50L6wBc82ylF9sGXbLYR" %}
ATOM Slashing 2024-02
{% endfile %}

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

{% file src="/files/b02EV4Vo3nt8mEH6CFQL" %}
ATOM slashing 2025-03
{% endfile %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.gatahub.zone/g/gatahub/gata-validators/slash-protection-policy.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.