# Bitrax: a closer reading of Bitcoin

Public keys. Real blocks. Verifiable proofs.

## Begin with the record

Bitcoin leaves a public record, but reading that record requires care. An address, a public key, a transaction and a block are related pieces of information. They are not interchangeable. Bitrax is an independent research observatory built around that distinction: inspect what is visible, reconstruct what can be checked, and keep the limits beside the result.

The terminal brings three instruments into one workspace: an address inspector, a transaction-inclusion proof engine, and a reading desk for quantum research. Each has a specific job. Together, they make a technical question easier to examine without turning an observation into a promise.

## Inspect the script

The address inspector starts by checking a Bitcoin mainnet address and its checksum. It then requests public records, samples up to 25 recent transactions, and examines up to 12 unspent outputs. If the provider limits the output list, the report identifies its fallback and reduced coverage. This is a bounded investigation, not a complete scan of every possible exposure.

The distinction between output types matters. A standard key-hash output contains a commitment to a public key; a matching key may appear when funds are spent. A Taproot output contains a public output key. The latter structure is specified in [BIP 341](https://bips.dev/341/). Bitrax reports these observable differences. A visible key does not establish an active attack, and a key absent from the sample does not establish quantum resistance. Earlier transactions, other addresses and off-chain disclosures remain outside the inspection.

## Rebuild the proof

The proof engine asks a narrower question: does this transaction ID lead to the Merkle root committed in the fetched block header? It retrieves the public proof and header, then recomputes the SHA-256d path locally in the browser. The result includes the intermediate hashes and a downloadable report.

This check has a clear boundary. It verifies inclusion against that header and checks the header hash against the reported block hash. It does not independently validate cumulative proof of work, the entire chain or every consensus rule. The local alteration demonstration changes the transaction ID to show a mismatch; it broadcasts nothing.

## Keep research in context

The research desk links directly to protocol proposals and cryptographic standards. Their status is part of the reading. [BIP 360](https://bips.dev/360/) is a draft proposal for Pay-to-Merkle-Root, while [NIST FIPS 204](https://csrc.nist.gov/pubs/fips/204/final) specifies the ML-DSA digital-signature standard. A published standard and a Bitcoin proposal are different things; neither means Bitrax has upgraded Bitcoin or protected a wallet.

Public block observations refresh every 60 seconds while the page is visible. Providers can be delayed or rate limited, so timestamps and error states matter. No wallet connection or private key is required. Bitrax does not sign transactions, hold funds or execute trades.

The aim is a useful research habit: start with a precise question, inspect the evidence, and describe exactly what the evidence supports. With Bitcoin and quantum research, a smaller claim that can be checked is more valuable than a large claim that cannot.

---

Research-document status checked on 17 October 2026. Open the linked primary documents for current text and status.