The Long Winter · RELIC · August 2026
From Digital Snow
to Digital Gold
with Blockchain Alchemy
Bitcoin, Avalanche, and the Next Form of the Validator
Avalanche validators already hold the network's most valuable asset: security capital. This is a proposal to make a bounded share of that capital productive inside Bitcoin's security economy — without ever putting staked AVAX at risk.
Scroll — the field reshapes with the argument
Executive summary
If Avalanche intends to ride the next major Bitcoin wave, it should already have a vehicle in the water.
The Long Winter proposes that Avalanche expand the economic meaning of validation. AVAX already secures Avalanche. The proposal is not to invent a new arbitrary token utility; it is to make that native utility more productive.
- 01AVAX principal remains sacred. Validator and delegator principal are never pledged, rehypothecated, or exposed to BSP liquidation.
- 02BSP begins treasury-funded. Seed operating capital purchases Bitcoin-directed work directly; externally earned BTC accumulates inside a protocol-owned reserve.
- 03Participating validators may commit a defined share of future settled AVAX rewards to a native bAVAX bond market. bAVAX is issued only against haircutted, measurable AVAX receivables.
- 04The treasury retains a spread of settled AVAX and returns that surplus to validation, creating Protocol-Owned Validation while BTC becomes the hard external reserve.
- 05Only after the BTC reserve has a production history may BSP use tightly capped, low-LTV credit against treasury-owned BTC. Staked AVAX is never collateral.
- 06Autonomous agents search markets; deterministic protocol rules control risk. AI proposes. It never controls principal or overrides reserve-coverage limits.
- 07ACP-236 introduces cycle-based reward settlement and configurable auto-compounding on Fuji; ACP-77 demonstrates programmable validator-management logic for Avalanche L1s. [3][4]
- 08The first version should be voluntary, tiny, auditable, and completely outside consensus. Mandatory capability should be considered only after years of production evidence.
The two security economies already exist. BSP connects them.
The ask
Create a Foundation/Ava Labs working group for Bitcoin Security Participation and bring Relic on as a paid strategic contributor or research lead for the workstream, with a mandate to falsify, prototype, and — if it survives — ship the mechanism.
§1 · The problem
What does this system produce when speculation is not enough?
Crypto has spent most of its existence preparing for summer. Then winter comes. Incentives become expenses. Treasuries shrink in dollar terms. Mercenary liquidity leaves. Yield paid in the same token that created the yield is revealed for what it is.
The next decade
There will be many fast chains, many cheap chains, and many environments capable of running smart contracts. Execution performance will matter, but it will not be sufficient. The networks that endure will be distinguished by economic structure: external revenue, owned liquidity, durable validator incentives, resilient balance sheets, and the ability to deploy capital productively through a long winter.
§8.1 · The Foundation is already asking this
On July 30, 2026 the Avalanche Foundation publicly described the connection between ecosystem output and AVAX value accrual as the “central problem” it is working on, organizing the work around measuring value, capturing it at the protocol level, and distributing it. It names validator economics and ecosystem capital allocation as dedicated research streams.[2]
This proposal adds a fourth direction: do not limit the search for capturable value to activity that originates inside Avalanche.
§2–3 · The insight
The holy grail was not another use case. It was making the native one powerful enough.
The ecosystem spent years searching for better AVAX value accrual: more transaction demand, more L1 activity, more burns, more DeFi. These can all matter. But AVAX already has a profound use case — it is the security capital that gives Avalanche economic weight.
Validators are institutions
A validator is a persistent identity backed by capital, uptime history, revenue, delegation relationships, and continuously operating infrastructure.
We ask them to do almost nothing
We built economically identifiable security institutions and then asked them to do nothing beyond consensus. Consensus is the first duty and stays inviolable — but the economics around it can do more.
This is capital allocation, not mining
Modern Bitcoin mining is an ASIC and energy business. Nobody is proposing validator CPUs mine Bitcoin. The opportunity is financing the physical search for it.
Stop asking only how Bitcoin comes to Avalanche. Ask how Avalanche can become economically useful to Bitcoin.
What every chain already does
Asset interoperability
- Bitcoin
- Bridge / wrapper
- BTC-representation on chain
- Does not finance a miner
- Does not add SHA-256 demand
- Does not diversify a pool
- Does not make a validator contribute to Bitcoin's security economy
What Bitcoin Security Participation does
Security interoperability
- Settled validator rewards
- Capital router
- Real Bitcoin hashpower
- Finances real miners and real machines
- Adds genuine SHA-256 demand
- Builds miner, pool, and energy relationships
- Gives Avalanche an economic position inside Bitcoin security
A bridged Bitcoin token is useful asset interoperability. It is not security interoperability. Bitcoin's history cannot be reproduced by better code or larger financing — which is exactly why the productive move is to participate in its security economy rather than to imitate it.
§6 · The mechanism
One loop, and it closes.
Seed capital buys Bitcoin-directed work. That work produces BTC, which the treasury keeps. Separately, a bounded share of settled validator rewards — never principal — is bonded into bAVAX, and the spread returns to validation as protocol-owned AVAX. Two reserves compound at once.
Stage 1 of 6
Seed capital
BSP starts treasury-funded: owned operating capital, no debt, no validator collateral. The pilot has to prove execution, custody, accounting, and settlement before anything is financed.
Following the loop — hover to pin a stage
§9 · Facts, not vibes
The starting position, as of August 8, 2026.
Every figure is a dated snapshot from an official or primary source. These are arithmetic illustrations, not forecasts of realized network rewards.
BTC gross mining economy[6][7]
$0
Gross revenue capacity per year — before power, equipment, financing, pool, and operating costs.
Put in proportion
929.16 EH/s × $32.58/PH/s/day × 365
The entire stream, before any commitment · 0.80% of the Bitcoin mining economy
§10.3 median: $23.50M deployed over ten years, shown per year · 0.02% of the Bitcoin mining economy
Bitcoin's security market is enormous, but Avalanche does not need to dominate it.
A persistent fraction of a percent of global hashpower-equivalent economics would already be a historically unusual relationship between a major proof-of-stake network and Bitcoin. The objective is not to beat mining — it is to own a permanent capability inside it, and to make that position cheaper and safer over time.
§6 · Bitcoin Security Participation
Principal-protected capital flowing outward. External value flowing home.
Select any stage to read what it does. Agents propose; deterministic protocol rules decide. An AI may propose — it may never override exposure limits or custody principal.
Reward Commitment
§6.1Settled rewards divide into three buckets: withdraw, auto-compound, and Bitcoin Security Commitment. The exact implementation belongs in an ACP, but the accounting boundary is already becoming native to the P-Chain.
Select any stage in the diagram above.
§6.2–6.7 · How the search is funded
Where the cash comes from — and who eats a loss.
The obvious hostile question deserves a plain answer. BSP starts with owned seed capital and no debt, earns BTC before it may ever borrow against BTC, and issues bAVAX only against a haircutted receivable inside a hard coverage floor. Validator principal is not in the facility at all.
Proprietary BSP capital structure
BSP Treasury + bAVAX Bond Market + Protocol-Owned Validation
BTC is the hard external reserve; committed AVAX reward streams are the bondable receivable; retained AVAX becomes protocol-owned security capital.
The strongest design is treasury-first. BSP starts with seed operating capital and no debt. Bitcoin-directed work produces real BTC, and that BTC is retained inside the BSP Treasury. The network gradually owns the collateral base that finances its own future operations.
The three owned assets
Seed capital funds the first search. Net BTC produced by approved hashpower and miner-finance activity is retained as treasury reserve rather than distributed by default.
Validators can commit a defined share of future settled AVAX rewards. BSP issues a discounted fixed-maturity bAVAX claim only against that measurable receivable.
When committed rewards settle, bAVAX liabilities are redeemed first. The protocol retains the bond spread in AVAX and returns that surplus to validation, creating permanently productive AVAX owned by the BSP Treasury.
BTC is the hard external reserve. AVAX receivables are the bondable asset. Validator principal is not in this diagram because it is not in the facility.
Bootstrap, earn, own — then, maybe, accelerate
Seed capital, no debt
Relic / Foundation-side seed capital funds a tightly capped pilot directly. No debt and no validator collateral are required to prove execution, custody, accounting, and settlement.
BTC settles into the treasury
Successful Bitcoin-security activity settles back into the BSP Treasury. The treasury sells only what is necessary to preserve operating liquidity and retains net BTC as reserve.
The bond spread becomes owned AVAX
bAVAX bonding converts part of future validator reward flow into protocol-owned AVAX spread. That AVAX returns to validation and compounds.
Credit is an accelerator, never the engine
Only after the BTC reserve has a credible track record may the protocol borrow conservatively against treasury-owned BTC.
bAVAX: bonded AVAX, not a second money
bAVAX should be a fixed-maturity financing instrument, not a second monetary token. Every unit must correspond to an asset BSP has actually acquired: a haircutted claim on future settled AVAX rewards. Governance cannot mint bAVAX merely because it wants more liquidity.
Maximum bAVAX issuance
Reserve coverage
A production system could require a reserve-coverage floor such as 1.25× before a new auction opens. If coverage falls below the protocol threshold, new bAVAX issuance stops automatically. Nothing needs to be liquidated from validator stake.
Credit is optional
10%–20%MAX LTV
The BTC reserve is the treasury collateral. BSP should prove that it can earn and custody BTC before it borrows against BTC. Once production history exists, an optional low-LTV revolving line can increase working capital without selling the reserve.
A mature BSP may permit, for example, 10%–20% maximum loan-to-value against treasury-owned BTC. If BTC falls, the credit limit contracts and new draws stop. The lender has a claim only against pledged treasury assets — never against staked validator AVAX.
§6.5 · Worked example
The 1,000 AVAX bond
Step 1 of 5
A validator commits future rewards
1,000 AVAX of forecast future rewards are committed to BSP for a fixed maturity. Stake principal stays entirely outside the facility.
Position
At no step does a bAVAX holder gain a claim on staked AVAX.
§6.7 · Router and autonomous search
The treasury exists to provide working capital. The router decides where approved capital may go; autonomous agents decide only what they want to propose. These roles remain separate.
- Approved uses can include rented SHA-256 hashpower, short-duration miner working capital, ASIC finance, power-contract finance, pool liquidity, and future verifiable Bitcoin-security instruments.
- Autonomous agents propose allocations. The deterministic risk engine checks hurdle rate, duration, slippage, oracle agreement, counterparty concentration, reserve coverage, and permitted treasury exposure.
- If expected economics do not clear the hurdle rate, capital remains idle. “Do nothing” is always a valid output.
- BSP should never depend on a single marketplace, pool, custodian, lender, stablecoin, model, or execution venue.
§7 · The Safety Constitution
One invariant sits above every other design decision.
Invariant #1
One AVAX securing Avalanche can never be lost because BSP failed.
Avalanche's existing staking design is compatible with this boundary: official validator materials describe staked tokens as not subject to slashing, while ACP-236 documentation states principal is returned and rewards are settled at cycle boundaries.[1][3]
No principal rehypothecation
No validator-principal or delegator-principal rehypothecation. BSP liabilities never obtain liquidation rights over staked AVAX.
Every bAVAX maps to a real receivable
Every bAVAX must map to a haircutted AVAX receivable and remain inside a global issuance ceiling. No unbacked governance minting.
A hard reserve-coverage floor
A hard BTC reserve-coverage floor governs new bAVAX issuance. Falling below the threshold halts expansion automatically.
Borrowing is optional and treasury-level
Any external borrowing is optional, treasury-level, and low-LTV against BSP-owned BTC or other BSP-owned assets — never against validator stake.
No recursive collateral
bAVAX or claims created by BSP cannot be re-counted to manufacture additional issuance or borrowing capacity.
No Bitcoin dependency in consensus
Bitcoin, pool, oracle, market, agent, custody, bond-market, or credit failure must never impair Avalanche consensus.
Deterministic limits
Counterparty concentration, slippage, duration, oracle-deviation, reserve-LTV, and global deployment limits are deterministic.
AI is explicitly untrusted
No model is consensus-critical and no model has discretionary control of validator principal.
§8.2 · ACP-236
The adjacent staking primitive already exists
Live on Fuji, not yet scheduled for Mainnet. It introduces auto-renewed validation cycles, reward settlement at cycle boundaries, and an AutoCompoundRewardShares field. That is almost exactly where BSP belongs — and it can be tested without altering consensus.[3]
§8.3 · ACP-77
Sovereign L1s can adopt, reject, or customize
L1 validator sets are managed through their own validator managers. BSP need not be a universal mandate: the Primary Network can prove the primitive, a Bitcoin-oriented L1 could require a larger commitment, an enterprise L1 could require zero.[4]
§6.4–6.5 · bAVAX arithmetic
Move the levers yourself.
This is the document's bond arithmetic, live. At its published defaults the transaction reproduces §6.5 exactly — 1,000 AVAX committed, 900 recognized after haircut, 850 bAVAX issued, 150 AVAX retained and returned to validation. Change any assumption and watch the reserve-coverage floor decide whether a new auction may open at all.
Bond levers
Network policy — §10.1
One bond, start to finish
- 1Validator commits1.0K AVAX
- 2Recognized after 10% haircut900 AVAX
- 3bAVAX issued at auction850 bAVAX
- 4Redeemed at settlement850 AVAXbAVAX liabilities are satisfied first
- 5Retained by BSP → validation150 AVAX15.0% protocol margin
At network scale — per year
bAVAX issued
574.9KAVAX
Protocol-owned AVAX
33.8KAVAX
POV share of stake
0.017%
Reserve coverage
1.41×
Above the illustrative 1.25× floor — a new auction may open.
● These are §6.5's published figures — 1000 AVAX committed, 900 recognized, 850 bAVAX issued, 150 retained.
§9 · The Physical Layer
Why Avalanche should think beyond software.
If the next decade is defined by a rapid expansion of AI, autonomous agents, and machine-to-machine commerce, the strategic bottleneck may move downward from software to the physical capacity required to run it. This section is deliberately the most attackable part of the proposal, so it states its own critiques and answers them.
A blockchain is not a disembodied economic system. It is software executed by physical machines, connected by physical networks, powered by physical energy, cooled by physical infrastructure, and ultimately manufactured from physical materials. If the next decade is defined by a rapid expansion of AI, autonomous agents, digital services, and machine-to-machine commerce, the strategic bottleneck may move downward from software to the physical capacity required to run it.
The question is not whether Avalanche should become a semiconductor manufacturer. It should not. The question is whether a network with a treasury, validators, capital markets, and a long-term security mandate should deliberately remain blind to the infrastructure that makes digital computation possible.
I do not think it should.
The thesis
Avalanche should develop a disciplined infrastructure-allocation capability whose first objective is to secure scarce inputs to computation: powered land, grid capacity, data-center capacity, memory, networking, accelerators, advanced packaging, semiconductor equipment, and — only when economically justified — strategic manufacturing exposure.
This is an extension of the Long Winter thesis, not a departure from it. BSP begins by recognizing that Bitcoin security is physical work. The infrastructure doctrine generalizes that observation: digital networks ultimately depend on ownership, access, and financing of physical productive capacity.
The strategic objective is resilience. Avalanche should not attempt to own everything. It should build the ability to identify what is becoming scarce, quantify the economics, and acquire exposure before scarcity becomes an existential constraint.
§9.1 — An infrastructure acquisition doctrine
The network should acquire capabilities, not trophies.
The obvious criticism is that “infrastructure” is so broad that it can become a license to spend treasury capital on anything. That is exactly why the proposal needs a narrow doctrine. Every acquisition or long-term contract should pass a scarcity, strategic dependence, cash flow, and exit test.
| Layer | What BSP / Avalanche should seek | Why it matters |
|---|---|---|
| Power | Generation, PPAs, substations, transmission/interconnection rights | Compute cannot exist without reliable power; grid access can take years to secure. |
| Land & facilities | Powered land, data-center shells, cooling and fiber access | Physical sites can become bottlenecks before equipment does. |
| Compute | ASICs, GPUs/accelerators, storage, networking | Creates immediate productive capacity and procurement leverage. |
| Memory | HBM/DRAM/NAND supply relationships or strategic inventory | Memory is a first-order constraint for AI and high-performance computing. |
| Packaging | Advanced packaging/test capacity and equipment | Chip performance increasingly depends on packaging and integration. |
| Semiconductor equipment | Strategic equipment exposure or financing | Equipment lead times can constrain fab expansion even when capital is available. |
| Fabrication | Minority stakes, capacity reservations, JVs, or other structured exposure | Only pursued when the economics, governance, and strategic value justify the scale. |
Capital discipline
No infrastructure purchase should be justified by narrative alone. Each proposal should show expected cash yield, replacement cost, strategic scarcity, downside case, liquidity/exit path, counterparty risk, regulatory perimeter, and the percentage of total treasury NAV at risk. A strategic asset can be worth owning and still be a bad price.
Stage the exposure — direct ownership is the last step, not the first
- 01Contract
- 02Capacity reservation
- 03Minority investment
- 04Joint venture
- 05Controlling ownership
Keep the core protocol liquid. Infrastructure should live in a ring-fenced treasury subsidiary or legal vehicle where appropriate. The P-Chain consensus system must never depend on the solvency of a factory, data center, energy project, or infrastructure SPV.
§9.2 — The Terafab Question
A category signal — not an assumed transaction
The proposal should be precise here. Avalanche should not assume that it can purchase “a fab deck” from SpaceX, Tesla, or any other manufacturer. There is no basis for treating such a transaction as available. The point is strategic: if the world’s most vertically integrated technology companies are building manufacturing capacity because access to compute hardware is becoming a strategic constraint, Avalanche should understand that category of asset and have the institutional capability to evaluate it.
Public facts
SpaceX has publicly described Terafab as a chip-manufacturing initiative with a long-term goal of producing one terawatt of compute hardware annually. Its public filings describe a vertically integrated approach spanning chip design/lithography masks, logic and memory fabrication, advanced packaging, and testing, while also stating that specific projects remain subject to separate agreements and that Terafab is intended to complement — not eliminate — third-party sourcing. [B1][B2]
That is strategically relevant because it demonstrates a broader industrial pattern: compute supply is being treated as infrastructure. The response is not to copy another company’s manufacturing plan. It is to recognize that a digital network with a ten-year horizon should have an infrastructure strategy of its own.
A serious Avalanche infrastructure desk could maintain a watchlist of opportunities such as:
- powered data-center campuses with secured interconnection capacity
- long-term power contracts and generation assets serving compute
- ASIC, GPU, accelerator, memory, and networking supply agreements
- advanced packaging, testing, and semiconductor-equipment capacity
- minority stakes or capacity reservations in strategically important fabs
- financing structures that turn scarce physical capacity into long-duration productive assets
The target is not ownership for prestige. The target is optionality over scarce computation.
§9.3 — The obvious critiques
A proposal that cannot survive criticism should not touch a treasury.
Correct if Avalanche buys unrelated businesses. The doctrine therefore limits investment to infrastructure that materially supports computation, network security, treasury resilience, or strategically scarce digital capacity. Governance should reject anything that cannot demonstrate a measurable link.
The non-negotiable boundary
No infrastructure asset can become a hidden dependency of Avalanche consensus. If the asset fails, burns capital, becomes legally inaccessible, or is seized, the P-Chain must continue operating normally. Infrastructure is an economic layer around the protocol — not a single point of failure inside it.
§9.4 — From Bitcoin Security to Compute Security
The strategic arc of The Long Winter
BSP begins with a narrow proposition: use a portion of validator economics to create productive exposure to Bitcoin security. The infrastructure doctrine asks what happens after the first reserve exists. The answer should be disciplined expansion into the physical bottlenecks that increasingly determine the value of computation.
The capital stack
AVAX secures Avalanche. Validator rewards create a recurring economic stream. bAVAX converts a bounded portion of that stream into protocol-owned AVAX. BTC earned by BSP becomes hard external reserve collateral. Treasury credit, if later justified, finances additional productive capacity. Infrastructure assets secure optionality over power, land, memory, compute, packaging and manufacturing.
Not “buy everything” — a ladder
- 01Prove
Operate Bitcoin-security activity and publish the economics.
- 02Accumulate
Retain BTC and protocol-owned AVAX rather than distributing every unit of surplus.
- 03Secure
Convert treasury strength into long-duration access to scarce physical inputs.
- 04Partner
Use contracts, joint ventures and minority positions before attempting control.
- 05Own selectively
Acquire only assets whose replacement value, strategic scarcity and cash economics justify ownership.
- 06Compound
Reinvest genuine external cash flows into the assets that make the network harder to starve of compute.
This is the part of the thesis I believe is easiest to underestimate. The next decade may not be won by the protocol with the cleverest abstraction. It may be won by the organizations that can reliably obtain the physical resources required to execute computation at scale.
Avalanche should not attempt to become a semiconductor company. It should become an economic system capable of owning a strategic claim on the infrastructure of computation.
If that sounds too ambitious, the correct response is not to dismiss it. The correct response is to build a 90-day diligence process that determines exactly which parts are economically insane, which parts are merely difficult, and which parts are already becoming inevitable. That is the same standard applied to BSP: build the smallest version that can be falsified, publish the result, and compound only what survives.
§10 · Ten years out
10,000 paths, 2026–2036.
The revised model asks how a treasury-owned BSP can grow from a small seed while retaining BTC, acquiring AVAX through bAVAX spreads, and using optional BTC-reserve credit only after collateral exists. It is a scenario engine, not a price prediction.
Treasury-first model
Day-one operations are paid from owned seed capital. Positive operating profit is retained as BTC. bAVAX acquires validator reward receivables. Retained AVAX becomes Protocol-Owned Validation. Only earned BTC may later support low-LTV working capital.
§10.3 — Median treasury outputs
- 10-yr deployment
- $4.45M
- BTC reserve value
- $0.18M
- BTC units
- 5.8 BTC
- Protocol AVAX
- 30K
- POV share
- 0.015%
- 10-yr deployment
- $23.50M
- BTC reserve value
- $1.13M
- BTC units
- 34.4 BTC
- Protocol AVAX
- 201K
- POV share
- 0.100%
- 10-yr deployment
- $51.06M
- BTC reserve value
- $2.90M
- BTC units
- 89.0 BTC
- Protocol AVAX
- 784K
- POV share
- 0.390%
The Base case begins with only $1.0M of seed operating capital. Across the median path, it supports about $23.5M of cumulative Bitcoin-security deployment, ends with roughly 34 BTC in the treasury, and accumulates about 201,000 AVAX of Protocol-Owned Validation through modeled bond spread and compounding.
Dispersion matters — published interquartile ranges
The treasury run publishes IQRs for deployment and BTC reserve value only, and only for Base and Strategic. There is no re-run Pilot range, and no re-run hashpower or network-share distribution.
§10.1 — Policy scenarios
| Scenario | Seed | Participation | Reward bonded | Bond spread | BTC LTV | Turnover | Utilization |
|---|---|---|---|---|---|---|---|
| Pilot | $0.5M | 5% → 25% | 5% | 3% | 10% | 2× / year | 50% |
| Base | $1.0M | 10% → 50% | 10% | 5% | 15% | 4× / year | 70% |
| Strategic | $2.0M | 10% → 75% | 20% | 7% | 20% | 4× / year | 75% |
Appendix A.7 of the v4 document reprints the percentile table from the earlier credit-first design without re-running it against the treasury model. Its figures do not reconcile with §10.3: A.7 puts the Base-case median 10-year deployment at $61.1M where §10.3 puts it at $23.50M. The treasury figures above are authoritative. This table is shown because it is the only published source of hashpower and network-share dispersion, and it should be re-run before any implementation decision.
Model assumptions
- Paths
- 10,000 independent quarterly paths
- Horizon
- 40 quarters — Aug 2026 → Aug 2036
- Seed
- 42 (reproducible)
- Initial validator self-stake
- 201,886,319 AVAX [1]
- Initial displayed staking APY
- 6.7% [1]
- Starting prices
- AVAX ≈ $6.54, BTC ≈ $65K — stochastic and highly volatile
- Staking APY
- declines 6.7% → 4.5% over ten years (modeling assumption)
- Operating profit
- positive profits retained as BTC; losses reduce the cash sleeve before any optional credit
- Protocol-owned AVAX
- bond spread is returned to validation and compounds its own rewards
- Optional credit
- limited by scenario LTV; contracts automatically when reserve value falls
- Net BSP margins
- stochastic around 2% Pilot, 4% Base, 5% Strategic — no permanent alpha assumed
- Principal
- validator and delegator principal excluded from every collateral calculation
What the simulation does not prove
- It does not prove profitable hashpower forever.
- It does not prove guaranteed BTC accumulation.
- It does not prove AVAX appreciation.
- It does not prove autonomous-agent alpha.
It tests whether a treasury-first system can acquire real reserves without making validator stake collateral.
§10.4 · What changed from the credit-first model
- Growth is slower at the beginning because BSP does not rent a large external balance sheet on day one.
- The tradeoff is ownership: the protocol accumulates BTC reserves and validating AVAX instead of paying away the core economics as financing spread.
- BTC appreciation can enlarge collateral capacity without selling the reserve; BTC drawdowns automatically reduce it.
- The bAVAX loop creates a separate AVAX sink: part of validator reward flow can become permanently protocol-owned validation rather than circulating reward supply.
- The system can survive with zero external credit. If credit markets disappear, BSP shrinks to its owned operating capital rather than becoming insolvent.
The proprietary loop
Seed capital → Bitcoin security work → BTC Reserve → optional BTC-backed working capital. In parallel: validator reward commitment → bAVAX → settled AVAX spread → Protocol-Owned Validation. The BTC side builds hard collateral. The AVAX side builds native security capacity.
This architecture changes the proposal from a financed mining strategy into an owned balance-sheet strategy. Hashpower is the external production engine; BTC is the reserve; bAVAX is the receivables instrument; validating AVAX is the native productive asset.
Ownership is the strategic advantage
A treasury-first BSP does not maximize day-one deployment. It maximizes survivability. The system can begin small, prove execution, retain BTC, and build a balance sheet that belongs to the protocol rather than to permanent outside lenders.
bAVAX is useful only if it remains boring
bAVAX converts a forecast reward stream into an explicit receivable with deterministic issuance limits. It should not rebase, promise unsustainable APY, or require perpetual new buyers. If the underlying reward asset is not there, new bAVAX cannot be created.
BTC becomes earned collateral
The first BTC in the treasury is more important than a larger theoretical credit line. Once BTC has been earned through actual Bitcoin-directed work, the treasury may keep it unencumbered or use a small portion as collateral. The protocol earns the right to leverage by first earning the collateral.
Protocol-Owned Validation compounds the other side
The AVAX retained through bAVAX bonding is not dead inventory. Returning it to validation creates a productive asset that secures Avalanche and earns future AVAX. BSP therefore compounds two reserves at once: external BTC and native validating AVAX.
Appendix A · Methodology
- Price processes
- BTC and AVAX modeled as correlated lognormal processes; drift and volatility are scenario parameters, not historical estimates. Volatilities are intentionally high to expose the proposal to long winters and violent recoveries.
- Hashrate & hashprice
- Stochastic log process partially correlated with BTC shocks. Gross hashprice is derived from modeled daily issuance plus fees divided by network hashrate, then converted to USD. [7]
- Halvings
- Subsidy follows the consensus schedule, approximated at the 2028, 2032, and 2036 boundaries. [7]
- Validator economics
- APY declines 6.7% → 4.5% over the decade; half of validator rewards are modeled as recompounded — an assumption reflecting the capability ACP-236 introduces, not a prediction of behavior. [3]
- Hashpower conversion
- Deployment is converted to gross hashpower-economic equivalent using modeled USD hashprice and a stochastic procurement cost factor centered on a 7% premium. “Financed EH/s” is a capacity proxy, not delivered pool hashrate.
- No AI alpha
- The headline model deliberately does not require persistent AI-generated trading alpha. Strategy alpha, miner-credit spreads, distressed financing, hedging, and pool-routing gains should be measured in pilots and added only after evidence exists.
§13 · Roadmap
Ambitious in vision. Boring in execution.
Learn how to deploy $100,000 intelligently before asking how to deploy $100 million.
Phase 0
90-day falsification sprint
Rebuild the treasury/BSP model with Foundation economists; publish assumptions, code, reserve-coverage rules, and falsification criteria.
Interview validators, miners, pools, hashpower markets, custodians, ASIC-finance providers, bond-market specialists, and BTC-collateral lenders.
Define the legal perimeter for custody, bAVAX issuance, lending, derivatives, sanctions screening, and miner counterparties.
Write the architecture for a voluntary off-consensus BSP Treasury tied to settled validator rewards and a fixed-maturity bAVAX test instrument.
Specify BTC reserve accounting, bond haircuts, coverage floors, Protocol-Owned Validation, oracle design, Hashwork Receipts, and failure behavior.
Decide whether the thesis survives. If not, publish why.
§14 · ACP path
Avalanche's ACP framework defines Standards Track proposals as changes to the design or function of the Avalanche Network. [9] BSP should not begin there. It should begin as a public research discussion and voluntary implementation, because the mechanism involves economics and external counterparties that must be tested before protocol-native integration.
A future ACP would likely specify:
- new reward-routing semantics at staking-cycle settlement
- validator BSP commitment configuration
- accounting and authorization rules
- network-level and validator-level risk parameters
- backwards compatibility and grandfathering
- reference implementation hooks for settlement vaults
- telemetry and audit requirements
- a complete guarantee that BSP failure cannot impair Avalanche consensus
§15 · Bring me into the room
Do not accept this idea on faith. Give me the chance to try to kill it with you.
Presentation video
Reserved for the walkthrough. Drop the file at /public/upgradeavax/ and set VIDEO.src in content.ts.
The ask
Create a Foundation / Ava Labs working group for Bitcoin Security Participation, and bring Relic on as a paid strategic contributor or research lead for the workstream.
Fund and staff a 90-day BSP falsification sprint with a mandate to falsify, prototype, and — if it survives — ship the mechanism. At day 90, make a binary decision: stop and publish why, or fund the Fuji pilot and begin the ACP path.
Put me beside the economics team, P-Chain and AvalancheGo engineers, validator operators, mining-market specialists, and counsel. I would rather discover a fatal flaw in week two than defend a beautiful idea that cannot survive reality.
§12 · The vehicle in the water
You do not build the boat after the wave reaches you.
Bitcoin's next expansion may come from price, sovereign accumulation, institutional credit, transaction-fee markets, energy-grid integration, miner consolidation, new hashpower derivatives, or something we do not yet see. The exact wave is unknowable. The capability to participate is knowable.
Winter will come again. The question is whether Avalanche enters it depending on summer — or carrying its own heat.
Sources
References
Market values and network statistics are time-sensitive snapshots. All model outputs should be rerun with current data before any implementation decision.
- [1]Avalanche — “Validators”
Accessed August 8, 2026. Total stake, validator stake, delegated stake, staking validators, APY, and no-slashing description.
- [2]Avalanche Foundation — Economic Research Agenda
July 30, 2026. The measure / capture / distribute framework and the AVAX value-accrual agenda.
- [3]Avalanche Builder Hub — AVAX Staking for Professionals
Fixed-term reward timing and ACP-236 Auto-Renewed Staking, activated on Fuji July 28, 2026; Mainnet activation not yet scheduled.
- [4]Avalanche Builder Hub — ACP-77: Reinventing Subnets
Independent Avalanche L1 validator management and the Validator Manager model.
- [5]Avalanche Builder Hub — AVAX Token
AVAX utility, staking, fee burning, and capped supply up to 720M AVAX.
- [6]Hashrate Index — Bitcoin Hashprice Index
Accessed August 8, 2026. Spot hashprice ≈ $32.58/PH/s/day; 7-day network hashrate ≈ 929.16 EH/s.
- [7]Bitcoin.org / Bitcoin Developer Reference
Mining, hash rate, block rewards, and the subsidy halving every 210,000 blocks.
- [8]Hashrate Index Roundup (August 3, 2026)
Current mining conditions, fees, hashrate, hashprice, and six-month forward hashprice.
- [9]Avalanche Builder Hub — Avalanche Community Proposals (ACPs)
Standards Track ACP definition and current proposal index.
- [10]Crypto.com — Avalanche price page
August 8, 2026 snapshot used only for current-value arithmetic; the Monte Carlo starts at ≈ $6.55.
- [B1]Space Exploration Technologies Corp. — public filing describing Terafab
2026. Describes Terafab and its one-terawatt annual compute-hardware goal. Cited in §9.2; no URL is given in the source document.
- [B2]SpaceX / Tesla / Intel public materials on Terafab
Vertically integrated logic, memory, packaging and test ambitions. Cited in §9.2; no URL is given in the source document.
Research proposal only. Not investment, legal, tax, or financial advice.
Download the full proposal