Bitcoin was created as peer-to-peer digital money, not as a platform for running complex financial applications. BTCFi aims to close that gap: using BTC and the infrastructure built around Bitcoin for lending, trading, staking, yield generation, and other decentralized finance applications.
BTCFi commonly refers to Bitcoin DeFi and, more broadly, Bitcoin Finance: an ecosystem of protocols and tools designed to expand the financial utility of BTC. The goal is not to replace Bitcoin’s role as a store of value, but to let holders use it as collateral, provide liquidity, or participate in financial applications.
The key point is that BTCFi is not a single network or technology. The term covers several different models, including native BTC locking mechanisms, Bitcoin-connected networks, sidechains, bridges, and tokenized representations of bitcoin on other blockchains.
Bitcoin prioritizes security, decentralization, and simplicity over highly expressive smart contracts. Because of that, much of BTCFi relies on additional infrastructure around the Bitcoin base layer to add programmability and connect BTC liquidity with decentralized applications.
In practice, BTCFi can be divided into several main approaches.
Some protocols allow users to lock BTC directly using Bitcoin-native functions such as timelocks, which prevent specific coins from being spent for a defined period or until certain conditions are met.
Babylon, for example, uses Bitcoin scripts and timelocks to enable BTC to participate as economic security for other networks without necessarily requiring users to hand custody of their bitcoin to a centralized intermediary.
This does not mean Bitcoin itself has become a proof-of-stake blockchain. Bitcoin continues to use proof of work. Any rewards come from the external protocol making use of the locked BTC, not from Bitcoin’s own issuance mechanism.
Other solutions execute applications and smart contracts outside Bitcoin’s base layer while maintaining an economic or technical connection to it. This category includes layer 2 systems, sidechains, and networks designed to extend Bitcoin’s programmability.
Rootstock is one of the most established examples. It is a Bitcoin sidechain that supports EVM-compatible smart contracts and uses rBTC as its native asset, pegged 1:1 to BTC through a two-way peg mechanism. Rootstock also uses merge-mining, which allows Bitcoin miners to contribute to the security of the sidechain.
This infrastructure makes it possible to build DeFi applications around Bitcoin without requiring Bitcoin’s base layer to execute complex smart contracts. Money On Chain, for example, is built on Rootstock and uses its smart-contract infrastructure and rBTC as collateral to provide Bitcoin-backed financial products.
Rootstock illustrates what this type of architecture can bring to BTCFi: stablecoins, lending markets, decentralized exchanges, and other financial protocols can be built while keeping Bitcoin at the center of the system.
However, not every Bitcoin-connected network inherits Bitcoin’s security in the same way. A sidechain remains a separate blockchain and may rely on its own consensus mechanisms, bridges, multisigs, or other components. In Rootstock’s case, for example, moving between BTC and rBTC depends on its two-way peg infrastructure.
That is why saying that an application “runs on Bitcoin” is less informative than understanding which part operates on Bitcoin itself, which part runs on another network, and what mechanisms are required to move BTC between them.
Another approach is to lock BTC and issue an equivalent representation on a programmable blockchain. Assets such as WBTC or cbBTC allow tokenized bitcoin to be used in DeFi ecosystems that already have lending markets, decentralized exchanges, liquidity pools, and other applications.
The benefit is access to existing financial infrastructure. The trade-off is the introduction of additional risks involving custody, reserves, issuance and redemption mechanisms, and sometimes bridges.
A token representing BTC at a 1:1 ratio does not necessarily have the same risk profile as holding BTC directly on the Bitcoin network.
Bridges connect Bitcoin, tokenized versions of bitcoin, and different BTCFi networks. They are particularly important because the ecosystem is fragmented across multiple chains and standards.
Interoperability makes capital more flexible, but it also increases the number of components users need to evaluate. The more contracts, validators, custodians, or intermediaries that sit between the original BTC and the final application, the larger the potential attack surface.
The main use case for BTCFi is turning BTC into a more financially productive asset without necessarily selling it.
A user might deposit BTC or a representation of BTC as collateral and borrow a stablecoin against it. Bitcoin can also be supplied to lending markets, added to liquidity pools, traded on decentralized exchanges, or used in staking and restaking systems connected to other networks.
The broader objective is to improve capital efficiency.
BTC held in a wallet serves its role as an asset. BTC used as collateral can potentially provide liquidity while the holder maintains exposure to bitcoin. But that additional utility introduces new risks, including liquidation, smart-contract vulnerabilities, bridge failures, or problems with the mechanism used to represent BTC on another network.
The financial products themselves are not fundamentally new. Lending, DEXs, derivatives, stablecoins, and liquidity pools have existed in other DeFi ecosystems for years.
What makes BTCFi different is that Bitcoin sits at the center of the system, whether as the main asset, collateral, a source of liquidity, or, in some designs, an element of economic security.
The technical trade-offs also differ. Blockchains with highly expressive smart-contract environments can run these applications directly on their main execution layer. BTCFi often requires additional layers or mechanisms.
For users, one question matters more than the label attached to the protocol:
Where is my BTC actually held, and what needs to happen for me to get it back?
“Earning yield on bitcoin” can sound as though BTC itself naturally generates interest. It does not.
Yield can come from several sources: interest paid by borrowers, trading fees, token incentives, or rewards from networks that use BTC as part of their economic security model.
Bitcoin staking protocols, for example, may reward users for locking BTC so it can help secure external networks.
Understanding the source of the return is essential. An APY funded mainly through token emissions has a very different risk profile from yield generated by borrowing demand or trading fees.
Before depositing BTC into any protocol, users should ask a simple question:
Who is paying this yield, and why?
There is no single “BTCFi risk.” The risk profile depends on the architecture.
Lending protocols can expose users to liquidation. Liquidity pools can introduce losses related to changing asset prices. Wrapped bitcoin introduces custody or reserve risks. Bridges and additional networks create more technical dependencies.
Smart-contract risk is also important. A vulnerability in a BTCFi application can cause losses even if the Bitcoin network itself continues to operate normally.
Before using a protocol, it is worth checking who controls the BTC, how withdrawals work, which bridges or oracles are involved, where the yield comes from, what can trigger liquidation, and whether administrators can modify critical parts of the system.
Not exactly.
Bitcoin uses proof of work to secure its own blockchain. When a protocol refers to Bitcoin staking, it usually means that BTC is being locked and used to provide economic security to another system.
The term “staking” therefore does not tell you enough about the underlying risk. Users still need to understand what is being locked, who controls the keys, what conditions allow the BTC to be recovered, and where the rewards come from.
BTCFi addresses an important tension in the Bitcoin ecosystem: Bitcoin holds enormous liquidity, but its base layer was not designed to replicate the full range of financial applications found on more programmable blockchains.
BTCFi tries to connect those two realities.
Its value, however, should not be judged only by the APYs offered by individual protocols. A more useful question is how much security, self-custody, and verifiability each design preserves while adding new financial functionality.
That distinction helps separate infrastructure from marketing. In BTCFi, it is not enough to know that an application “uses Bitcoin.” What matters is where the BTC is held, who controls the exit path, and what can fail between the user and Bitcoin’s base layer.
