A treasury that holds bitcoin and does nothing else earns no return on the position and uses none of its balance-sheet utility. BTCfi is the practice of changing that, and for an institution the questions it raises are different from the ones a retail user faces. This article is educational and is not legal or investment advice; financialization decisions should be made with qualified counsel and an internal risk assessment.
What BTCfi actually means
BTCfi is the practice of putting an otherwise inert bitcoin holding to work: pledging bitcoin as collateral, lending it under defined terms, issuing bitcoin-denominated assets, or settling obligations on a Bitcoin rail. The "fi" stands for financialization, the same process that turned gold from an inert store of value into a base for loans, certificates, and settlement.
The term carries a deliberate contrast with the broader category of programmable finance built on general-purpose chains. BTCfi keeps the activity anchored to Bitcoin: bitcoin is the collateral, a Bitcoin layer is the venue, and final settlement traces back to the Bitcoin base chain. The institution does not have to trust a foreign consensus mechanism, a bridge operator, or a token contract on a chain it does not control.
For an institution, the appeal is specific. Bitcoin is the most liquid and most widely held digital asset, it settles without a counterparty, and its supply schedule is fixed and auditable. Those properties make it a credible base for credit and collateral, the same way Treasuries are a credible base in traditional markets. The work of BTCfi is building the lending, issuance, and settlement plumbing around that base without giving up the properties that made bitcoin worth holding. The clearest first example is collateralized credit, where a holder borrows against bitcoin without selling it; see Bitcoin-backed loans.
Custody and compliance come first, yield comes second
Retail discussions of putting bitcoin to work usually start with the yield number. An institution cannot, because a yield it cannot custody safely or report cleanly is a liability rather than an asset. The institutional sequence runs in the opposite direction.
First, custody. Before any position is opened, the institution needs to know that the underlying bitcoin is held under controls it can defend to an auditor: keys isolated from internet-connected systems, authorization separated across roles, and reserves that can be verified on-chain rather than merely attested on paper. A yield strategy that requires shipping bitcoin to an opaque counterparty fails this test on the first question.
Second, compliance. If the activity touches issued assets, the institution needs transfer controls that hold up to a regulator: whitelists that restrict who can receive an asset, supply controls, and the ability to demonstrate that a non-compliant transfer cannot happen rather than merely promising it will not. If the activity touches client funds, segregation and proof that client assets are not being reused are non-negotiable.
Third, and only third, yield. With custody and compliance settled, the institution evaluates the return on its merits and prices the risks that come with it. The return has to clear the cost of the controls above, plus the counterparty and protocol risk discussed below. A strategy that looks attractive before those costs are counted often looks marginal after.
This ordering is why the institutional BTCfi conversation looks different from the retail one. The constraints that retail users treat as optional are the institution's entry requirements, and they sit alongside the broader treasury question of why an institution holds bitcoin in the first place; see What is a Bitcoin treasury strategy?
The approaches, surveyed honestly
There is no single way to put bitcoin to work, and the available approaches differ sharply in where they place trust. The table below summarizes the main approaches; the sections after it explain the trade-offs.
| Approach | Where the activity happens | What it is good for | The main risk to underwrite |
|---|---|---|---|
| Lightning Network | Bitcoin layer-2 payment channels | Fast, cheap, high-volume payments and routing | Channel liquidity management, online key requirements |
| Liquid Network | Bitcoin layer-2 sidechain (federation-secured) | Confidential settlement, compliant asset issuance, faster blocks | Federation trust model, peg operation |
| Discreet log contracts | Bitcoin base layer, oracle-attested | Private bilateral contracts that settle on-chain | Oracle honesty and availability |
| Wrapped BTC on another chain | A separate, non-Bitcoin chain | Access to that chain's lending and asset markets | Bridge custodian, peg integrity, token-contract bugs |
Lightning Network
Lightning is Bitcoin's payment layer: a network of bilateral channels that settles transactions off-chain and anchors to the base chain when channels open and close. For BTCfi, Lightning is the rail for high-volume, low-value flows, instant settlement, and payment routing, rather than for collateralized credit. Its constraints are operational: channels need liquidity on both sides, and signing keys have to stay online to route, which raises the bar on key management for an institution.
Liquid Network
The Liquid Network is a Bitcoin layer-2 sidechain, developed by Blockstream and live since 2018, with roughly one-minute blocks and its own asset, LBTC, pegged one-to-one to bitcoin. Liquid matters for BTCfi because it adds two capabilities the base chain lacks natively: Confidential Transactions, which hide transaction amounts and asset types from chain observers while allowing selective disclosure to an auditor or regulator, and issued assets, which let a party mint and govern bitcoin-denominated or other tokenized assets on the same rail where bitcoin settles. An institution using Liquid keeps its activity inside the Bitcoin world while gaining settlement privacy and an issuance toolkit. The trade-off to understand is the consensus model: Liquid is secured by a federation of functionaries rather than by proof-of-work mining, and the peg between bitcoin and LBTC is operated by that federation. The same issuance mechanics underpin tokenized financial instruments on Liquid; see How asset tokenization works and How businesses use stablecoins on Liquid.
Discreet log contracts
Discreet log contracts, or DLCs, are a way to run bilateral financial contracts directly on Bitcoin without putting the contract logic on-chain. Two parties lock funds into a multisignature output and pre-sign a set of outcomes; an oracle later publishes a signature attesting to the real-world result, and that signature unlocks the agreed payout. The oracle never has to know the contract terms or that a contract exists, and only the final settlement touches the chain, so the arrangement is private and lightweight. DLCs suit collateralized bets, derivatives, and insurance-style payouts between known counterparties. The risk to underwrite is the oracle: a dishonest or unavailable oracle can misreport an outcome or stall settlement, which is why production DLC designs distribute trust across multiple oracles.
Wrapped BTC on another chain
The fourth approach moves bitcoin off Bitcoin entirely. A user sends bitcoin to a custodian, the custodian holds it, and a token representing that bitcoin is minted on a separate chain, where it can be used in that chain's lending and asset markets. The appeal is access to those markets; the cost is a stack of new risks that the institution has to underwrite on top of the original bitcoin position, covered in the next section.
Why Bitcoin-native rails change the risk math
The security argument for keeping bitcoin on Bitcoin-native rails is straightforward: each time bitcoin leaves Bitcoin and its own layers, the institution adds parties and code it now has to trust, and every added trust assumption is a new way to lose the position.
Wrapped BTC on another chain is the clearest example. For a wrapped token to exist, the actual bitcoin sits with a custodian, so the holder takes on custodian risk: if that custodian is hacked, becomes insolvent, or has its reserves frozen, the token can stop being redeemable for real bitcoin. The token also depends on a peg that has to be defended through mint-and-burn operations across two chains, and a break anywhere in that machinery can knock the token off its one-to-one value. On top of both, the token lives inside a smart contract on the destination chain, and a bug in that contract, or in the bridge that moves value between chains, is a direct path to loss. Audits reduce that risk but do not remove it. None of these failure modes exist for bitcoin that never left Bitcoin.
Bitcoin-native approaches do not eliminate risk; they keep the risk inside a system the institution already understands. A DLC concentrates its risk in the oracle, Liquid concentrates its risk in the federation and the peg, and Lightning concentrates its risk in channel and key operation. Each of those is a single, well-scoped assumption that an institution can evaluate, monitor, and price. Wrapping bitcoin onto a separate chain stacks several such assumptions at once, in a system whose security the institution does not control and whose failures it cannot reverse. The native-rail choice keeps the number of things that can go wrong small and legible.
How Blockstream's stack maps to institutional BTCfi
Blockstream builds infrastructure for this, not the financial products that run on top of it. The pieces fit the institutional ordering above.
For custody and governance, the Blockstream Enterprise Custody Engine holds the underlying bitcoin under controls an institution can show an auditor: signers managed independently from accounts, isolated hardware security modules protecting keys, Spend Policies that can automatically allow, deny, or route a transaction for review, separation of duties across Drafter, Approver, and Authorizer roles, and on-chain verifiable reserves in segregated accounts. This is the "custody first" layer, the precondition before any position is opened.
For settlement and issuance, the Liquid Network provides the confidential settlement rail, and AMP, Blockstream's asset-issuance platform, handles compliant asset issuance on it. AMP issues bitcoin-denominated or other tokenized assets with controlled supply and per-asset transfer restrictions, and in its current version those restrictions are enforced cryptographically: the hardware security module refuses to cosign a transfer that breaks a whitelist or supply rule, so a non-compliant transaction cannot settle rather than merely being discouraged. Confidential Transactions on Liquid keep amounts and asset types private from chain observers while preserving selective disclosure to a regulator. This is the "compliance" layer for any BTCfi activity that involves issued assets, including the tokenized instruments covered in What are tokenized securities?
For more expressive contract logic, Simplicity is a smart-contract language for the Liquid Network designed for formal verification. It went live on Liquid mainnet in 2025 and is still maturing, with tooling and adoption early. It lets richer Bitcoin-native contracts, the kind that today push institutions toward foreign chains, run on a Bitcoin layer instead.
The throughline is that every one of these keeps the activity on Bitcoin and its own layers. An institution can custody, issue, restrict, and settle without ever sending its bitcoin to a chain it does not control.
Frequently Asked Questions
What does BTCfi mean?
BTCfi means Bitcoin financialization: the productive use of bitcoin and bitcoin-denominated assets through lending, borrowing, collateral, yield, issuance, and settlement, carried out on Bitcoin or its layers rather than on a separate chain. The term distinguishes financial activity anchored to Bitcoin from the broader programmable-finance category built on general-purpose chains.
Is BTCfi the same as DeFi?
No. BTCfi keeps the collateral, the venue, and the final settlement anchored to Bitcoin and its native layers, so the institution does not have to trust a separate chain's consensus, a bridge operator, or a foreign token contract. The defining feature of BTCfi is that bitcoin never has to leave the system whose security the holder already trusts.
How can an institution earn yield on bitcoin without bridging it to another chain?
Several Bitcoin-native approaches exist. Discreet log contracts let two parties run collateralized contracts that settle directly on Bitcoin using an oracle for outcomes. The Liquid Network supports confidential settlement and the issuance of yield-bearing or collateralized assets on a Bitcoin layer-2. Lightning supports payment-based revenue such as routing. Each keeps the bitcoin on Bitcoin and replaces foreign-chain risk with a single, scoped assumption the institution can evaluate.
Why is wrapped BTC on another chain considered riskier?
Wrapping bitcoin onto a separate chain adds three risks on top of the original position. The bitcoin itself sits with a custodian, so a hack, insolvency, or freeze of that custodian can cut the token off from its backing. The token relies on a peg defended by mint-and-burn operations spanning two separate chains, which can break. And the token runs inside a smart contract and bridge on the destination chain, where a code bug is a direct path to loss. Bitcoin that stays on Bitcoin-native rails avoids all three.
Is yield on bitcoin ever risk-free?
No. Any return on bitcoin compensates for a risk taken: counterparty risk when bitcoin is lent or pledged, smart-contract risk when it touches a contract, custody risk when it is held by another party, and peg or bridge risk when it is moved off Bitcoin. An institution's job is to name each risk, decide whether it is acceptable, and confirm the return is large enough to justify it. When a yield is presented without a named source of risk, the risk has usually been left undisclosed rather than removed.
What does Blockstream provide for BTCfi?
Blockstream provides the Bitcoin-native rails, not the financial products. The Custody Engine in Blockstream Enterprise handles institutional custody and governance with on-chain verifiable reserves. The Liquid Network provides confidential settlement, and AMP provides compliant asset issuance with cryptographically enforced transfer restrictions. Simplicity, live on Liquid mainnet since 2025 and still maturing, supports more expressive Bitcoin-native contracts. Issuers and regulated partners build the actual financial products on top of these rails.