Bitcoin contracts and general-purpose applications are different
Bitcoin's transaction scripts specify conditions for spending outputs. They can check signatures and require multiple signers; transactions can also impose time constraints. The Bitcoin developer guide describes Script as stack-based and not Turing complete, specifically lacking loops and gotos. These are real programmable contracts, even though their execution model differs from Ethereum's. A financial arrangement does not universally require arbitrary computation. The useful question is whether its particular rules can be enforced by Bitcoin transactions, require an additional protocol, or depend on another execution environment. [1]
Likewise, running code on a blockchain does not remove every intermediary. Ethereum's security documentation describes administrative powers such as ownership, upgrades and emergency stops. A contract may have people or governance controlling those powers. Examine the deployed system rather than treating "DeFi" as a promise that nobody can intervene. [2]
Wrapped Bitcoin: how BTC's value actually gets there
Custodial wrapping is one design, not the definition of all Bitcoin finance. In this model, a custodian holds BTC while a token represents it on another network. WBTC's project website describes a 1:1 BTC backing arrangement and says only identity-verified institutions, approved through DAO governance, can mint and burn WBTC; this is the project's description, not an independent reserve audit. [4] A backing target is not a guarantee that the token's market price will always equal BTC or that every holder can redeem directly. Before using a particular token, verify its current custodian, minting and redemption eligibility, fees and terms. The diagram below illustrates dependencies, not a recommendation or a certification of any implementation.
Controlling the keys to a wrapped token is not the same as controlling the keys to its underlying BTC reserve. Nor does a working reserve arrangement establish that an application accepting the token is safe: contract bugs, administrative controls and economic risks must be assessed separately. [2]
How many things have to keep working
The custodian is not the only dependency a wrapping design adds. The simplified comparison below shows selected parts of self-custody, exchange custody and a custodially wrapped-token arrangement. It is a way to ask separate risk questions, not an exhaustive count or a claim that every box must appear in every implementation.
Diagram text equivalent (selected dependencies, not a complete risk count):
- Self-custody: Bitcoin ledger.
- Exchange custody: Custodian → Bitcoin ledger.
- Custodially wrapped BTC used in DeFi: Custodian → Peg (WBTC) → Bridge (if crossing chains) → DeFi contract.
What's actually gone wrong, on the record
Euler's March 2023 incident was a lending-protocol exploit, not a bridge exploit. Euler Labs' retrospective attributes it to a missing account-health check in the donateToReserves function and the resulting self-liquidation strategy. It reports roughly $197 million in assets taken at the time and says 100% of the stolen funds were subsequently recovered. Those are the affected project's account of the incident and recovery, not a guarantee that a future loss would be recoverable. [3]
Keep the failure categories separate: a lending contract can be exploited without a bridge failing, and a custodian or redemption arrangement can fail independently of application code. This chapter does not infer a ranking of all DeFi risks, a permanent loss total or a reason for an exchange's delisting from that one incident.
Bitcoin-native attempts to close the gap
Do not use "Bitcoin-native" or "Layer 2" as a substitute for an implementation review. Ask what Bitcoin itself verifies, what executes elsewhere, who controls upgrades or custody, and how a user exits if an operator disappears. These questions are more useful than assuming every system advertised as built on Bitcoin inherits the same security or uses the same bridge. This chapter does not certify any named additional network.
Where this connects to the last chapter
The previous chapter discusses products marketed as "Bitcoin staking." Labels can overlap, so do not infer the mechanism from the name. Determine whether you are lending BTC to a custodian, holding a wrapped token, committing a Bitcoin output under spending conditions, or combining several arrangements. A description of one design does not establish the custody, exit or loss risks of another.
Ask what Bitcoin verifies, what the application enforces, and what still depends on somebody keeping a promise. Those are different questions.
This educational page is maintained with AI assistance by an AI Agent representing Twenty-One Million. The project has commercial and affiliate content elsewhere; no product is recommended here. Primary references support the specific distinctions cited above, not an endorsement or safety certification.