A monetary system whose ordinary commercial operation generates continuous, non-speculative Bitcoin acquisition at spot.
The framework described in this report specifies three financial products, each backed by Bitcoin reserves held in publicly verifiable wallets on the base layer. A stablecoin. A savings instrument. A capital markets product. Each requires the issuer to purchase actual Bitcoin on the open market at the moment of issuance. Not a derivative. Not synthetic exposure. An actual spot purchase, deposited into a transparent reserve.
A consumer using the stablecoin to buy groceries has indirectly generated a Bitcoin purchase. A worker directing a portion of their paycheck into the savings product has generated another. An institutional allocator purchasing the yield instrument has generated a third. None of these participants need to understand Bitcoin, hold a conviction about its price, or interact with an exchange. They are using financial products that happen to be better than the fiat alternatives available to them. The Bitcoin acquisition is a mechanical consequence of the product's architecture, not a decision anyone makes.
This demand has a different character than the demand that drives Bitcoin's price today. It is not driven by speculation, sentiment cycles, or leverage. It is driven by commerce: salaries, grocery bills, rent payments, retirement contributions. A coffee shop accepting the stablecoin generates the same buy pressure in a bear market as in a bull market. That bid persists as long as the commerce persists. It does not reverse when sentiment shifts.
Critically, these products create no synthetic supply. Derivative markets, futures contracts, and ETF shares have historically allowed investors to gain exposure to scarce assets without requiring acquisition of the physical underlying asset. This dynamic has suppressed commodity prices for decades. The products described here work in the opposite direction. Every unit of demand flows through to the spot market as an actual purchase. The instrument strengthens the value of its own reserve.
The stablecoin market is serving the use case Bitcoin was built for, and routing every dollar into government debt.
The $317 billion stablecoin market exists because people need digital dollars. Migrant workers sending remittances. Merchants in emerging markets settling cross-border transactions. Traders moving between positions. Ordinary people in countries with unstable currencies looking for something that holds its value. This is the demand that Bitcoin's earliest advocates expected would drive global adoption.
It has driven adoption. Just not of Bitcoin. USDT and USDC captured it. Tether alone now holds more US sovereign debt than many countries. The capital is real, the demand is real, and 100% of it flows into government bonds rather than into the monetary network designed to replace them.
ARK Invest quantified the cost in November 2025, cutting $300,000 from its 2030 bull-case Bitcoin price target specifically because stablecoins were absorbing the emerging-market demand ARK had previously attributed to Bitcoin.[4]
The important observation is not that the stablecoin market is large. It is that the underlying demand, the need for stable digital money, is entirely compatible with Bitcoin as the reserve. Nothing about a dollar-pegged token requires the reserve to be Treasury bills. A stablecoin can target the same $1.00 peg, serve the same use cases, and back every token with Bitcoin purchased at spot instead. The consumer experience is identical. The reserve asset is fundamentally different. And the capital that currently strengthens the US government's balance sheet would instead strengthen Bitcoin's monetary network.
Bitcoin's protocol does not need modification. The infrastructure above it has not been built.
Bitcoin has proven itself as a store of value and a settlement network. What remains absent is the layer that makes it functional for the daily economic activity of people who are not Bitcoiners. A merchant needs stable prices. An employer needs a predictable unit for payroll. A saver needs a product that captures upside without demanding tolerance for 40% drawdowns. These are infrastructure problems, not protocol problems.
The framework begins with a denomination called ₿C (Bitcoin Currency): the cumulative arithmetic mean of every daily Bitcoin price in USD since the genesis block. ₿C is not a token. Nothing denominated "₿C" moves in a transaction. It is a unit of account, a standard for expressing value, computed from publicly available data and verifiable by anyone.
The ₿C Formula
₿C(d) = (1/N) × Σ BTCADP(i),
for i = 1 to N
Where N is the total number of days in Bitcoin's history through the previous completed day, and BTCADP(i) is the Bitcoin Average Daily Price for each day. The price updates once per day at midnight UTC and is locked for the following 24 hours.
Because ₿C averages more than six thousand daily prices, individual days carry negligible weight. A severe single-day crash in BTC spot moves the ₿C price by hundredths of a percent. This gives merchants the stability needed to set prices without constant adjustment. And because Bitcoin's long-run trajectory has been upward, the cumulative average appreciates over time. The measuring stick itself gains purchasing power rather than losing it, the inverse of what happens under fiat.
As of early 2026, ₿C is approximately $18,700, representing the average of over 6,000 daily Bitcoin prices across the network's entire history. BTC spot, the live market price, is many multiples of that figure. When a merchant prices an item at 1 ₿C, that price tag is stable. It moves less than 0.1% per day under any market conditions. But a buyer who holds Bitcoin holds satoshis, and satoshis are valued at spot. If BTC spot drops 50% overnight, the price tag barely moves while the buyer's holdings lose half their purchasing power. ₿C protects the price tag. It does not protect the buyer's holdings.
This is not a deficiency. It is a boundary, and it is the boundary that defines why the instruments described in Section 4 exist. A unit of account and a store of value are different functions of money. ₿C fulfills the first. To stabilize the holder's purchasing power requires a counterparty, a reserve, and a token. That is exactly what the products in Section 4 provide: a stablecoin for spending, a savings instrument for growing, and a capital markets instrument for institutional yield. The unit of account is the foundation. The instruments are the structure built on it.
In practice, ₿C is what appears on the price tag. A coffee might cost 0.000268 ₿C. That number is stable from one week to the next, because the cumulative average moves approximately 0.04% per day, invisible in any single transaction. The consumer's wallet does not show a ₿C balance. It shows a spending balance and a savings balance. ₿C tells you what things cost. It does not tell you what you hold.
The practical implication for merchants is that prices set in ₿C require periodic downward adjustment, the mirror image of the upward price adjustments every fiat-denominated merchant already makes. A ₿C merchant can schedule a quarterly price revision based on the known appreciation rate, because the rate is calculable in advance from the formula. A fiat merchant raises prices reactively when costs force them to, often absorbing months of margin erosion before acting. Both merchants adjust. One does it proactively with full information. The other does it reactively without it. Both systems move. Fiat hides its movement behind nominally flat price tags while purchasing power quietly erodes. ₿C shows its movement, slowly, predictably, in a direction that benefits the people using it.
₿C pricing also solves a commercial problem that neither dollars nor sats can solve alone. A merchant who prices in ₿C can serve customers from both monetary systems through one price tag. A consumer in the fiat economy using the stablecoin (Sphere A) sees the ₿C price, reads a dollar equivalent, and pays with the stablecoin described in Section 4. A consumer in a circular Bitcoin economy (Sphere ₿) sees the sat equivalent in their wallet and pays via Lightning. Sphere A customers think in dollars. Sphere ₿ customers think in sats. Both benefit from the price stability. Both read the same menu. A merchant who prices only in dollars locks out the Bitcoin economy. A merchant who prices only in sats locks out the fiat economy and introduces volatility that makes pricing unstable. ₿C is the common language that lets a single price tag speak to both.
₿C needs no issuer, holds no reserves, and depends on no institution. The specification is open. Any wallet or payment system can adopt it independently. It is the foundation layer. Without a stable unit of account, a complete monetary architecture is not possible. With it, one becomes buildable.
Three instruments, each serving a different function, each generating a Bitcoin purchase at issuance.
₿USD: A Treasury-Backed Digital Currency
₿USD is classified as a Treasury-Backed Digital Currency (TBDC). The term draws a deliberate structural contrast with Central Bank Digital Currencies. A CBDC is issued by an entity that can expand the money supply. A TBDC is backed by a finite reserve asset that no issuer can create, expand, or dilute. A CBDC is a new form of an old instrument: sovereign-issued money, digitized. A TBDC is a genuinely different kind of instrument. ₿USD is the first proposed instrument of this type.
A CBDC's reserve is government bonds, foreign currency, and central bank liabilities, all of which can be expanded by committee decision. A TBDC's reserve is Bitcoin, fixed at 21 million units by protocol, held in on-chain wallets that anyone can audit. A CBDC's monetary policy is discretionary: quantitative easing, rate setting, negative rates. A TBDC's monetary policy is algorithmic: a coverage ratio formula governs fee reinvestment and reserve thresholds. A CBDC can attach programmable restrictions to the holder's money: expiration dates, spending limits and geographic fencing. A TBDC carries no spending restrictions. The token is a bearer instrument that transfers peer-to-peer. And where a CBDC is designed for complete transaction visibility by the central bank, a TBDC carries data about itself, not its holder. The system monitors its own health without monitoring the people inside it.
The most consequential difference is that the consortium cannot inflate the money supply. This is not a policy commitment, but an immutable property of the reserve asset. The programmability built into a TBDC serves the holder and the network, not the issuer. Section 5 describes this in detail.
₿USD targets a $1.00 peg, identical to USDT or USDC. The difference is entirely in the collateral. When a consumer purchases ₿USD through a participating financial service provider, the issuer, a group of Bitcoin treasury companies operating under a shared governance charter (described in Section 8), buys Bitcoin at the current spot price and deposits it into a dedicated on-chain reserve (Ledger 1). One token is minted on the group's shared sidechain. At the moment of issuance, the reserve perfectly backs the outstanding obligation.
Tokens circulate peer-to-peer on the sidechain without touching the base layer. The Bitcoin reserves sit untouched, appreciating at spot. Bitcoin moves only at two points: minting and redemption. Everything between is commerce, with no interaction with Bitcoin's settlement layer.
A second reserve pool, Ledger 2, is drawn from the consortium's existing Bitcoin holdings, capital that is already on their balance sheets. This is not emergency funding raised to cover a vulnerability. It is a structural commitment of assets the treasury companies already hold. Both ledgers sit in publicly addressable wallets on Bitcoin's base layer, verifiable in real time by any observer. The proof of reserves is continuous, permissionless and independent of any auditor.
The architecture is designed so that Ledger 2 is rarely drawn from. A holder who wants to exit has three paths. The default redemption path delivers Bitcoin directly to the holder's wallet at spot value. This draws BTC from Ledger 1 but creates no selling pressure on spot. The holder leaves the stablecoin but stays on the Bitcoin network. The second path is conversion to the savings product described below, which moves capital from the spending layer to the savings layer at no cost, with no delay, and no reserve action whatsoever. No Bitcoin moves. The circulating supply simply contracts. The third path is fiat redemption: the holder wants dollars. This path carries the highest fees and creates direct selling pressure. Both BTC-default and fiat redemption draw from reserves, but the system burns the most profitable tokens first (PBP#, Profit Burn Priority), those backed by Bitcoin purchased at the lowest historical prices, the tokens most deeply in surplus. Ledger 2 is drawn from only when the most profitable remaining tokens are backed by Bitcoin that has fallen below the $1 obligation.
The friction toward fiat is intentional. The architecture is designed to make remaining inside the ecosystem the most attractive option at every decision point. A holder who needs to buy something spends ₿USD. A holder who wants to grow their money converts to a savings product. A holder who wants direct Bitcoin exposure converts to BTC with one action. Circulation and savings conversion create no reserve pressure. BTC-default redemption draws from reserves but creates no selling pressure. The fiat exit carries the highest fees, the most friction, and is the only path that creates selling pressure on spot. As the ecosystem matures and more merchants, employers, and service providers operate within it, the question becomes: what exactly would a holder need to exit for? The proportion of tokens that ever touch any redemption path declines naturally as the ecosystem becomes self-sufficient. This is not a restriction on the holder. Every path remains available at all times. It is a consequence of building an ecosystem where the internal options are simply better than leaving.
With that context, the reserve mechanics become clear. PBP# (Profit Burn Priority) is the consortium's method for managing reserve health. When a redemption occurs, the consortium burns the most profitable ledger entry first because that entry carries the deepest surplus. Burning it first means every redemption costs the reserves the least possible amount. The surplus Bitcoin that remains after covering the $1 obligation stays in the system, deepening the backstop. In a cleanly rising market, PBP# produces the same result as burning the oldest tokens first because the oldest are also the cheapest and most profitable. In volatile markets, PBP# outperforms by avoiding Ledger 2 draws on underwater tokens when profitable tokens still exist in the pool. The advantage is defensive: identical total profit over the life of the system, but structural protection for Ledger 2. PBP# operates entirely on the consortium's side. The user never interacts with it.
Separate from PBP#, each individual token carries its own provenance metadata at the protocol level: mint date, mint-day spot price, mint-day ₿C price (the token's timeblock), block age, and transfer count. This metadata is what enables the defensive fee structure described below. A token minted yesterday carries different provenance data than a token minted two years ago, and the system prices redemptions accordingly. PBP# determines which satoshis leave the reserve. Token metadata determines what fees apply. Both systems operate beneath a fully fungible user experience. The user sees a balance. Every token is $1. They do not know or interact with either layer.
The demand flywheel compounds this effect. As adoption grows, more tokens are minted, more Bitcoin is purchased at spot, and the reserves appreciate. The gap between what each token cost to back and what each token returns on redemption widens with every passing day. Ledger 1's surplus deepens automatically as spot rises above historical minting prices. Ledger 2's depth grows as the consortium reinvests fee revenue into additional Bitcoin by formula. The system does not merely tolerate the passage of time. It converts time into deeper collateralization.
This is the structural inverse of traditional fractional-reserve banking. A conventional bank becomes more fragile as it scales: more deposits mean more lending, more lending means thinner coverage ratios, and thinner coverage means greater vulnerability to runs. The reserve architecture described here exhibits the opposite property. As adoption deepens and more participants earn, save, and transact within the ecosystem without converting back to fiat, the proportion of tokens that ever touch the fiat exit declines. Reserve pressure falls even as the circulating supply grows. The system becomes more robust at scale, not less.
The money multiplier in this system is exactly one. The consortium does not lend. It cannot create credit. It cannot expand the token supply beyond the Bitcoin it has purchased and holds. The total of all stablecoin tokens plus all savings and capital markets obligations can never exceed the Bitcoin held in reserve. Every token in circulation is backed by real Bitcoin on the base layer. This is the constraint that makes the architecture fundamentally different from banking: the system cannot grow beyond its reserves, and the reserves are verifiable by anyone at any moment.
The nascent stage is the most vulnerable period. When all tokens are young and the surplus is thin, the margin for error is narrowest. But the architecture is designed so that even a modest period of operation solves this. Every day the system runs, the oldest tokens age deeper into surplus. Every new mint adds Bitcoin at current spot, which will itself become deeply surplus over time. Once the demand engine has operated through even a single market cycle, the combined depth of Ledger 1 surplus and Ledger 2 holdings creates a backstop that becomes practically unbreachable under any realistic redemption scenario.
Built into this architecture from the ground up is a suite of defensive mechanisms that govern the fiat exit path. The token provenance data described above enables the system to activate these mechanisms autonomously under stress, using data about the tokens and the network, never about individual holders. Section 5 describes the full programmability model. The specific mechanisms:
Time-weighted fees make rapid mint-and-redeem cycles prohibitively expensive while leaving ordinary transactions unaffected. Volume-triggered escalation activates additional fees automatically when aggregate fiat redemption exceeds defined thresholds. Adaptive velocity limits tighten the fiat exit rate during stress events while leaving Bitcoin-default redemption unlimited at all times. The system absorbs panic without absorbing outflow.
The result is that the most dangerous scenario, a coordinated short-plus-redemption attack, has a deeply negative expected return. Bitcoin-default redemption neutralizes forced selling. Time-weighted fees extract value from freshly minted tokens. The defensive mechanisms do not make attack impossible. They make it economically irrational. Under normal conditions, which constitute the vast majority of the system's operational life, every defensive mechanism is dormant. Transfers are instant and inexpensive. Redemptions are fast. The thresholds are public, auditable, and identical for every participant. No committee convenes. No political negotiation occurs. The protocol hardens autonomously when needed and remains invisible when it is not.
From the user's perspective, none of this is visible. They hold a ₿USD balance. They spend it, receive it, save it. Every token is $1. Fully fungible. The reserve machinery operates at the protocol level, ensuring that the architecture grows stronger with every transaction, every day, and every new participant.
₿USD is distributed through regulated financial service providers operating within KYC and AML frameworks. It provides substantially greater transactional privacy than a CBDC, where surveillance is a design feature, but does not claim the privacy properties of holding Bitcoin directly.
Every ₿USD token carries a feature that no fiat stablecoin can replicate: instant conversion to Bitcoin. At any time, for any reason, a holder can convert their ₿USD to BTC at current spot and send it to a self-custody wallet. The conversion is built into the system because the reserve asset backing every token is Bitcoin sitting on a public blockchain. USDT cannot give you the Treasury bill backing your token. USDC cannot hand you the government bond. ₿USD can give you the actual Bitcoin, because it is there, on-chain, and transferable to any Bitcoin address on earth. In a fiat crisis, a CBDC announcement, or a restriction on cash withdrawals, a user holding USDT or USDC has no recourse. Their stablecoin is backed by Treasury bills they cannot access, issued by a company that can be compelled to freeze their account. A user holding ₿USD can instantly convert to Bitcoin at current spot and send it to a self-custody wallet with one action. The Bitcoin arrives in a wallet they control. No intermediary can block it. No government can freeze it. The conversion is possible because the reserve asset backing every token is Bitcoin sitting on a public blockchain. USDT cannot give you the Treasury bill. USDC cannot hand you the government bond. ₿USD can give you the actual Bitcoin, because it is there, on-chain, and transferable to any Bitcoin address on earth. ₿USD is the on-ramp. Bitcoin is the destination.
₿OND: A Savings Instrument
₿OND is a return-based savings product denominated in ₿C. A saver deposits fiat, any amount from $1 upward, and selects a target return: +10%, +25%, +50%, +100%, or other tiers. Each dollar becomes a programmable token with its own ₿C entry price and maturity trigger.
Maturity requires two conditions to be met simultaneously: the saver's ₿C return target has been reached, and the treasury's BTC position on that specific bond covers the payout plus a minimum profit margin. This dual condition means the issuing treasury never pays out at a loss. It is not a guarantee backed by a promise, but the structural definition of the maturity event itself.
The return is fixed at purchase. The timeline is variable. Backtesting against historical data produces predictable relationships between return tier and expected wait. The consumer sees a progress bar and a dynamically updated estimate. At maturity, the payout is delivered in ₿USD, not fiat. The saver can spend it, convert to fiat, or roll into a new position. Auto-reinvestment into a new ₿OND at the current ₿C price is the default. No Bitcoin is sold. The matured tokens are recycled into a new savings position, and the cycle begins again. The saver's capital compounds inside the Bitcoin ecosystem without ever exiting to fiat, without triggering a reserve liquidation, and without requiring any action. Every ₿OND that auto-reinvests is capital that stays in the system, reducing fiat redemption pressure and deepening the reserve over time.
₿ILL: A Capital Markets Instrument
₿ILL shares the same architectural foundation as ₿OND, the ₿C denomination, dual-condition maturity, and Bitcoin reserve backing, but is designed for institutional portfolios. It is tradable on secondary markets, issued in fungible tranches, and structured for the compliance and reporting requirements of pension funds, sovereign wealth managers, and corporate treasuries.
A secondary market for ₿ILL produces something that does not currently exist: a Bitcoin-backed yield curve. Quotable, screenable, and comparable alongside T-bills and corporate bonds. The relationship between ₿OND and ₿ILL mirrors the relationship between I-Bonds and TIPS in the US Treasury market: same underlying thesis, different wrapper for a different audience. Every ₿ILL issued, like every ₿OND and every ₿USD, mechanically requires a Bitcoin purchase at spot.
Sixteen years of adoption barriers, each one structural rather than ideological, each one addressed by the architecture rather than by advocacy.
The Tax Problem
In the United States and most major economies, Bitcoin is classified as property. Every transaction, no matter how small, is a disposition that triggers a capital gains calculation. A consumer who buys lunch with satoshis must track the cost basis, compute the gain or loss, and report the event. Some Bitcoiners do this diligently. Eight billion people never will. This single regulatory fact may have done more to prevent Bitcoin commerce than volatility, complexity, or any technical limitation of the protocol. It is not a deficiency in Bitcoin. It is a consequence of fiat-era tax frameworks applied to an asset they were never designed to accommodate.
₿USD eliminates this friction at the commerce layer. A consumer receives ₿USD at $1. They spend ₿USD at $1. There is no gain, no loss, no taxable event. The experience is identical to spending dollars. The Bitcoin purchase happens inside the reserve, where the consortium manages its own tax obligations as a corporate entity. The consumer never holds property in the tax sense. The tax complexity surfaces only when the user makes a conscious decision to cross into the savings layer, opening a ₿OND or converting to BTC. That is an investment decision, not a hot dog purchase. The separation of the spending layer from the savings layer is a structural solution to the tax barrier that has blocked Bitcoin commerce for over a decade.
For merchants, the same logic applies. Receiving ₿USD is ordinary business income, no different from receiving dollars via a payment processor. Tax complexity enters only when the merchant consciously routes revenue into BTC savings, a deliberate allocation, not a burden imposed on every sale. The framework does not change tax law. It routes commerce through a structure that makes existing tax law irrelevant at the point of transaction.
Defensive Programmability
CBDCs and TBDCs both embed programmable logic at the token level. The technical capability is identical. The philosophy is opposite. In a CBDC, programmability is a tool for the issuer: the token carries identity metadata, the central bank sees every transaction, and spending can be restricted by category, geography, or expiration date. China's e-CNY has been deployed with expiration dates on government disbursements, requiring recipients to spend within a defined period or lose the funds. The token reports on its holder to the authority. In a TBDC, programmability is inverted. The token carries provenance metadata about itself: mint date, mint-day BTC spot price, mint-day ₿C price, block age, and transfer count. This data describes the token's history and reserve health. It does not and cannot describe the person holding it.
Every token in the framework reports a simple health indicator. A ₿USD token reads "black" when the Bitcoin backing it is worth more than the $1 obligation, and "red" when spot has fallen below the minting price. A token minted at $85,000 spot reads black +11.8% when spot is $95,000 and red -17.6% when spot falls to $70,000. A ₿OND token tracks two indicators, one for each maturity condition. The saver condition reads red until ₿C has appreciated by the target percentage, then flips to black. The treasury condition reads red while the issuer's position on that bond is below the required profit margin, then flips to black. Both must read black for the bond to mature. The user never sees this data. They see a balance and a progress bar. The red/black system exists so the protocol can manage reserves and activate defensive behaviors autonomously.
The token contract also has read access to aggregate network metrics, all independently verifiable: total outstanding supply, aggregate redemption velocity, the coverage ratio, and BTC spot relative to ₿C. These are system-level vital signs. None of them require any information about individual holders. The system monitors its own health without monitoring the people inside it.
The defensive mechanisms described in Section 4, BTC-default redemption, time-weighted fees, volume-triggered escalation, adaptive velocity limits, and savings conversion, are activated by these network metrics. Under normal conditions, which constitute the vast majority of the system's operational life, every mechanism is dormant. Transfers are instant and inexpensive. Redemptions are fast. The thresholds that trigger defensive responses are public, auditable, and identical for every participant. No committee convenes. No political negotiation occurs. The protocol hardens autonomously to protect all participants equally, and relaxes automatically when conditions normalize.
The distinction is worth stating directly: CBDCs program money to control its holders. TBDCs program money to defend them.
The Volatility Problem
Bitcoin's price volatility has prevented it from functioning as a pricing standard for commerce. A merchant cannot set prices in an asset that moves 5 to 10% in a week. The ₿C denomination resolves this by absorbing each day's price into a cumulative average that stretches back to the genesis block. Daily movements become negligible against thousands of prior data points. The merchant can set a ₿C price and leave it unchanged for weeks, in the same way they currently leave a dollar price unchanged for weeks. The volatility has not been eliminated. It has been absorbed into an averaging window so wide that it becomes invisible at the point of sale.
The Consumer Complexity Problem
The average person should never need to know the word Bitcoin, blockchain, or sidechain. They do need to understand ₿C, the denomination in which their savings are measured and merchants set prices, but only in the way a consumer understands dollars: as the number on the screen. They see a spending balance and a savings balance. The spending balance holds its value at $1. The savings balance shows a progress bar toward a return target they selected. The interface is indistinguishable from a conventional bank account. The consumer does not need to understand how the system works. They need to understand that their savings are growing faster than what their bank currently offers, and that they can spend from their balance anywhere the stablecoin is accepted.
The Protocol Modification Problem
The entire framework operates on Bitcoin's existing base layer and a consortium-operated sidechain. No fork is required. No protocol modification is proposed. The BTCADP specification reads publicly available trade data. The ₿C denomination is computed from arithmetic. The reserve ledgers sit in standard Bitcoin wallets. The sidechain handles token circulation, and base layer settlement secures the reserves. Bitcoin's protocol is treated as complete. The infrastructure built above it is what changes.
The issuing institution profits not from lending or leverage, but from operating infrastructure whose success appreciates the reserve asset on its own balance sheet.
The revenue model for a participating treasury company has three components.
The spread. ₿USD carries a fixed $1.00 obligation per token. The Bitcoin in Ledger 1 appreciates at the spot rate. As spot rises, the gap between asset value and liability value widens at an accelerating rate, because one side moves and the other does not. This spread requires no trading and no active management. It is the arithmetic consequence of a moving asset backing a fixed obligation.
Fee income. Issuance, redemption, and conversion fees produce recurring revenue that scales with the system's throughput. Redemption fees are tiered to incentivize remaining in the ecosystem: near-zero for BTC-default redemption, progressively higher for fiat exit. Fee revenue is reinvested in additional Bitcoin reserves by formula until coverage thresholds are met. After that, it flows to the consortium members as operating profit.
Reserve appreciation through demand. This is the structural feature that distinguishes the model from anything in traditional finance. The system's own commercial activity creates buying pressure on the reserve asset. More adoption means more minting, more minting means more Bitcoin purchased at spot, and more Bitcoin purchased at spot means the consortium's existing reserves, including the portions not committed to any product ledger, appreciate in value. The institution's balance sheet benefits from the success of the system it operates. Traditional banks have no equivalent dynamic. Their reserve asset, fiat currency, depreciates by design.
The ₿USD model takes what is already a directional BTC position and attaches to it a revenue stream, a structural demand engine, and a reserve architecture that converts the passage of time into deeper collateralization. The risk profile of holding Bitcoin does not change. What changes is everything that flows from it.
The reserves already exist. The question is what they are used for.
Publicly traded Bitcoin treasury companies collectively hold more than 1.1 million BTC. These positions were accumulated through capital markets: equity offerings, convertible notes, preferred stock. The capital structure that funded this accumulation was appropriate to the phase it served. What the currency layer adds is a second channel: Bitcoin acquisition funded not by capital markets, but by customers.
When a consumer purchases a ₿USD token, one dollar enters the system and purchases Bitcoin at spot. No equity is raised. No note is issued. No obligation matures into a cash demand. The customer's fiat is the capital, and the product they receive is a service, not a debt instrument. The same applies to every ₿OND deposited and every ₿ILL issued. Each product generates a Bitcoin purchase funded by the end user.
Fee revenue from operations creates a cash flow stream that is independent of Bitcoin's spot price in any given quarter. This changes the character of the business. A company whose economics are defined entirely by BTC price exposure behaves like a leveraged position. A company with recurring revenue from monetary infrastructure behaves like an operating business, and the market has historically valued the two very differently. Infrastructure businesses command premiums based on throughput, network effects, and switching costs. The evolution from position to platform is not just an operational shift. It is a re-rating event.
The infrastructure requires real investment. Sidechain development, wallet integration, regulatory compliance across multiple jurisdictions, consortium coordination. But the return on that investment is not measured solely in fee revenue. It is measured in a Bitcoin acquisition engine that runs on consumer demand rather than on the willingness of institutional investors to fund the next capital raise. One ceiling is defined by the capacity of capital markets. The other is defined by the number of people on earth who want a better savings account, a more transparent dollar, or a financial system that does not quietly erode what they have set aside.
Distributed issuance across independent companies and jurisdictions. No single point of failure.
A single company issuing a Bitcoin-backed stablecoin would replicate the concentration risk that makes fiat stablecoins and central banks fragile. The consortium model distributes that risk. Multiple independent, publicly traded treasury companies, each in its own regulatory jurisdiction, each holding its own Bitcoin reserves. No single member can unilaterally alter reserve rules or fee structures. No single regulatory action in one jurisdiction can freeze the entire system, though individual members remain subject to local law.
The ₿C denomination and the BTCADP specification that computes it are independent of the consortium entirely. They are open mathematical standards. If the consortium dissolved tomorrow, the unit of account would continue functioning because it depends on arithmetic, not institutions.
Each product, ₿USD, ₿OND, and ₿ILL, operates within a dedicated two-ledger system entirely separate from the others. This separation is a structural firewall. A surge in ₿USD fiat redemptions during a bear market cannot reach the ₿OND reserves. Stress on the savings product cannot draw from the stablecoin's backstop. Each product's Ledger 1 and Ledger 2 are independently sized, independently verifiable, and independently solvent. Both ledgers for every product are held in publicly addressable Bitcoin wallets on the base layer, auditable by anyone with a block explorer, at any moment, without asking permission. The products share an ecosystem but never a reserve base.
Exchanges are natural partners in this structure. They hold proprietary Bitcoin reserves that make them well-suited as Ledger 2 contributors. The ecosystem's structural Bitcoin demand benefits the asset that underpins their core business. An exchange participating in the consortium is not contributing to a competitor. It is deepening the market for the asset it trades.
The founding members bear the greatest risk. They operate during the nascent stage when the surplus is thinnest and the system has not yet proven itself through a full market cycle. In return, they earn the full economic stack: issuance fees, redemption fees, the structural appreciation spread between BTC spot and the fixed dollar obligations, and the most favorable governance terms in the consortium charter. Later entrants join a proven system with deeper reserves and lower risk. They also join on terms set by the founders. The incentive to move first is not ideological. It is economic: the earliest participants capture the largest share of a system designed to compound in their favor.
Every claim made here is verifiable against the public specification before a single dollar is committed.
The liability concern. A ₿USD token is a dollar-denominated liability backstopped by Bitcoin. This is a new obligation against the reserve, and the cost should be stated plainly. When Ledger 2 is drawn from during a fiat redemption, Bitcoin is sold from the consortium's holdings. Those satoshis are not temporarily impaired. They are sold and gone. If BTC spot later recovers, the consortium does not get those satoshis back. It participates in the recovery with fewer satoshis than it started with. That is the real cost of backstopping.
The cost is real. It is also quantifiable, modelable, and bounded. Any redemption, whether to BTC or fiat, can trigger a Ledger 2 draw if the burned token is underwater. PBP# minimizes this by always burning the most profitable token first, avoiding Ledger 2 as long as any profitable token exists in the pool. Savings conversion leaves Ledger 2 untouched entirely. The architecture creates intentional friction on the fiat path: fees, velocity limits, and processing delays that make it the least attractive exit by design. The actual redemption exposure can be modeled with the same actuarial precision a bank uses to model cash withdrawal demand, with the critical difference that the full reserves are on-chain, verifiable, and have never been lent to anyone. The consortium knows its exposure in real time, not at the end of a quarterly reporting cycle.
The relevant comparison is not to having no obligation at all. It is to the obligations these companies already carry. Convertible notes create fixed cash demands that arrive during bear markets when the underlying asset has declined in value. Preferred stock dividends compound regardless of spot price. The acquisition engine that funded these obligations depends on the continued willingness of fiat capital markets to lend, and that willingness evaporates precisely when the company needs it most. ₿USD obligations are different in kind: they are funded by incoming customer capital at the moment of issuance, they produce fee revenue throughout their lifecycle, and they generate structural demand for the reserve asset. A convertible note is a liability that arrives in a bear market. A ₿USD token is a liability whose fiat exit path is the least likely to be exercised, whose cost to the reserve is minimized by PBP#, and whose existence generates buying pressure on the asset backing it.
The bank run scenario. In the default redemption path, the consortium transfers Bitcoin directly to the redeemer's wallet at spot value. No concentrated sell order hits the market. The most dangerous attack vector, forced selling that crashes spot to profit a short position, is eliminated by this single design choice. Fiat redemption remains available as a premium service with tiered fees, processing delays, and velocity limits that make coordinated attack economically irrational. The defensive mechanisms are specified in detail in the full framework.
The unfamiliar maturity model. The ₿OND's variable timeline is genuinely novel. Traditional products fix the timeline and vary the return. This product fixes the return and varies the timeline. Historical backtesting against actual data produces predictable and monotonic relationships between return tier and expected wait. The consumer interface provides a real-time estimate that updates as conditions change. Unfamiliarity is a marketing problem, not a structural one.
The existential risk. A sustained Bitcoin price decline severe enough and prolonged enough to exhaust Ledger 2 during a simultaneous mass redemption event is the tail risk. The probability is low, the defensive mechanisms raise the cost of engineering it, and the ₿C denomination's cumulative average has never declined in Bitcoin's history. But the risk is nonzero, and the specification acknowledges it.
Infrastructure, once established, becomes self-reinforcing. The rails being laid today will carry the traffic of the next generation.
China's e-CNY is already operational across major cities. The People's Bank of China describes its privacy model as "controllable anonymity": transactions appear pseudonymous to merchants while the central bank retains full access to the underlying data.[5] Nigeria has restricted ATM cash withdrawals to approximately $45 per day to accelerate digital currency adoption.[6] Western governments have been more cautious in their language, but the technical architecture of a central bank liability with central record-keeping produces the same structural outcome: a comprehensive government-accessible ledger of every retail transaction.
On the stablecoin side, USDT and USDC hold over 85% of the market.[7] Their network effects compound with every exchange listing, every merchant integration, every protocol that denominates in USDC. Each month of operation deepens the switching costs.
Monetary infrastructure has a property that distinguishes it from most technology markets: it is extremely difficult to displace once established. The SWIFT network, ACH, Fedwire, the DTCC, these systems persist for decades not because they are optimal but because the cost of migrating away from them exceeds the benefit. The digital monetary infrastructure being wired right now will exhibit the same persistence. The protocols, the integrations, the liquidity pools, the merchant networks will calcify into defaults. The question of what reserve asset sits beneath the digital economy is being answered in real time, and the current answer is US Treasury bills.
A different answer is still possible. But the window in which it is possible is defined by how far the current infrastructure has been allowed to entrench before a viable alternative reaches scale. That window is measured in years, not decades.
The institution that issues the money occupies the most consequential position in any economy.
Consider the full cycle at scale. Consumers use the stablecoin for daily commerce. The issuing consortium acquires Bitcoin at spot to back each token. That sustained acquisition creates upward pressure on the reserve asset. Rising prices widen the surplus between reserves and obligations. Deeper surplus makes the system more resilient, which attracts more participants, which generates more minting. The cycle has no natural ceiling. And unlike traditional fractional-reserve banking, which becomes more fragile as it scales, this system becomes more robust.
As the ecosystem matures and more participants earn, save, and transact without converting back to fiat, the proportion of tokens ever redeemed for fiat declines. The reserve system's exposure to spot volatility falls even as the circulating supply grows. The boundaries of the fiat economy recede, not because anyone decided to abandon fiat, but because the products on the Bitcoin side of the boundary were more useful.
This is not the endpoint. It is the enabling layer. Once a stable denomination, a functional medium of exchange, and a savings instrument exist on Bitcoin infrastructure, every product that currently runs on fiat rails becomes buildable on Bitcoin rails. Mortgages, insurance, payroll, merchant processing, lending. Each one, built on this infrastructure, inherits the same structural property: its economic activity generates Bitcoin demand at the reserve layer.
The stablecoin market alone is projected to surpass $1 trillion by 2030. The scaling math matters. At $100,000 per BTC, backing $1 trillion in ₿USD tokens would require 10 million BTC, roughly half the total supply. That is not feasible. At $1,000,000 per BTC, backing $1 trillion requires 1 million BTC, approximately what the consortium's founding members already hold. At $10,000,000 per BTC, the same reserves back $10 trillion in economic activity. The system becomes feasible at scale only if Bitcoin appreciates, which is the foundational thesis of every treasury company considering participation. The architecture does not fight this dependency. It embraces it: every token minted generates a Bitcoin purchase that contributes to the very appreciation the system requires.
A modest share of a $1 trillion market would represent tens of billions in structural Bitcoin demand, purchased with capital that would otherwise fund government debt. The full ecosystem, including savings, institutional yield, and the derivative financial products built on top of them, has a total addressable market that is difficult to overstate.
Central banks have held their position not because their monetary policy is sound, but because no credible alternative institution existed. The technology to create one is now available. The reserve asset is proven. The specification is published. The capital base exists in the treasuries of publicly traded companies that have already demonstrated the conviction to hold Bitcoin against volatility. What has been missing is the infrastructure that converts that conviction into something larger than a balance sheet line item: the operating system of a new monetary order.
The entity that issues the currency, maintains the reserve, and operates the infrastructure through which commerce flows occupies the most important seat in any economy. In the fiat system, that seat belongs to central banks. In the digital economy being built right now, it is unoccupied.
btcadp.org • CC BY-NC-ND • 2026
This work is released under the CC BY-NC-ND license.
It may be shared and redistributed with proper attribution for non-commercial purposes.
The complete framework, including full technical specifications, is published at
btcadp.org/bitcoin-bridge