I came across a discussion on the Babylon governance forum this morning: someone proposed shortening the unbonding period from 7 days to 3 days.
The most valuable information in the replies isn’t the "pro” or "con"—it’s a technical explainer that traces where the 7 days come from: the unbonding period must be ≥ the challenge window period. The challenge window is the time given to a vigilante to submit slashing evidence. If unbonding is shortened, the FP could be slashed during the challenge period—but the BTC will have already been withdrawn. In that case, slashing becomes meaningless.
7 days isn’t picked out of thin air. It comes from a chain of cryptographic constraints: the submission and verification times for EOTS evidence determine the length of the challenge window, and the length of the challenge window determines the lower bound for the unbonding period.
So when people talk about shortening unbonding, what they’re really discussing is whether the challenge window can be shortened. Shortening the challenge window means the vigilante’s response window gets tighter—which raises the requirements for coverage and speed across the monitoring network.
That proposal ultimately didn’t make it to a vote. But what made me pause wasn’t the proposal itself—rather, it was "a parameter that looks like a product-experience knob, yet is chained—step by step—to the core design of the protocol security layer".
Every number you see in the UI may have an invisible rope tied to it.
@BabylonLabs_io $BABY #baby
The most valuable information in the replies isn’t the "pro” or "con"—it’s a technical explainer that traces where the 7 days come from: the unbonding period must be ≥ the challenge window period. The challenge window is the time given to a vigilante to submit slashing evidence. If unbonding is shortened, the FP could be slashed during the challenge period—but the BTC will have already been withdrawn. In that case, slashing becomes meaningless.
7 days isn’t picked out of thin air. It comes from a chain of cryptographic constraints: the submission and verification times for EOTS evidence determine the length of the challenge window, and the length of the challenge window determines the lower bound for the unbonding period.
So when people talk about shortening unbonding, what they’re really discussing is whether the challenge window can be shortened. Shortening the challenge window means the vigilante’s response window gets tighter—which raises the requirements for coverage and speed across the monitoring network.
That proposal ultimately didn’t make it to a vote. But what made me pause wasn’t the proposal itself—rather, it was "a parameter that looks like a product-experience knob, yet is chained—step by step—to the core design of the protocol security layer".
Every number you see in the UI may have an invisible rope tied to it.
@BabylonLabs_io $BABY #baby