The short answer: not natively
Chapter 18 already laid out the mechanical difference between the two consensus models: proof-of-work earns the right to add the next block by spending real, external electricity and hardware; proof-of-stake earns it by locking up the network's own coin as collateral. Bitcoin has run on proof-of-work since block zero and has no protocol-level concept of "stake" at all — there's no built-in mechanism where locking BTC on Bitcoin's own chain earns you a share of new issuance or transaction fees the way locking ETH does on Ethereum. If a product, exchange, or article uses the word "staking" for Bitcoin specifically, it's describing something built on top of or alongside Bitcoin, never a change to Bitcoin's own base layer.
Then what is everyone actually doing?
Three distinct arrangements get called "Bitcoin staking" in practice, and they don't share much beyond the label:
For the lending case, the SEC staff's investor bulletin on crypto interest-bearing accounts explains that returns can come from lending and other investment activities, with risks including illiquidity, default and the platform's bankruptcy. Read the actual account terms and disclosures rather than inferring protection from the word "staking."
How the native version actually works
Case 3 is worth walking through mechanically. In Babylon's transaction specification, the staking output has three spending paths: withdrawal after the original timelock expires, early unbonding, and slashing. After the original timelock expires, the staker can withdraw with their own signature. Early unbonding instead requires the staker's signature plus co-signatures from a quorum of the covenant committee, and moves the BTC into a separate unbonding output with its own waiting period. It does not require the finality provider's consent. The diagram above summarizes custody, not every spending path: keeping your key is not the same as being able to spend immediately.
The staker delegates to a "finality provider" — an operator that participates in securing the other chain. Double-signing conflicting blocks at the same height can expose that provider's signing key through the protocol's extractable signature scheme. That key alone is not enough to spend the staked BTC: the slashing path also requires the staker's signature and covenant-committee quorum signatures. Stake activation requires a pre-signed slashing transaction; the exposed provider key enables completion of that prepared transaction without fresh cooperation from the staker or provider. The protocol-specified fraction goes to a burn address, while the remainder stays in a timelocked refund output before the staker can withdraw it. Slashing is also possible during the early-unbonding waiting period. The BTC stays on Bitcoin, but stake registration, delegation and finality voting involve the separate Babylon Genesis chain.
Why yields aren't a fixed number
Every version of "Bitcoin staking" advertises a yield, and none of those numbers are a fixed, guaranteed rate — they move with how much total BTC is competing for the same delegation opportunities, market demand for the underlying service, and (for the lending-relabeled version) whatever interest rate the platform can actually charge borrowers at any given moment. This book doesn't publish live rates for the same reason it doesn't publish a live BTC/USD price: any specific percentage printed here would be stale before it mattered. The category-level distinction — custodial loan, wrapped-and-bridged, or native self-custodied delegation — is the durable thing worth understanding; the exact APY on any of them today is not.
The custody question, again
Notice that two of the three cases above put your BTC back in someone else's hands — the same tradeoff Chapter 13 already covered for exchanges and Chapter 8 covered as the one rule that outranks every other rule. "Staking" doesn't exempt an arrangement from that question; it just adds a yield on top of the same custodial risk, which arguably makes it more important to ask who actually holds the keys while your coins are locked, not less. Only the native, self-custodied case avoids handing your keys to anyone — and even there, you're still trusting a finality provider's honesty and a young protocol's code, just not trusting them with your private key directly.
Bitcoin was never built to be staked. Everything called "Bitcoin staking" is something else entirely, wearing the one word that makes it sound familiar.