Ir al contenido principal
Actualización de consenso obligatoria Hard fork · bloque 185.000

Actualiza todos los nodos BTX a v0.33.2 antes del fork.

MatMul v4.7 Epoch A se activa en el bloque 185.000 de mainnet. Mineros, pools, validadores, bolsas, custodios, exploradores y operadores con código anterior no seguirán el consenso actualizado.

Bloques hasta el hard fork Consultando la altura de mainnet
4927 bloques restantes
Altura actual 180.073
Activación 185.000
Tiempo estimado ≈ 5d 03h 10m 30s

El fork depende de la altura, no del reloj. La estimación usa el objetivo de 90 segundos de BTX y se recalcula desde la altura en vivo. Actualiza, reinicia y confirma v0.33.2 antes del bloque 185.000.

AI Infrastructure Reserve Asset

Institutional framework for BTX reserves, compatible AI infrastructure, switching and step-in rights, valuation, controls, and risk disclosures, updated for MatMul v4.7.

Contexto compartido

Esta guía vive dentro de ambas rutas de BTX.

Las superficies de billetera y monitoreo importan tanto a operadores como a builders IA nativos. Vuelve al micrositio correspondiente para recuperar el contexto completo.

Institutional thesis

Own AI for the expansion. Own BTX for the contraction.

The AI infrastructure reserve-asset thesis treats BTX as a scarce monetary reserve whose security budget is tied to deterministic accelerator work. A complete implementation can combine three separately governed pieces: a BTX reserve, compatible compute infrastructure, and contractual switching, step-in, or collateral-control rights. Holding BTX alone does not create rights to a data center, and owning compatible hardware alone does not create a monetary hedge.

This is a strategic risk framework, not a claim of guaranteed daily inverse correlation to AI equities, GPU prices, data-center rents, or credit spreads. It is designed to complement conventional instruments such as puts, credit protection, insurance, power hedges, liquidity reserves, and government securities.

Technical basis as of 5 August 2026

v0.33.2 is the current published node release, built from commit b4671ec28bb24e2fcbdd8252576119d54fd95238. Mainnet stays on MatMul v3 below height 185,000 and changes atomically at that height to MatMul v4.7 Epoch A: Profile 1 Resident Curriculum with complete, deterministic ExactReplay. Testnet and signet do not activate this boundary.

Current release factInstitutional interpretation
4 sequential rounds; 16 FFN layers per roundA serial, transformer-shaped exact-integer workload rather than a conventional hash loop
4,096 consensus MatMul dimension; batch-sequence 16,384Epoch A establishes accelerator affinity without claiming the deferred Profile-2 workload is live
141,149,805,215,744 exact MACs per episodeEvery claimed Epoch-A block is replayed in full before its chainwork is authenticated
182-byte digest-only headerNo proof or witness expansion enters the Epoch-A block header
Qualified CUDA and Metal strict-device pathsProduction operation requires self-qualification and zero CPU GEMM fallback
Profile 2, Coupled-V3, Stage-3 proof authority disabledThe larger data-center workload remains a future, height-versioned roadmap item—not current consensus

Read the complete MatMul v4.7 specification and legacy context before using the technical premise in an investment, lending, insurance, or infrastructure document.

Three distinct hedge channels

ChannelMechanismWhat must existPrimary failure mode
Monetary reserve A scarce, liquid reserve outside a single compute lease, borrower, or hardware vendor Custodied BTX, liquidity policy, limits, and rebalancing rules Basis and liquidity risk: BTX may fall when the protected exposure falls
Operational switching option Underused compatible accelerators can be redirected from AI workloads to BTX validation/mining when economics and contracts permit Qualified hardware, software images, power/network capacity, rehearsed procedures, and explicit switching rights The equipment, power contract, software, or activation state may not support profitable switching
Collateral recovery A lender, insurer, or SPV can take control of compatible infrastructure and operate, lease, or sell it after a trigger Perfected security interest, access and step-in rights, operator, key custody, and an enforceable waterfall Legal control, technical readiness, or realized mining revenue may fail at the same time as the credit

These channels should be underwritten independently. Adding their notional values together without overlap, haircut, liquidity, and trigger analysis overstates protection.

Illustrative institutional structures

  • Reserve overlay: a governed BTX allocation alongside an AI-equity, private-credit, or infrastructure portfolio.
  • Data-center credit package: BTX reserve covenants plus lender step-in rights over qualified accelerators and operating accounts.
  • Capacity backstop: a pre-negotiated right to redirect idle capacity, subject to customer contracts and power economics.
  • Collateral-recovery SPV: equipment, access rights, operator agreements, and BTX flows placed under a bankruptcy-remote waterfall.
  • Fund or exchange-traded product: liquid BTX exposure, with no implied ownership of or claim on infrastructure unless separately documented.
  • Insurer or structured note: defined triggers and payouts referencing disclosed BTX and/or infrastructure values, with explicit basis-risk limits.
  • Sovereign, utility, or corporate reserve: a strategic allocation paired with energy, data-center, and custody policy.

Product labels do not create legal rights. Each structure needs instrument-specific advice on securities, commodities, banking, insurance, tax, accounting, sanctions, custody, insolvency, and energy regulation.

Valuation framework

A research model can decompose value into monetary scarcity, post-quantum security duration, network security and adoption, a contingent AI-capacity option, and market liquidity. The components are scenario inputs, not independently tradeable claims, and the result is a reference value—not an executable market price.

ComponentPossible evidenceRequired haircut
Monetary scarcitySupply schedule, custody, turnover, market depthVolatility, concentration, venue and liquidation capacity
Post-quantum durationLive transfer policy, wallet support, migration and recovery proceduresImplementation, adoption, and governance uncertainty
Network securityQualified capacity, distribution, chainwork, operator diversityActivation, centralization, outage, and adversarial stress
AI-capacity optionCompatible devices, switching rights, power, measured performance, operating playbookHardware obsolescence, availability, revenue, capex, opex, and time-to-switch
Liquidity/adoptionRegulated access, spreads, depth, borrow and settlement availabilityMarket fragmentation, legal restrictions, and stressed exit costs

Any use of BTX reference pricing should disclose its inputs, observation time, venue set, confidence level, and the difference between a model output and realizable proceeds.

Scenario analysis

ScenarioPotential contributionWhat can still go wrong
AI expansionPrimary AI assets participate; the BTX reserve may diversify monetary and network exposureReserve carry and opportunity cost can detract from returns
Utilization slowdownContracted switching may create an alternative demand path for compatible acceleratorsBTX economics may not cover power, staffing, and wear; customer restrictions may block switching
Borrower defaultStep-in and collateral rights can preserve equipment and operating optionalityPerfection, access, firmware, keys, interconnection, or operator continuity may fail
Crypto or BTX stressConventional AI assets and liquidity reserves may remain intactThe BTX leg can lose value independently of AI fundamentals
Joint systemic shockOnly diversified, legally separated layers may retain valueCorrelations can converge to one and all three hedge channels can impair together

Risks and controls

  • Basis risk: size the reserve from stress tests, not an assumed negative beta.
  • Liquidity risk: set venue, slippage, liquidation-time, and concentration limits.
  • Implementation risk: verify signed binaries, activation height, device qualification, and replay telemetry.
  • Hardware risk: inventory exact accelerator, memory, driver, runtime, power, cooling, and spare-part profiles.
  • Mining-economics risk: model difficulty, block rewards, fees, downtime, pool terms, power, and tax under downside cases.
  • Custody risk: separate reserve, treasury, attestation, and infrastructure-control keys; define recovery and succession.
  • Regulatory and accounting risk: obtain current jurisdiction-specific advice before launch and at each material change.
  • Governance risk: require independent limits, conflict controls, price sources, change management, and incident escalation.
  • Concentration risk: measure dependence on release maintainers, device vendors, signers, custodians, venues, utilities, and operators.

Investment-committee and infrastructure checklist

  1. State the protected exposure, loss mechanism, horizon, sizing rule, and maximum tolerable basis loss.
  2. Separate the BTX asset, infrastructure, and contractual rights in the legal and valuation schedules.
  3. Verify the exact v0.33.2 source commit, signed artifacts, chain, activation height, and node role.
  4. Prove device qualification and rehearse strict-device operations before treating switching capacity as available.
  5. If using trusted RPC mirrors, document that they are not independent MatMul validators and require an approved M-of-N signer policy.
  6. Perfect security interests and test physical, network, firmware, account, key, power, and data-center access after a simulated default.
  7. Define custody, valuation, margin, liquidity, rebalancing, insurance, tax, accounting, and regulatory owners.
  8. Run independent downside cases covering BTX drawdown, higher difficulty, lower rewards, device outage, power spikes, legal delay, and forced sale.
  9. Predefine exit, suspension, incident, fork, and governance-change triggers.
  10. Make every public claim traceable to current source, measured evidence, executed contracts, or clearly labeled assumptions.

Claims to avoid

  • “BTX is a guaranteed hedge against an AI crash.”
  • “Profile 2, Coupled-V3, or succinct proof authority is live in v0.33.2.”
  • “Any GPU can mine or validate MatMul v4.7 in production.”
  • “A trusted mirror independently validates BTX proof-of-work.”
  • “Holding BTX gives the holder rights to AI infrastructure or mining revenue.”
  • “A model/reference value is an executable price or guaranteed recovery value.”
  • “Post-quantum design eliminates implementation, custody, governance, or market risk.”

This page is institutional research and technical documentation, not an offer, solicitation, recommendation, fiduciary opinion, accounting conclusion, or legal, tax, insurance, or investment advice.