---
title: Understanding Babylon Slashing
description: "Understanding Babylon Slashing: Slashing Conditions for BTC/BABY Staking"
image: https://connect.bitminetech.io/hubfs/Article%209.png
---

![](https://connect.bitminetech.io/hs-fs/hubfs/Article%209.png?width=2100&height=1224&name=Article%209.png)

# Understanding Babylon Slashing

![Pier Two Team](https://app.hubspot.com/settings/avatar/d41d8cd98f00b204e9800998ecf8427e)

 Pier Two Team

May 14, 2025

Pier Two is proud to support Babylon as a Finality Provider and Validator.

BTC and BABY stakers should understand all risks relating to their delegated assets, including Babylon’s built-in slashing conditions.

Keep reading to understand the slashing risks within the Babylon ecosystem and how these risks are mitigated when staking with professional node operators.

# Overview of Slashing in Babylon

Slashing is a protocol-enforced penalty for validator misbehaviour. It is intended to discourage actions that compromise network security or integrity. Babylon introduces slashing for both:

1. **Finality Providers**: Those who stake BTC to provide time-stamping and finality to Babylon and other blockchains.
2. **Validators**: Those who stake BABY tokens to help secure Babylon’s native proof-of-stake (PoS) chain and other Babylon Secured Networks (BSNs).

# Slashing Conditions

## 1. Finality Providers — BTC Stake

- **Slashing Condition:** Equivocation (double signing). Equivocation in Babylon’s context means signing two conflicting messages for the same block height or epoch, which undermines consensus.
- **Penalty:** A fixed ratio, 0.1% of staked BTC.
- **Impact:** 
    - The slashed BTC is burned.
    - The FP enters a "Slashed" state permanently — they cannot receive any further BTC rewards.
    - Previously earned rewards are not clawed back.
- **No Slashing For:** 
    - Downtime
    - Missed votes
    - Any other behaviour apart from double-signing

## 2. Validators — BABY Stake (on Babylon Chain and other BSNs)

- **Slashing Condition:** Equivocation (double signing).
- **Penalty: **A fixed ratio, 5% of staked BABY tokens.
- **Impact:** 
    - BABY tokens are burned from the validator’s self-stake and/or delegators' stake proportionally.
    - The validator remains jailed until manually unjailed.
- **No Slashing For:** 
    - Downtime
    - Surround voting
    - Any other faults not related to double-signing

# Summary of Slashing Conditions

| **Role** | **Asset Staked** | **Slash Penalty** | **Slashing Condition** | **Slashed Funds Burned?** | **Permanently Jailed?** |
| --- | --- | --- | --- | --- | --- |
| **Finality Provider** | BTC | 0.1% | Equivocation | Yes | Yes (no more rewards) |
| **Validator** | BABY | 5% | Equivocation | Yes | No (can be unjailed) |

 

# Slashing Risk Mitigation by Pier Two

Pier Two actively reduces slashing risks through the following practices:

1. **Secure Infrastructure: **Pier Two is ISO/IEC 27001:2022 and SOC 2 Type I certified, and is actively working toward SOC 2 Type II and NORS certification. [Read more here.](https://piertwo.com/insights/pier-two-enters-soc-2-type-ii-audit-phase)
2. **Key Redundancy: **Finality Provider and Validator keys are securely stored. Signing rights are tightly controlled.
3. **Single Instance Key Management: **Validator keys are never active on more than one node simultaneously, eliminating common causes of double-signing.
4. **High Availability Infrastructure: **Uptime is maintained through globally redundant infrastructure architecture, reducing pressure to make unsafe changes that could result in slashing.
5. **Monitoring and Alerting (24/7): **Pier Two’s global team is monitoring its infrastructure 24/7 to catch anomalies before they escalate into slashing risks.

# Final Thoughts

Babylon incorporates slashing as a protocol-level risk that cannot be entirely eliminated, penalising malicious actions (equivocation) while being lenient toward non-malicious faults (eg, downtime).

# Ready to Stake?

Contact Pier Two today to learn how we can help you stake.

## Share this post

<https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fconnect.bitminetech.io%2Fblog%2Funderstanding-babylon-slashing><https://twitter.com/intent/tweet?url=https%3A%2F%2Fconnect.bitminetech.io%2Fblog%2Funderstanding-babylon-slashing><https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fconnect.bitminetech.io%2Fblog%2Funderstanding-babylon-slashing><https://pinterest.com/pin/create/button/?url=https%3A%2F%2Fconnect.bitminetech.io%2Fblog%2Funderstanding-babylon-slashing>[mailto:https%3A%2F%2Fconnect.bitminetech.io%2Fblog%2Funderstanding-babylon-slashing](mailto:https%3A%2F%2Fconnect.bitminetech.io%2Fblog%2Funderstanding-babylon-slashing)

## Keep reading

[![Pier Two is joining MAVAN, a Bitmine company](https://connect.bitminetech.io/hs-fs/hubfs/blog-images/Bitmine.png?width=676&height=381&name=Bitmine.png)

Ethereum

### Pier Two is joining MAVAN, a Bitmine company

](https://connect.bitminetech.io/blog/pier-two-is-joining-mavan-a-bitmine-company?hsLang=en)

[![](https://connect.bitminetech.io/hs-fs/hubfs/Control%20Centre%20Upgrade.png?width=2100&height=1224&name=Control%20Centre%20Upgrade.png)

### From Management to Mastery: Pier Two’s Upgraded Control Centre

](https://connect.bitminetech.io/blog/from-management-to-mastery-pier-twos-upgraded-control-centre?hsLang=en)

```json
{
  "@context" : "https://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Pier Two Team",
    "url" : "https://connect.bitminetech.io/blog/author/pier-two-team"
  },
  "dateModified" : "2025-05-14T06:39:39.357Z",
  "datePublished" : "2025-05-14T05:46:21.000Z",
  "headline" : "Understanding Babylon Slashing",
  "image" : [ "https://connect.bitminetech.io/hubfs/Article%209.png" ],
  "mainEntityOfPage" : {
    "@id" : "https://connect.bitminetech.io/blog/understanding-babylon-slashing",
    "@type" : "WebPage"
  },
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "url" : "https://connect.bitminetech.io/hubfs/BMNR_logo_transparent.png"
    },
    "name" : "Bitmine MAVAN"
  }
}
```