Bitcoin’s functionality is expanding beyond simple trading and long-term holding; now, it can generate passive income through interest-like rewards.
However, this earning potential comes with a condition: the Bitcoin used to generate these returns must be locked up for extended periods, ranging from several months to years. An increasing number of Bitcoin holders are engaging in time-locked contracts. These contracts offer yield opportunities but consequently restrict the immediate availability of the involved Bitcoin.
The advantage of this practice is its effect on the market; reduced circulating supply and increased opportunity for price increases driven by supply scarcity.
Bitcoin that is both time-locked and staked introduces a time-based element within the Unspent Transaction Output (UTXO) set, influencing the easily accessible supply, transaction expenses, and reactions to transaction fees.
This shift is particularly noticeable in Babylon’s self-custody model, which leverages Bitcoin script time-locks. This allows holders to stake their Bitcoin without the necessity of wrapping them. It is also noticeable in the wider implementation of locktime features at the base layer (L1).
According to Babylon, roughly 56,900 BTC are currently being staked using their platform. Babylon’s staking script documentation indicates that the system employs CLTV and CSV primitives for enforcing the time component. This places the time constraint directly at the UTXO level, rather than relying on external bridges or synthetic tokens.
Existing conditions are already favorable for limiting the supply of Bitcoin.
The long-term holder supply is approximately 14.4 million BTC, while the supply deemed illiquid is close to 14.3 million BTC. While these are classified by holder behavior and are not locked in contracts, they provide context regarding how time-locking could impact the amount of Bitcoin available for trading or selling during downturns.
To get an accurate idea of the available Bitcoin, one must deduct the coins staked via Babylon, and also discount other time-locked outputs from the total circulating supply. This discount factors in the reality that some time-locks are expiring in the near future, while certain scripts allow for partial spending.
This method results in an available Bitcoin float determined by current staking activity and locktime usage, not solely on price fluctuations.
Decisions regarding governance and strategy are shortening the time stakers have to react to changes, while also increasing protection costs. The waiting period for unstaking was reduced from 1,008 to around 301 blocks (approximately 50 hours, using the targeted block creation time).
Concurrent with this, the predetermined fee for pre-signed slashing transactions increased to 150,000 satoshis. Given a standard transaction size of 355 virtual bytes (vB), this equates to roughly 422 satoshis per vB.
The purpose of this parameter is to ensure transactions are processed even when there is resistance to including them in a block. This puts downward pressure on overall market fees. Under normal circumstances, these preset slashing fees are applied quickly and staking is simple.
If median transaction fees remain in the 50 to 200 satoshi per vB range, the preset fee should still process. However, transactions related to non-slashing operations using “child pays for parent” (CPFP) become more expensive.
If typical fees begin to rise near the slashing preset, the risk of delays in slashing increases unless the governance minimum is modified, or new methods improve the speed of package relay and mining.
According to Bitcoin Optech, version-3 transaction relay (TRUC) and package relay technologies, which seek to improve security and predictability of ancestor and child packages, are progressing through policy discussions. This is of great importance when a large number of users need to quickly access previously locked coins.
Current fee observations do not fully reflect underlying structural pressures.
The market has demonstrated median fees close to 1 satoshi per vB, indicating blockspace availability. Concurrently, mainnet.observer now categorizes time-locks by type (height-based and time-based) and displays fee-rate distribution, enabling tracking of the proportion of locked UTXOs in contrast to typical fee levels.
Should the proportion of time-locked UTXOs increase while average fees stay low, those users needing to transact quickly will be more dependent on ancestor packages and CPFP, potentially creating sharper fee spikes even if baseline demand is constant.
This represents a mechanical effect instead of a sentiment-driven one. Duration, in this case, has a direct effect on how quickly fees can spike.
The extent of this duration effect can be estimated with simple ranges. Assuming a circulating supply of around 19.7 to 19.8 million BTC, the following directional scenarios emerge when subtracting the Bitcoin staked with Babylon and conservatively adjusting for other time-locked outputs:
| Case | Babylon staked BTC | λ-adjusted time-locked BTC | Estimated free-float reduction (BTC) | Share of supply (approx.) |
|---|---|---|---|---|
| Base | 57,000 | 10,000 | 67,000 | ~0.34% |
| Growth | 100,000 | 10,000 | 110,000 | ~0.56% |
| Stretch | 200,000 | 20,000 | 220,000 | ~1.11% |
Every additional 50,000 BTC moved into firm time-locks or Babylon staking reduces the free float by approximately 0.25% of the total supply.
This is the amount of Bitcoin accessible at any one time; even small shifts in the amount of time-locked coins can have an effect on market availability.
While information on long-term holder and illiquid supply is valuable, the aforementioned method for evaluating the available supply only considers verifiable script constraints and Babylon staking so as to avoid overlap from wallets that may be held over time, yet remain accessible.
New entities are leveraging settlement periods.
Citrea is developing a zk-rollup settling on Bitcoin. They use predetermined windows for settlement in order to keep collateral and settlements secure and predictable. The project’s blog states that it is approaching mainnet launch.
Stacks’ sBTC deposits are now live, creating a process through which Bitcoin-secured collateral can interact with L1 over time windows rather than instantaneous redemptions. The security of the peg and guarantees of settlement rely on time-locks, which means that demand for L1 duration can increase independently of the activity in spot trading.
A low-risk rate of return of approximately 4% on the U.S. 10-year Treasury, commonly displayed on rate dashboards and referenced in Citrea’s documentation, provides a financial incentive for native yields to maintain demand for duration, even if Bitcoin price volatility is low.
Policy timing is also important. Bitcoin Core v30 was recently released and included ongoing discussions related to default mempool operations and relay rules.
Bitcoin Core v30 incorporated improvements to package relay and policy defaults that significantly loosened restrictions on OP_RETURN. The settings are configurable if an operator chooses to revert to a more restrictive setup. This increases the capacity of the system to process critical safety packages during periods of network congestion, and lowers risks when slashing transactions face high fees.
If defaults had been more stringent, fee levels and Babylon’s minimum slashing fee would have become more important. The mempool ties fee and staking policies together.
Two actionable observations should guide short-term monitoring efforts.
First, the recent change to Babylon’s waiting period to unstake only applies to new stakes. Existing guidance may still reference the previous 1,008-block delay. Any data analysis should take cohort timing into account.
Second, fee distribution snapshots from mainnet.observer, specifically related to the quantity of transactions below 1 satoshi per vB, should be analyzed with Babylon’s live staked count in order to identify periods where duration increases during otherwise calm blocks.
A sustained increase in the total staked amount towards 100,000 BTC would necessitate new estimations of available Bitcoin. A general upward trend in median fees would put Babylon’s preset slashing fee back on the radar.
Taken together, this creates a market where a quantifiable slice of Bitcoin now has a time-based maturity imposed through scripting or staking rules, and where peak fee activity is dictated by the quantity of Bitcoin needing to be transferred at one time.
The conditions are now shaped by Babylon’s staking volume, current fee conditions, and Bitcoin Core’s final policy choices.