#baby $BABY
@BabylonLabs_io
I expected slashing to end the moment the penalty was paid.
Then I noticed Babylon does not return the surviving BTC immediately.
If a delegated Finality Provider double-signs, the slashing transaction can spend either the active staking output or the unbonding output. One part of the BTC goes to a protocol-defined burn address. The rest moves into a separate slashing-refund output.
That refund is still timelocked.
At first, that felt unnecessarily harsh. The staker has already lost part of the position because of the provider’s behavior. Why delay access to the remainder too?
Because without the second lock, slashing could become an exit shortcut.
If the non-slashed balance were released immediately, the abnormal path could return the remaining BTC faster than ordinary unbonding. The punishment transaction would not only penalize misconduct. It could also improve liquidity.
Babylon removes that incentive by making the refund wait through the protocol’s unbonding period. Slashing remains strictly worse than following the normal exit path.
The design also exposes an uncomfortable fairness tradeoff.
An honest delegator can lose part of the stake and still wait for the rest because the protocol protects the security model, not the user’s intent.
This is the metric I would watch: not only whether slashing is enforceable, but whether every abnormal path remains economically inferior to honest unbonding.
A punishment mechanism is safest when nobody can benefit from choosing it.
@BabylonLabs_io
I expected slashing to end the moment the penalty was paid.
Then I noticed Babylon does not return the surviving BTC immediately.
If a delegated Finality Provider double-signs, the slashing transaction can spend either the active staking output or the unbonding output. One part of the BTC goes to a protocol-defined burn address. The rest moves into a separate slashing-refund output.
That refund is still timelocked.
At first, that felt unnecessarily harsh. The staker has already lost part of the position because of the provider’s behavior. Why delay access to the remainder too?
Because without the second lock, slashing could become an exit shortcut.
If the non-slashed balance were released immediately, the abnormal path could return the remaining BTC faster than ordinary unbonding. The punishment transaction would not only penalize misconduct. It could also improve liquidity.
Babylon removes that incentive by making the refund wait through the protocol’s unbonding period. Slashing remains strictly worse than following the normal exit path.
The design also exposes an uncomfortable fairness tradeoff.
An honest delegator can lose part of the stake and still wait for the rest because the protocol protects the security model, not the user’s intent.
This is the metric I would watch: not only whether slashing is enforceable, but whether every abnormal path remains economically inferior to honest unbonding.
A punishment mechanism is safest when nobody can benefit from choosing it.