Bitquant: Bitcoin, keys and the next signature

Bitcoin made verification part of everyday language: blocks, hashes, public keys, signatures. The quantum question adds a new layer to that vocabulary. How do we reason about records when the assumptions behind a signature can change? Bitquant turns that question into a small terminal you can operate. Read a public block. Prepare a simulated qubit. Sign a record. Alter it. Verify again.

The ambition is to make a complex conversation tangible. A terminal gives each idea an action and each action a visible result. You can follow the chain reference, move a state vector and challenge a signature without connecting a wallet. The experience begins with curiosity and rewards attention: what exactly was observed, what was signed, and what did verification actually establish?

Bitcoin’s BIP340 specifies Schnorr signatures over secp256k1 (https://github.com/bitcoin/bips/blob/master/bip-0340.mediawiki). Chaincode’s 2025 report, Bitcoin and Quantum Computing: Current Status and Future Directions, examines quantum risk, signature proposals and migration questions (https://chaincode.com/bitcoin-post-quantum.pdf). These references frame a serious engineering conversation involving cryptography, protocol choices and coordination across an ecosystem. Bitquant offers a place to explore a few of its underlying ideas.

The Bitcoin view starts with a command you choose. It requests a public mainnet block snapshot from mempool.space and displays its height, hash, timestamp and transaction count. The fetch time stays visible, and you can inspect the block in the explorer. Each sync requests one snapshot. There is no continuous feed or independent chain validation. That boundary makes the source and freshness of the observation easy to read.

The Quantum view opens a one-qubit experiment. Adjust θ and φ, watch the projected Bloch sphere, apply H, X or Z, then measure the state. Amplitudes, probabilities and sample counts make the changes visible. Try H, then Z, then H from the initial state to explore how phase affects the result through interference. This runs as a classical simulation in your browser. IBM’s Bloch sphere lesson provides the geometric reference (https://quantum.cloud.ibm.com/learning/en/courses/general-formulation-of-quantum-information/density-matrices/bloch-sphere).

The Proof view uses ML-DSA-65 to sign and verify a local snapshot of the model’s assumptions and results. A fresh temporary key is generated for the operation. Then the tamper command changes one byte and checks the original signature against the altered record. The unchanged record verifies; the altered record is rejected. The experience puts record integrity into a sequence you can repeat: create, sign, change, check.

ML-DSA is specified in NIST’s FIPS 204, published in August 2024 (https://csrc.nist.gov/pubs/fips/204/final). Bitquant references that standard for its local signature demonstration. A successful demo verifies the relationship between its public key, signature and record bytes. It does not establish a real-world issuer’s identity or provide security for Bitcoin, WBTC, a wallet or a token. Bitcoin’s protocol and this local experiment remain separate.

Another thread is a proposed WBTC pairing on Solana. Pump’s published Supported Pair Assets list includes WBTC represented through Wormhole Portal (https://pump.fun/docs/custom-pairs). Bitquant is exploring that pairing; no Bitquant token has been launched, no reward vault is configured, and no distributions have occurred. The Pairing view uses editable assumptions to show arithmetic examples. Its figures are hypothetical and do not forecast payouts.

Bitquant was built using OpenAI Codex and is an independent project. OpenAI is a construction-tool reference; NIST and the other cited organizations provide source material. No affiliation, sponsorship, endorsement or audit of Bitquant is claimed. The current product is an invitation to inspect, experiment and ask better questions about the next signature.

Observe the chain. Question the keys. Test the next kind of proof.
