Frequently Asked
Questions

Sats are a precise unit of account for a volatile asset. That volatility creates three specific barriers to pricing that ₿C addresses directly.

Volatility. A merchant cannot price a sandwich in sats today and have that price mean the same thing tomorrow. ₿C solves this through arithmetic , a cumulative historical average whose day-to-day movements are small enough for stable pricing, even on days when Bitcoin spot crashes. Day-to-day pricing stability is a mathematical property of the denomination. The long-run appreciation is a separate property, and a desirable one.

Familiarity. Ordinary people think in purchasing power terms. A unit whose fiat-equivalent value barely moves maps onto how humans already think about money. Asking the world to redenominate its intuitions around a number that swings 10% in a day is an adoption barrier that has nothing to do with Bitcoin's technical soundness.

Friction. Every time a user has to consult the spot price, make a mental conversion, or hesitate about spending an appreciating asset, that friction kills the transaction. ₿C removes it entirely at the commerce layer without touching the protocol.

The barrier to Bitcoin functioning as everyday money is volatility: BTC spot can swing 10% in a day. ₿C solves for that specific problem. It moves approximately 0.04% per day. A merchant sets a price and can leave it unchanged for weeks. The fact that the solution also appreciates is Bitcoin's hard money property expressed in a denomination. That is the feature, not the side effect.

The magnitude is real but gradual. ₿C has appreciated between 19% and 125% annually in recent years, meaningful, but nothing like Bitcoin's spot volatility. A merchant denominating in ₿C adjusts prices periodically as the unit appreciates, exactly as any hard money economy functions. This is the mirror image of the upward price adjustments every fiat-denominated merchant already makes. The difference is that the ₿C adjustment is calculable in advance, while the fiat adjustment is reactive.

Empirical evidence from the technology sector, where prices for computing power, storage, and bandwidth have fallen consistently for decades, suggests that consumers purchase goods when they need them, even when they expect prices to fall. What changes under predictable appreciation is not the decision to spend but the incentive to save. Fiat's inflationary design punishes saving. ₿C's appreciating design rewards it.

One dollar is not always one dollar. The number on the price tag stays the same, but the purchasing power behind that number quietly erodes. The Federal Reserve targets 2% annual depreciation as policy. In practice, the rate varies unpredictably: 1.2% in 2020, 7.0% in 2021, 6.5% in 2022, 3.4% in 2023. The dollar's purchasing power is in constant motion, always downward, at a rate determined after the fact by a discretionary authority. The movement is real. It is just not visible on the price tag.

A unit of account exists to express value. Value is purchasing power. If the purchasing power of the dollar erodes, the unit of account is degrading, even though the number on the price tag has not changed. The $5 coffee is still labeled $5. But that $5 buys less of everything else than it did last year. The apparent stability is in the label. The instability is in the substance. Inflation is not a side effect of the dollar's stability. It is the expression of the dollar's instability, made invisible by nominally flat price tags.

₿C makes the opposite trade-off. The number on the price tag visibly changes, slowly, predictably, in a direction that benefits the holder. No unit of account is perfectly flat. Every unit of account moves in purchasing power. The question is not whether it moves. It is whether the movement is transparent or opaque, predictable or discretionary, beneficial or harmful to the people using it.

No. The US dollar is the measurement instrument, not the peg. ₿C measures Bitcoin's cumulative average price in dollars the same way a thermometer measures temperature in Fahrenheit , the thermometer is not Fahrenheit-dependent, it is simply using a common unit for measurement.

The ₿C denomination does not inherit dollar inflation. If the dollar inflates, the ₿C price in dollars rises accordingly , just as the BTC spot price rises. The purchasing power expressed by the ₿C unit tracks Bitcoin's history, not the Federal Reserve's balance sheet.

The USD denomination is a practical choice based on where Bitcoin's deepest liquidity has always lived. Converting ₿C to any other currency is trivial: multiply by the relevant forex rate. A future extension of the BTCADP specification may define additional currency pair variants.

No. ₿C requires no changes to the Bitcoin protocol whatsoever. No soft fork, no hard fork, no new opcodes, no consensus rule modifications. The Bitcoin network need not accommodate ₿C in any way.

The denomination operates entirely in the calculation layer. It defines a unit of account , a way to express and agree upon value , that is deterministic, publicly verifiable, and requires no real-time data beyond the daily BTCADP update at midnight UTC.

How this unit is used in practice , wallet interfaces, invoicing systems, merchant pricing, payment protocols , is left entirely to implementers. The ₿C standard specifies what the unit is and how it is computed. Nothing more.

It is a deliberate, documented convention , the opposite of arbitrary. No organized exchange existed between January 3, 2009 and July 17, 2010. A daily reference price requires a market, and no market existed. Defining those 561 days as $0.00 provides a clean, unambiguous, reproducible baseline. The alternative , treating those days as undefined , would produce an incomplete historical record.

The specification acknowledges this convention openly and invites researchers to produce alternative valuations based on documented peer-to-peer transactions, mining costs, or other methodologies. That work is encouraged.

Volume weighting across exchanges would reintroduce the exact manipulation vector the methodology is designed to eliminate. An exchange that fabricates volume would gain proportional influence over the final price. Equal weighting ensures no single exchange, regardless of its reported size, can dominate the result.

The trimmed mean handles the trade-off: if a small exchange's VWAP is an outlier, it is trimmed. If it falls within the middle 50%, its price is broadly consistent with the market and deserves equal inclusion. The known Sybil attack vector , creating multiple small exchanges to shift the mean , is documented, cost-analyzed, and detectable through the transparency record.

Nobody. The ₿C price is the cumulative arithmetic mean of every daily Bitcoin price since the genesis block. No person, institution, or publisher can alter that calculation. The methodology is the authority, not the publisher.

The independence is mathematically enforced. Because the cumulative average incorporates over 6,200 days of history, the weight of any single day's data is approximately 1/6,200 of the total. Any researcher with access to basic historical Bitcoin price data , freely available from CoinGecko, CoinMarketCap, or any standard price feed , will arrive at a ₿C price essentially indistinguishable from one computed using the most rigorous trade-level data available. The arithmetic buries the noise.

This property strengthens over time, not weakens. In ten years with 9,700 days of history, the tolerance for data imprecision is even larger. A researcher in 2035 with nothing but a free API and a spreadsheet can independently verify the ₿C price to within a fraction of a cent. If btcadp.org ceased to exist tomorrow, any competent party with the specification and trade data could continue computing the BTCADP without interruption.

₿C is a unit of account. It is not a stablecoin, a peg, or a promise. It is a standard for expressing value , derived from Bitcoin's cumulative price history, updated once per day, and verifiable by anyone.

A unit of account does not need to be flat. The meter is a unit of length. The kilogram is a unit of mass. Neither is pegged to anything. ₿C is a unit of value anchored to Bitcoin's full price history since the genesis block. Its fiat-equivalent value appreciates as that history accumulates , the daily rate converges toward Bitcoin's own long-run growth rate, compounding to meaningful appreciation over time.

It is the hard money property of Bitcoin, expressed in a denomination stable enough for pricing, invoicing, and contracts.

The ₿C price is the arithmetic mean of every daily Bitcoin price since the genesis block. It appreciates for the same reason Bitcoin's long-run price appreciates: each new day of market activity, if Bitcoin is trading above the current average, pulls that average upward. There is no backing required because there is no peg to defend. The price is a mathematical fact derived from historical data.

Each new day is a timeblock , a single observation permanently absorbed into the cumulative average. Once added, a timeblock cannot be removed or significantly altered. Its influence diminishes as subsequent days are added, but its contribution is permanent. The ₿C price today embeds every market day from January 2009 forward, weighted equally across history.

The appreciation is not guaranteed by any institution. It is the natural consequence of Bitcoin's long-run price trajectory being upward. If Bitcoin's price were to permanently decline, ₿C would eventually decline with it , just very slowly. The denomination does not fight the market. It averages it.

₿C, ₿USD, ₿ond, and ₿ILL are four distinct components of the same ecosystem. Understanding each separately makes the whole clearer.

₿C (₿C) is the unit of account , the denomination. It is the cumulative arithmetic mean of every daily Bitcoin price since the genesis block. It requires no issuer, holds no reserves, and makes no redemption promise. Any wallet, merchant, or payment system can adopt it independently. It is a standard for expressing value, not a product.

₿USD is the medium of exchange , always worth exactly $1.00, redeemable for $1.00 on demand. It is issued by a consortium of Bitcoin treasury companies, with each $1 of ₿USD backed by Bitcoin purchased at spot. Prices and values across the ecosystem are denominated in ₿C, but ₿USD is the instrument people spend and receive.

₿ond is the savings product , a return-based instrument denominated in ₿C. A saver deposits fiat and selects a target return (+10%, +25%, +50%, etc.). The treasury purchases Bitcoin at spot. The bond matures when a dual condition is met: the saver's ₿C return target has been reached, and the treasury's BTC position on that bond is profitable. At maturity, the payout is returned as ₿USD. The ₿ond is where the appreciation of ₿C is captured by long-term savers.

A ₿ond is a return-based savings instrument denominated in ₿C (₿C) and issued by a Bitcoin treasury company. A saver deposits dollars , any amount, from $1 upward , and selects a target return: +10%, +25%, +50%, +100%, or any tier offered by the issuing consortium. 1 USD = 1 ₿OND. Each dollar becomes a ₿OND with its own ₿C entry price, target return, and maturity trigger.

The consortium purchases Bitcoin at spot with the deposited funds. The bond matures when two conditions are simultaneously met: the saver's ₿C return target has been reached, and the treasury's BTC position on that specific bond is profitable. At maturity, the saver receives their payout in ₿USD , the system's dollar-pegged spending instrument , which they can spend, withdraw to fiat, or auto-reinvest into a new ₿OND.

A ₿ond matures when both conditions of the dual trigger are simultaneously met: the saver's ₿C return target has been reached, and the treasury's BTC position on that bond covers the payout plus a minimum profit margin. There is no fixed calendar date , the timeline is determined by the market.

At maturity, the saver receives their original deposit plus the chosen return, paid in ₿USD. The holder then has three options:

Auto-reinvest. The ₿USD immediately converts to a new ₿OND at the current ₿C price , no BTC is sold, no fiat changes hands. The saver compounds their returns while the treasury's BTC position remains untouched. This is the lowest-friction and structurally ideal path.

Spend it. The ₿USD enters the saver's spending wallet for everyday commerce within the ecosystem , zero sell pressure on Bitcoin.

Exit to fiat. Redeem ₿USD for dollars , the highest-friction path and the only one that triggers a BTC sale from reserves.

The treasury retains the surplus BTC , the spread between the BTC position's value and the saver's payout , as profit. The dual condition guarantees the treasury is profitable on every individual bond at every payout, by design.

No. A ₿ond cannot be spent directly. It is a savings instrument, not a payment instrument. To spend, a ₿ond holder converts their position into ₿USD , paying an implementation-defined early exit fee if the dual maturity condition has not yet been met.

This distinction is intentional. The separation of savings (₿ond) from spending (₿USD) is what gives the ₿ond its structural properties. A savings instrument that can be instantly liquidated at any moment cannot maintain the reserve architecture that makes the system robust against coordinated attacks.

The classic attack on a reserve-backed currency is a coordinated bank run: simultaneously short the reserve asset while triggering mass redemptions, using the forced selling of reserves to amplify the short position. This attack has destroyed algorithmic stablecoins and pressured overcollateralized systems. It works because redemptions can be triggered at any moment, en masse, by any sufficiently large coordinated actor.

The ₿ond's dual condition structurally defuses this. A bond cannot mature unless both the saver's return target is reached and the treasury's BTC position is profitable on that specific bond. During a sustained spot decline, neither condition is met , bonds simply wait. There is no redemption trigger that an attacker can pull. The system does not pay out during stress; it pauses.

Early conversion to ₿USD is available , with a fee. That fee is the friction that prevents the maturity structure from being circumvented. An attacker who wants to trigger early conversions at scale must pay the conversion cost on every position. At any meaningful scale, the cost exceeds the profitability of the attack long before it threatens reserve integrity.

Additionally, the dual condition guarantees the treasury is profitable on every individual bond at every payout. There is no scenario in which a maturity event weakens the treasury's reserves , every payout, by construction, leaves the treasury with surplus BTC.

They are complementary instruments designed for different purposes.

₿ond is for savers. It is denominated in ₿C (₿C), matures when a dual condition is met (saver's return target reached and treasury position profitable), cannot be spent directly, and its return is chosen by the saver at purchase. The timeline is variable , determined by the market, not a calendar date.

₿USD is for transactors. It is always worth exactly $1.00, can be spent immediately, and pays no yield. Its value proposition is a hard dollar peg backed by Bitcoin on-chain rather than government debt.

The two products connect through conversion. A ₿ond that matures pays out in ₿USD. A ₿USD holder who wants to save converts into a ₿ond. Both conversions keep capital inside the Bitcoin economy. Auto-reinvest makes the cycle seamless , a maturing ₿ond immediately rolls into a new one without touching fiat.

₿ILL is the capital markets instrument , designed for institutional investors such as pension funds, sovereign wealth managers, and corporate treasuries. It shares the same architectural foundation as ₿ond: the ₿C denomination, dual-condition maturity, Bitcoin reserve backing, and consortium issuance model.

The key difference is the wrapper. ₿ond is non-tradable by design, optimized for retail savers who never want to see a mark-to-market loss. ₿ILL is tradable on secondary markets, issued in fungible tranches, and structured for institutional portfolio integration. Think of it like I-Bonds vs. TIPS: same issuer, same inflation-protection thesis, different wrapper for a different audience.

A tradable ₿ILL with secondary market pricing produces something no Bitcoin-backed instrument has ever had: a yield curve. Portfolio managers can quote yield-to-maturity, duration, and credit quality in the language they already speak. And during bear markets, when ₿ILLs trade at a discount, counter-cyclical buyers step in , capital that flows into the system precisely when it is under the most stress.

The specific mechanics , tranche structure, secondary market infrastructure, coupon design, and minimum denomination , are deliberately left to the institutions that build and trade these instruments. The framework provides the foundation. The capital markets layer is designed to be filled by the participants best equipped to design it.

Each instrument in the framework has structurally different redemption mechanics, duration profiles, and risk characteristics. ₿USD faces demand-deposit risk. ₿OND faces maturity-timing risk. ₿ILL faces secondary-market pricing risk. These cannot share a reserve pool. The architectural principle is universal: every product has its own dedicated two-ledger system. Three products, six ledgers.

Each product has two ledgers: an issuance pool (Ledger 1) holding Bitcoin purchased at the time of product issuance, and a backstop (Ledger 2) drawn from treasury companies' existing holdings to cover redemption shortfalls.

₿USD L1 holds BTC backing outstanding $1 ₿USD. ₿USD L2 self-fortifies over time as BTC appreciation creates surplus above the $1 obligation. ₿ond L1 holds BTC purchased with saver deposits, tagged to individual bonds. ₿ond L2 provides the backstop reserve drawn from treasury holdings, sized actuarially against the known maturity book. ₿ILL L1 holds BTC purchased with institutional capital at issuance. ₿ILL L2 follows the same backstop logic, sized against the institutional obligation book.

The separation is not a bookkeeping formality. It is a structural firewall. A stress event on ₿USD cannot accelerate ₿OND maturities or draw from ₿ILL reserves. Each product lives or dies on its own reserve base. All six ledgers are held in publicly addressable Bitcoin wallets on the base layer , verifiable by any observer in real time, without an auditor.

USDT and USDC achieve price stability by holding dollar reserves , but in doing so, they reproduce every structural weakness of the fiat system they claim to improve upon. The issuer is a centralized entity that can freeze accounts, censor transactions, and is subject to regulatory capture. The reserves must be trusted and audited. And the stablecoin is, in economic substance, a digital dollar with extra steps , the user gains blockchain settlement but inherits dollar inflation, counterparty risk, and the jurisdictional vulnerabilities of the issuing entity.

₿USD backed by Bitcoin eliminates each of these dependencies. The reserves are Bitcoin on the base layer , publicly addressable, verifiable in real time by anyone without an auditor. The issuing entities are publicly traded companies whose Bitcoin holdings are a matter of public record. No single consortium member can unilaterally modify the reserve rules. The distributed structure means no single jurisdiction can freeze the entire system, though individual members may be subject to regulatory action in their jurisdictions. And critically, the reserve asset appreciates over time rather than eroding through inflation. A USDC holder's deposits back US government debt. A ₿USD holder's deposits purchase Bitcoin , an asset whose purchasing power has improved, not eroded, over every multi-year period in its history. Both target $1.00. The difference is what sits behind that dollar.

For users who want exposure to ₿C's long-run appreciation rather than a fixed dollar peg, the product is the ₿ond , a return-based savings instrument denominated in ₿C (₿C) and backed by Bitcoin reserves. See the ₿ond section of this FAQ for details.

The Terra/Luna comparison does not survive contact with the actual mechanics. Terra/Luna failed because its collateral was endogenous , the system's own token, whose value depended entirely on confidence in the system itself. When confidence broke, the collateral evaporated simultaneously with the liability. It was a circular firing squad by design.

₿USD is the structural opposite. The collateral is Bitcoin , exogenous, independently valued, liquid, and completely indifferent to whether ₿USD exists or not. Bitcoin's value does not depend on ₿USD succeeding.

The risk that does exist is straightforward and knowable: a sustained decline in BTC spot below individual reserve notes' issuance prices creates reserve shortfalls that must be covered by the backstop ledger. The system uses six separate ledgers , two per product for ₿USD, ₿ond, and ₿ILL , keeping all three products cleanly separated so stress on one cannot consume reserves of another. Treasury companies understand this risk intimately , it is directional Bitcoin exposure, which is their core business. They already model it, manage it, and hold reserves against it.

No , and this question reflects a common conflation worth addressing directly. The ratio of BTC spot price to ₿C price (roughly 4-5x at current levels) is a price relationship between two different units. It describes how many ₿C units one Bitcoin can purchase. It has no direct bearing on the ₿USD collateral ratio.

₿USD has a $1 liability, not a ₿C liability. When a user mints ₿USD, they send $1. The treasury uses that $1 to purchase Bitcoin at spot. Ledger 1 holds exactly enough Bitcoin to back that $1 obligation at the moment of minting. ₿USD starts at 1:1, not overcollateralized.

Surplus in the ₿USD reserve only emerges after minting, as Bitcoin's spot price appreciates above the original $1 purchase price. That growing surplus flows into Ledger 2 , the ₿USD backstop , strengthening the reserve system over time without requiring additional capital contributions.

The ₿ond is a different product with a different structure. A ₿ond has a ₿C (₿C)-denominated obligation , not a $1 obligation. The spread between Bitcoin's spot appreciation and the slowly-rising ₿C obligation is the treasury company's earned return at ₿ond maturity. These are separate instruments with separate ledgers and separate economics.

Intraday drift is only a concern at the boundaries of the system , when fiat converts to ₿USD (minting) or ₿USD converts back to fiat (redemption). Inside the currency layer, there is no drift because no conversion happens.

A merchant prices in ₿C. A customer pays in ₿USD. The merchant receives ₿USD. No spot price is consulted. No satoshi conversion occurs. The ₿C price is the same at 9am as it is at 4pm because it updates once per day at midnight UTC. Neither party is exposed to intraday Bitcoin volatility.

The system is designed for commerce to transact entirely on The ₿ridge Network. Bitcoin's base layer is touched only at the boundaries: when fiat enters and when fiat exits. Everything in between is ₿USD transfers on The ₿ridge Network, denominated in ₿C, with no reference to spot price required.

Governance structure is an implementation question for the participating treasury companies, not a specification question for the protocol. The concept demonstrates that the incentives are aligned and the mechanics are sound. How participants choose to formalize their cooperation , legal structure, jurisdiction, decision rules, default procedures , is their problem to solve, and they have every incentive to solve it well.

This is the same relationship as Bitcoin's protocol and mining pool governance. Satoshi defined the protocol and the incentive structure. Governance forms emerged organically because participants had skin in the game. The ₿C denomination and ₿USD mechanics define the protocol layer. Institutional structure follows from aligned incentives.

Importantly, the ₿C denomination computes the same way regardless of how the consortium is structured. The unit of account is not contingent on any particular governance arrangement.

Regulatory compliance is jurisdiction-specific, time-specific, and an implementation question for the entities that choose to build on this protocol. ₿USD is designed to be regulatory-framework-neutral , it can be implemented under whatever compliance structure the participants determine is appropriate in their jurisdiction.

Regulatory frameworks for Bitcoin-backed instruments are still being written. The landscape in 2026 looks different from 2023 and will look different again in 2028. Treasury companies considering this model will have legal teams whose entire job is navigating that environment. The protocol's job is to be mechanically sound. It is.