Taproot at Five: The Quiet Upgrade Bitcoin Is Still Building On

On November 14, 2021, Bitcoin enforced the rules of block 709,632 and switched on Taproot, the network’s largest consensus change since SegWit in 2017. There was no downtime, no token, and almost no drama. Most holders never noticed. Five years later, with the anniversary landing on November 14, 2026, that quiet debut looks like the whole point: Taproot was built to be invisible, and it succeeded.

The paradox is that the upgrade almost nobody talks about has become the layer almost everything now sits on. Measured by raw usage, Taproot reads like an underachiever; by most dashboards it accounts for roughly a fifth of transactions in 2026. Measured by consequence, it is everywhere. The covenant soft-fork fight, stablecoins settling over Lightning, trust-minimized bridges pulling bitcoin into decentralized finance, and even the first serious quantum-resistance proposals all build directly on the container Taproot introduced.

This is a look at what Taproot actually changed, what it accidentally unleashed, and why, at five years old, it has turned into the foundation Bitcoin is arguing over rather than a finished feature. With Bitcoin trading around $78,000 in early September 2026 and a crowded roadmap of competing proposals, the anniversary arrives at an awkward, interesting moment.

What Taproot Actually Switched On in 2021

Taproot shipped as three linked Bitcoin Improvement Proposals. BIP-340 introduced Schnorr signatures, a signature scheme whose math is linear, which lets multiple signatures and public keys be combined into one. BIP-341 defined Taproot itself and the Pay-to-Taproot (P2TR) output, which folds a simple key path and a tree of alternative scripts into a single address. BIP-342, known as Tapscript, updated the scripting language so builders could use the new primitives without dragging along old limits.

• BIP-340 (Schnorr signatures): a linear signature scheme that lets public keys and signatures be combined into one.
• BIP-341 (Taproot): the Pay-to-Taproot output that folds a key path together with a tree of alternative scripts.
• BIP-342 (Tapscript): an updated scripting language built for the new primitives.

The practical payoff came in three forms. Privacy improved because a cooperative multisig spend or a routine Lightning channel close can now look identical to an ordinary single-signature payment on-chain. Cost fell because Schnorr signatures are a compact 64 bytes and because only the branch of a script tree you actually use has to be revealed; Chainalysis estimated the savings on complex spends at roughly a quarter. And flexibility grew, because a single Taproot output can hide many possible spending conditions behind one clean key.

Activation itself was a study in caution. Bitcoin used a mechanism called Speedy Trial, roughly 90% of miners signaled support by the middle of 2021, and enforcement began at block 709,632. Crucially, Taproot did not bolt smart contracts onto Bitcoin. It made the scripting that already existed cheaper, more private, and more extensible, and it created the P2TR container that later builders would spend the next half-decade filling with things its authors never specified.

The Adoption Curve, Five Years On

If Taproot were a startup, its growth chart would worry investors. Adoption crept along in the low single digits through 2022 as wallets and exchanges slowly added support for sending to P2TR addresses. It then spiked, cooled, and settled. By most measures in 2026 it accounts for something like 15% to 20% of transactions, and public dashboards such as the Spark SegWit and Taproot adoption tracker put organic usage in that neighborhood.

The important caveat is that adoption is not one number. You can count addresses that receive funds, transactions with at least one Taproot input, or the share of total outputs, and each method tells a different story. That is why analytics providers report different figures for the same week, and any single percentage should be read as an approximation rather than a hard number. Compared with SegWit, which took years to cross a majority of activity after its 2017 launch, Taproot is following a familiar, unhurried curve: the benefits accrue mostly to complex spenders, so casual users have little reason to switch quickly.

Exchange support tells a similar story of slow but steady progress. Major venues including Coinbase, Kraken and Binance now let customers send to and from Taproot addresses, and a growing share of self-custody wallets generate P2TR by default. What is missing is a reason for the average user to care, because the fee and privacy benefits are marginal for a simple one-input, one-output payment. Adoption therefore tracks the spread of multisig, Lightning and asset protocols more than any single wallet update.

The Accidental Cambrian Explosion: Ordinals, BRC-20 and Runes

The most consequential thing Taproot did was something none of its authors set out to do. Because Tapscript relaxed the old limits on how much data a single script could hold, and because witness data carries a discount inherited from SegWit, Taproot outputs became a cheap place to stuff arbitrary content into the blockchain. In late 2022 the developer Casey Rodarmor used exactly that property to launch Ordinals, a scheme for numbering individual satoshis and inscribing images, text, and code directly on-chain.

The floodgates opened fast. BRC-20, a rough token standard built on inscriptions, appeared in early 2023 and briefly turned Bitcoin into a meme-coin casino. Then in April 2024, at the halving block 840,000, the Runes protocol launched a more efficient fungible-token design, and Taproot usage spiked toward its all-time high. For a few months in 2024, inscriptions and Runes were the single largest driver of Bitcoin fees, pushing the average cost of a simple payment to levels not seen since the 2017 mania.

The economic side effects were large. Inscription waves repeatedly filled blocks, handed miners a windfall, and did so at exactly the moment the block subsidy was shrinking. That reshaped the debate about Bitcoin’s long-term security budget, because a healthy fee market is what is supposed to pay for mining once new issuance fades toward zero.

Reasonable people disagree fiercely about whether this was a feature or an abuse. Supporters argue it created a durable fee market that will matter as the block subsidy shrinks toward zero. Detractors argue it clogged blocks with data that has nothing to do with money. Either way, the fight was made possible by Taproot, and it set the stage for the ugliest governance battle of 2026.

The Data War Taproot Helped Start

When Bitcoin Core relaxed its default limits on arbitrary data in 2025, the long-simmering argument about inscriptions boiled over. Node operators split, with a meaningful minority switching to the Knots implementation to keep tighter filtering. By 2026 the dispute had a formal proposal attached to it: BIP-110, a temporary soft fork that would cap arbitrary data in transactions for a one-year trial.

The politics were brutal. According to research from AMINA Group, BIP-110 opened a mandatory signaling window around August 9, 2026, needed 55% of blocks over a two-week period, and drew under 2% miner support, effectively dead on arrival. Blockstream chief executive Adam Back opposed it in blunt terms, Casa security executive Jameson Lopp framed the idea as a form of censorship, and Michael Saylor circulated a point-by-point critique. The relevant point for a Taproot retrospective is simple: the network spent the summer of 2026 fighting over a problem that only exists because Taproot made on-chain data so cheap.

That fight matters beyond aesthetics. It is a preview of how Bitcoin will handle every future change to what its blocks may contain, and it hardened the informal rule that miners, not developers, hold the final vote through signaling. Anyone hoping the next soft fork will sail through should study how quickly BIP-110 sank.

Stablecoins Come to Bitcoin Through Taproot Assets

While the data war raged, a quieter use of Taproot outputs may prove more important. Taproot Assets, a protocol from Lightning Labs, embeds asset definitions inside Taproot commitments so that tokens, including dollar stablecoins, can be minted on Bitcoin and then moved over the Lightning Network for near-instant, low-fee settlement. In June 2026 the team shipped Taproot Assets version 0.8 and a developer SDK, describing the result as the first multi-asset Lightning protocol on mainnet.

The headline event came earlier in the year. After an integration the company said took fourteen months, Tether brought USDT back to Bitcoin over Lightning via Taproot Assets, closing a loop that started when the stablecoin first launched on the Omni Layer more than a decade ago. Native and bridged stablecoins now flow through wallets and services built on the protocol, giving Bitcoin something it never had at scale: dollar-denominated payments that settle in Bitcoin’s security model rather than on a separate chain.

This is a subtle but real shift. For years the stablecoin story belonged to Ethereum, Tron, and Solana. Taproot Assets does not challenge those networks on liquidity yet, but it gives Bitcoin holders a way to keep and spend dollars without leaving the base chain’s assumptions. If stablecoins are the killer app of crypto, Taproot quietly handed Bitcoin a ticket to that market.

BitVM and the Trust-Minimized Bridge

The second big thing built on Taproot outputs is BitVM, a design that lets Bitcoin verify complex computations without new opcodes by encoding them across enormous Taproot script trees and settling disputes through fraud proofs. It is clever precisely because it works within today’s rules; the price is large, cumbersome transactions that only Taproot makes affordable to express.

BitVM moved from theory to product in 2025. CoinDesk reported that Bitlayer launched a BitVM Bridge on mainnet in July 2025, using a token called YBTC pegged one to one with BTC to let holders move into decentralized finance with far weaker trust assumptions than a custodial wrapper. Around the same time, developers validated the so-called unhappy path, the fraud-proof challenge, on Bitcoin mainnet, confirming that the mechanism holds up even under congestion.

Trust-minimized is not the same as trustless, and BitVM bridges still carry real assumptions about liveness and honest challengers. That is why the design deserves the scrutiny we bring to every cross-chain system in our analysis of bridge security economics and what cross-chain trust actually costs. But it is a genuine advance, and it exists because Taproot gave builders room to encode logic that Bitcoin’s own script never natively supported.

The Covenant Question Taproot Left Open

Every workaround built on Taproot, from BitVM’s giant scripts to convoluted vault designs, points at the same missing piece: covenants, a way for a coin to constrain how it can be spent in the future. Taproot made covenants easier to imagine but did not ship them, and the resulting debate has become the central technical fight of the post-Taproot era. The community has moved past the old question of whether Bitcoin should have covenants at all; the argument now is which primitive to add and in what combination.

Several proposals compete for the next soft-fork slot. OP_CHECKTEMPLATEVERIFY (BIP-119, often shortened to CTV) is the narrow, conservative option; CHECKSIGFROMSTACK (CSFS, BIP-348) is frequently paired with it; the LNHANCE bundle from developer Brandon Black combines both plus a helper opcode; and OP_CAT (BIP-347) is the broad, powerful, and most contentious choice because it can enable recursive covenants. As Spark’s covenant comparison lays out, a CTV-plus-CSFS combination has become the developer frontrunner, though nothing has meaningful miner support yet.

Notable voices pull in different directions. Andrew Poelstra, Blockstream’s director of research and a Taproot co-author, has publicly argued that OP_CAT’s small size and expressive power make it the more elegant long-term bet, even as many engineers prefer CTV’s limited blast radius. Signaling tells the sober story: miner support for the covenant proposals has stayed negligible through mid-2026, which means any activation, if it comes, is likely a 2027 story at the earliest.

Vaults, Self-Custody and Why Covenants Matter

The strongest argument for covenants is not tokens or trading; it is security. A covenant lets you build a vault, a wallet that enforces its own spending rules, so that even an attacker who steals your keys cannot immediately drain the funds. A withdrawal could be forced to sit in a timelock, or to pass through a pre-approved address, giving the real owner a window to claw the coins back to cold storage.

That matters because, as we have argued before, the theft is often the easy part of a private-key compromise; the hard part for an attacker should be actually moving the money. Bitcoin vaults aim to make that second step slow and reversible. It is the same programmable-custody instinct that Ethereum pursues through account abstraction and smart-account wallets, only expressed in Bitcoin’s more conservative idiom, where new powers are added grudgingly and only after years of review.

The catch is that today the best vault designs are either clunky, requiring pre-signed transactions and careful key deletion, or they lean on emulated tricks rather than native support. Real covenants would make vaults simple enough for ordinary hardware wallets to offer by default. That is the prize Taproot dangled and did not deliver, and it is why the covenant debate is really a self-custody debate wearing a cryptography costume.

Adoption of vault-style custody is still early, but the direction is clear. Institutional custodians and high-net-worth holders are the natural first users, because they already run the multisig and time-lock setups that covenants would streamline. For everyone else, the promise is a wallet that fails safe: lose a key and you are inconvenienced, not immediately robbed.

The Quantum Clock and Taproot’s Script Path

The newest chapter in the Taproot story is defensive. Bitcoin’s signatures rely on elliptic-curve cryptography that a sufficiently powerful quantum computer could someday break, and 2026 brought that abstract worry closer. AMINA Group noted that late-March research from Google Quantum AI suggested breaking Bitcoin’s keys might need fewer than 500,000 physical qubits, a sharp cut from earlier estimates in the millions, and that roughly 6.9 million BTC, about a third of supply, sits in outputs that have already exposed a public key.

Here is where Taproot’s design becomes a template rather than a liability. BIP-360, a proposed quantum-resistant output type that started life as Pay-to-Quantum-Resistant-Hash and was later renamed Pay-to-Merkle-Root, behaves much like a Taproot script path but removes the key-path route that leaves a long-lived public key sitting in the open. It was merged into the Bitcoin BIP repository in February 2026 as a draft. In other words, the structure Taproot invented to make spends cheaper is now the scaffold for making them quantum-safe.

The politics are predictably fraught. A companion draft, BIP-361, co-authored by Casa’s Jameson Lopp, proposes to eventually sunset legacy signatures; its own text frames the logic bluntly, saying it turns quantum security into a private incentive, so that failing to upgrade means additional friction to access your funds. Lopp has been careful to stress how early this all is. Speaking to Cryptopolitan in mid-2026, he said the proposal is not ready for prime time, describing it as a rough idea for a contingency plan that needs more research and development. For now the threat is not considered imminent, and one 2026 workaround already lets cautious holders buy quantum-safe protection at a cost of a few hundred dollars per move, a stopgap rather than a fix.

Miniscript and the Rise of Programmable Custody

Not everything Taproot promised has stalled. One of its quieter wins is that the script path, combined with a language called Miniscript, is finally making complex Bitcoin custody legible. Miniscript lets developers express spending policies (this many keys, after this much time, with these fallbacks) in a structured way that software can analyze, sign for, and audit, instead of hand-rolling raw script and hoping for the best.

Married to Taproot, this is powerful. A single P2TR address can hide a whole decision tree of inheritance plans, corporate approval rules, and emergency recovery paths, revealing only the branch that is actually used. We went deep on this in our guide to Taproot’s script path and programmable Bitcoin custody, and it is arguably where the upgrade is quietly delivering the most value in 2026, even without covenants. Enterprise custodians and multisig providers are the early adopters, precisely the users for whom Taproot’s privacy and fee savings are largest.

The lesson is that Taproot’s payoff is lumpy. For a person buying coffee, it changes nothing. For a family office arranging a seven-of-eleven multisig with time-locked recovery, it is transformative, cheaper, more private, and easier to reason about than anything Bitcoin offered before 2021.

The 2026 Roadmap: Four Forks Fighting for One Slot

Zoom out and Taproot’s fifth year looks less like a birthday and more like a traffic jam. Bitcoin changes its consensus rules rarely and reluctantly, roughly once every four years by recent habit, yet 2026 has at least four serious proposals jostling for attention. They cannot all go first, and the community’s allergy to bundling means each must win its own long, skeptical review.

The candidates fall into distinct camps: housekeeping, restriction, expansion, and defense. The consensus cleanup work fixes old bugs, BIP-110 tried and failed to restrict data, the covenant proposals want to expand what Bitcoin can express, and the quantum drafts want to defend against a future computer. The table below sketches where each stood in 2026.

If there is a through-line, it is that Taproot changed the tempo of Bitcoin development. By proving a careful, minimally disruptive soft fork could ship, it raised the bar for everything after it, and by unleashing inscriptions it created new pressures that the next fork will have to answer.

What Taproot Did Not Deliver

Honesty requires acknowledging the gaps. The privacy gains Taproot promised are real in theory but muted in practice, because privacy is a herd property: it only works well when most spends look alike, and with adoption near a fifth, a Taproot spend can still stand out. Chain-surveillance firms adapted quickly, and the anonymity set is smaller than the marketing suggested.

Taproot also did not, by itself, make Bitcoin programmable. Everything genuinely new, from BitVM to vaults, is a workaround that squeezes logic into scripts the base layer only tolerates rather than embraces. And the key-path spend, the very thing that makes cooperative transactions look clean, is exactly the exposure the quantum drafts now want to close. Five years on, Taproot looks less like a destination and more like a well-built on-ramp to debates that are still unresolved.

None of that makes the upgrade a failure. It makes it a foundation, and foundations are judged by what gets built on them, not by how much attention they draw.

The Market Backdrop: Bitcoin Near $78,000 Into Fork Season

Protocol debates never happen in a vacuum, and the 2026 backdrop is jittery. Bitcoin spent the first week of September changing hands around $78,000, well below its 2024 highs, as traders weighed a heavy calendar of United States macro data. The spot Bitcoin exchange-traded funds that the SEC cleared in 2024 have kept large, sticky demand in the market, but they have also tied Bitcoin more tightly to the same interest-rate expectations that move equities.

That macro pressure is part of the coiled-spring setup into September’s decision week, when inflation prints and policy signals could snap the price sharply in either direction. For long-term holders the technical roadmap matters more than any single candle, but sentiment feeds development: a strong market makes miners and businesses more willing to experiment with a new fork, while a weak one makes everyone conservative. Fork season and a nervous tape are colliding at once.

For United States investors specifically, the regulatory tone has warmed relative to the enforcement-heavy years, but the SEC still shapes how tokens, staking, and custody products reach retail. A protocol upgrade like Taproot sits outside that perimeter, yet the products built on it, from stablecoins to bridged BTC, land squarely inside it.

What the Next Five Years Could Look Like

Extrapolating from Taproot’s first five years, the safest prediction is patience. Adoption will keep grinding upward as wallets default to P2TR and as Taproot Assets and Lightning pull more real payment volume through the address type. The covenant fight will likely resolve slowly, with a narrow option such as CTV plus CSFS the most probable eventual winner, and even that is unlikely to activate before 2027 given how cold miner signaling is today.

The quantum question is the wildcard. It may stay a slow-moving research topic for years, or a single dramatic hardware announcement could turn BIP-360 and BIP-361 from drafts into urgent priorities overnight. Either way, the fact that both build on Taproot’s script path means the 2021 upgrade will keep shaping Bitcoin’s defenses long after its authors have moved on.

The most fitting tribute to Taproot at five is that almost no one will mark the anniversary, and yet every serious conversation about Bitcoin’s future, about money, security, and survival, now runs straight through it. The quiet upgrade won by disappearing into the foundation. That was always the plan.

Frequently Asked Questions

When did Taproot activate, and what are BIPs 340, 341 and 342?

Taproot activated at block 709,632 on November 14, 2021, after roughly 90% of miners signaled support through the Speedy Trial process. It bundled three proposals: BIP-340 (Schnorr signatures), BIP-341 (Taproot and the Pay-to-Taproot output), and BIP-342 (Tapscript). Together they made complex spends cheaper, more private, and more extensible.

What did Taproot actually enable on Bitcoin?

Directly, it brought Schnorr signatures, key aggregation, and a script path that reveals only the branch you use, cutting fees on multisig and Lightning spends by roughly a quarter. Indirectly, its witness structure enabled Ordinals, BRC-20 and Runes, and it now underpins Taproot Assets stablecoins, BitVM bridges, and the leading quantum-resistance proposals.

Why is Taproot adoption still relatively low in 2026?

Adoption depends on wallets and exchanges defaulting to Pay-to-Taproot addresses, which has been gradual, and on users making the complex spends Taproot optimizes. By most dashboards it sits around a fifth of transactions in 2026, down from a spike near 40% in 2024 driven by inscriptions. Figures also vary by dashboard, because different methods count adoption differently.

Are covenants coming to Bitcoin?

Not yet. Several proposals compete for the next soft fork, including OP_CTV, CSFS, the LNHANCE bundle and OP_CAT, with a CTV-plus-CSFS combination emerging as the developer frontrunner. As of 2026 none has meaningful miner signaling, so activation, if it happens, is most likely a 2027 event or later.

Does the quantum threat affect Taproot addresses?

A Taproot key-path spend reveals a public key that a future quantum computer could target, and reporting suggests more than a third of all bitcoin already sits in outputs that have exposed a key. Proposed fixes such as BIP-360 reuse Taproot’s script-path structure to add a quantum-resistant output type, while BIP-361 would phase out legacy signatures. Both remain drafts, and the threat is not considered imminent.

By Ada Okafor, senior editor at HOGE Wire.