First day on Babylon, so I started where the security actually lives, the staking contract itself, becuase everything else in this protocol sits on top of it.
Babylon builds staking directly on Bitcoin's UTXO model. A staker creates an output whose spending conditions are defined in Bitcoin script, and those conditions are what turn ordinary btc into security collateral. Three conditions govern the contract. The holders own cryptographic signature. A time-lock expiration. And covenant committee consensus for the slashing path.
Why three seperate conditions rather then one? Becuase each answers a diffrent failure scenario. The signature requirement means nobody moves your coin without you, self custody preserved. The time-lock means the network your securing can count on the collateral staying put for a known duration, security you can schedule against. And the covenant path exists becuase slashing has to be possible without trusting the staker to punish themselves, wich no rational actor would do.
The mechanism enabling that last part is worth naming precisely, Extractable One-Time Signatures. Sign two conflicting things and your private key becomes extractable, making the punishment automatic rather then discretionary.
Notice what was NOT required for any of this. No wrapping, no bridging, no custodian. The coin never leaves Bitcoin, the script itself is the cage and the contract simultaneosly.
What im still uncertain about is the covenant committees composition and what majority threshold executes a slash, becuase thats where residual trust concentrates. Day one question, fifteen days to answer it.
@BabylonLabs_io #baby $BABY
Babylon builds staking directly on Bitcoin's UTXO model. A staker creates an output whose spending conditions are defined in Bitcoin script, and those conditions are what turn ordinary btc into security collateral. Three conditions govern the contract. The holders own cryptographic signature. A time-lock expiration. And covenant committee consensus for the slashing path.
Why three seperate conditions rather then one? Becuase each answers a diffrent failure scenario. The signature requirement means nobody moves your coin without you, self custody preserved. The time-lock means the network your securing can count on the collateral staying put for a known duration, security you can schedule against. And the covenant path exists becuase slashing has to be possible without trusting the staker to punish themselves, wich no rational actor would do.
The mechanism enabling that last part is worth naming precisely, Extractable One-Time Signatures. Sign two conflicting things and your private key becomes extractable, making the punishment automatic rather then discretionary.
Notice what was NOT required for any of this. No wrapping, no bridging, no custodian. The coin never leaves Bitcoin, the script itself is the cage and the contract simultaneosly.
What im still uncertain about is the covenant committees composition and what majority threshold executes a slash, becuase thats where residual trust concentrates. Day one question, fifteen days to answer it.
@BabylonLabs_io #baby $BABY