The release that meets you where you are.
BTX v0.33.1 and the browser wallet.
Every technology has a moment when it stops asking people to come to it, and starts going to where people already are. Email had it when it left the terminal for the browser. Banking had it when the branch became an app. BTX v0.33.1 is that release: the project's most advanced cryptography — digital signatures designed to survive quantum computers — compiled down to something that runs in an ordinary browser tab.
No node to sync. No command line. No installation ceremony. And, crucially, no compromise on who holds the keys. This is one of those releases where the engineering choices are the values, and you can read them like a balance sheet.
Whyte Consolidated Research · 2026-07-11· 9 min read · On BTX v0.33.1
Don't lower the standard. Move it.
Here is an uncomfortable truth about self-custody, the idea that you — not an exchange, not a custodian — hold your own assets: most people never do it, because the tooling asks too much.Running a full node is like being asked to operate your own bank vault, plumbing included. It's the gold standard for sovereignty, and it's a non-starter for a CFO who just needs to receive, hold, and verify.
The industry's usual answer is to shrug and hand users to a custodian. Convenient, familiar — and it quietly reintroduces the exact counterparty risk the technology was built to remove. Every few years the market relearns, expensively, what “not your keys” means.
BTX's answer in v0.33.1 is different: don't lower the standard, moveit. Take the node's own signing cryptography — bit-for-bit the same — and deliver it to the browser, so the easy path and the sovereign path become the same path.
The same cryptography, wearing different clothes.
BTX signs transactions with post-quantum signature schemes — ML-DSA-44 and SLH-DSA-SHAKE-128s, algorithms from the family standardized by NIST after a years-long global competition. In plain terms: the math is chosen so that even a future quantum computer, the kind that would unravel today's conventional signatures, gets no purchase. Most chains treat this as a someday problem. BTX treats it as a launch requirement.
Until now, that cryptography lived in the native node — compiled C, running on servers and workstations. What v0.33.1 ships is a WebAssembly build of that same library: btx-pqc.wasm, a portable module that browsers, web workers, and Node.js can all execute at near-native speed. Key generation, signing, verification — the full custody toolkit, in an environment that requires nothing but a URL.
And here's the line in the release notes worth framing: the project's CI generates keys from identical entropy in both the native node and the WASM build, and verifies the results match. The browser wallet isn't a lookalike of the node's cryptography. It is provably, byte-for-byte, the same cryptography wearing different clothes.
- ✓Key generation, signing, and verification — the full custody toolkit.
- ✓Runs in browsers, web workers, and Node.js at near-native speed.
- ✓The node's own signature library, compiled — not a reimplementation.
- ✓CI-verified: identical entropy produces identical keys in native and WASM builds.
- ✕Never reaches for the operating system's entropy — randomness comes only from the caller.
- ✕Filesystem access compiled out entirely — it structurally cannot touch your disk.
- ✕No network calls of its own — it signs what it is given, nothing more.
- ✕Not a custodian — keys live with the user, in the tab, full stop.
The discipline shows in the refusals. The browser build takes randomness only from the caller — it never reaches for the operating system's entropy on its own — and its filesystem access is compiled out entirely. That's not a limitation; it's the custody model enforced at build time. A signing module that can'ttouch your disk is a module you don't have to trust not to.
The easy on-ramp has no lock-in.
A browser wallet alone is a nice demo. What makes v0.33.1 a serious piece of financial infrastructure is the bridge in the other direction. Your browser wallet can export itself as a .btxwallet file — a small, human-inspectable JSON bundle holding the post-quantum master seed and the public descriptors that define your addresses. And as of this release, the native node treats that file as a first-class citizen.
| Aspect | Mechanism | Note |
|---|---|---|
| Format | .btxwallet | small, human-inspectable JSON bundle |
| Contents | seed + descriptors | post-quantum master seed and public address descriptors |
| Browser → node, fresh | restorewalletbundle | one RPC rebuilds the entire browser wallet in a full node |
| Browser → node, merge | importwalletbundle | folds the bundle into a wallet you already run |
| Node → browser | export bundle | the reverse road exists — a node wallet exports browser-compatible |
| Handling | key, not backup | plaintext seed — offline, briefly, then deleted; encrypted archives for routine backups |
| Check | Status | Why it matters |
|---|---|---|
| Format & version | checked | malformed or future-versioned bundles are rejected |
| Network | checked | a testnet bundle can't land in a mainnet wallet |
| Derivation structure | checked | the address tree must match what the browser wallet declares |
| First receive address | re-derived | the node independently derives it and confirms the match |
Trust, then verify, then verify again: before installing anything the node checks the bundle's format, version, network, and derivation structure — and independently re-derives your first receive address to confirm it matches.
Why does this matter to a business reader? Because it means the easy on-ramp has no lock-in.Start in the browser on day one. When your holdings, your compliance posture, or your paranoia grow, graduate to a full node — and your wallet comes with you, cryptographically intact, no custodian's permission required. The exit is guaranteed by the protocol's own tooling, not by a vendor's goodwill. In an industry where “exportable” usually means a support ticket and a prayer, that's a structural promise.
One caveat, made with admirable bluntness in the release notes: a .btxwallet file contains your master seed in plaintext. It is a key, not a backup format.Handle it like the crown jewels — offline, briefly, then deleted — and use the node's encrypted archive format for routine backups. Unvarnished warnings like this one are a trust signal: projects confident in their architecture document their sharp edges; projects that aren't, bury them.
The official binaries now speak fluent enterprise.
There's a one-line change in this release that institutional builders will appreciate: published btxd binaries now ship with ZMQ notifications enabled. If that's alphabet soup — ZMQ is the event stream a node can emit the instant a block or transaction lands, and it's how exchanges, payment processors, and monitoring systems build real-time integrations. Previously you had to compile the node yourself to get it. Now the official, signed binaries carry it out of the box. It's the difference between a product that tolerates integration and one that invites it.
And for the operations-minded: v0.33.1 changes no consensus rules and touches no wire formats. Upgrading is uneventful by design — back up your wallets, stop the node cleanly, wait for it to exit, install the signed release binaries, restart. The best infrastructure upgrades are the boring ones.
Read the point releases. That's where values live.
We've written before about BTX's grand ideas — proof-of-work that performs verified, useful matrix computation; a chain that doubles as a market for physical infrastructure. Grand ideas attract attention. But if you want to know whether a project deserves your confidence, read its point releases. That's where values live, because nobody's watching.
Read this one and you find: quantum-resistant cryptography brought to the least technical user without dilution.A build that structurally cannot exfiltrate what it never touches. CI that proves the browser and the node share one cryptographic truth. An escape hatch from easy mode to sovereign mode, verified at import. A sharp edge documented in plain language. And an enterprise event stream turned on because integrators shouldn't have to compile trust from source.
None of it is flashy. All of it is the same sentence, said six ways: your keys, your exit, your proof.
The barrier didn't come down with a press release. It came down the way real barriers do — one careful point release at a time, until one day you open a browser tab and the vault is simply there, and it answers only to you.
BTX v0.33.1 and the browser wallet — questions
- What ships in BTX v0.33.1?
- Three things: a WebAssembly build of the node's post-quantum signature library (btx-pqc.wasm) that runs in browsers, web workers, and Node.js; a browser-to-node wallet bridge — .btxwallet export from the browser, restorewalletbundle and importwalletbundle RPCs on the node, plus export in the reverse direction; and published btxd binaries with ZMQ notifications enabled. No consensus rules or wire formats change.
- Is the browser wallet's cryptography weaker than the node's?
- No — it is the same cryptography. btx-pqc.wasm is a WebAssembly compile of the node's own post-quantum signing library (ML-DSA-44 and SLH-DSA-SHAKE-128s), and the project's CI generates keys from identical entropy in both the native node and the WASM build and verifies the results match byte for byte. The browser wallet is not a lookalike; it is provably the same cryptography in a different runtime.
- What are ML-DSA-44 and SLH-DSA-SHAKE-128s?
- Post-quantum digital signature schemes from the family standardized by NIST after a years-long global competition. They are chosen so that even a future quantum computer — the kind that would break today's conventional elliptic-curve signatures — gets no purchase. BTX signs transactions with them from genesis rather than treating quantum resistance as a someday upgrade.
- How do I move a browser wallet into a full node?
- Export the browser wallet as a .btxwallet file — a small, human-inspectable JSON bundle holding the post-quantum master seed and public descriptors — then call the node's restorewalletbundle RPC to rebuild it as a full node wallet, or importwalletbundle to merge it into a wallet you already run. Before installing any key material the node verifies the format, version, network, and derivation structure, and independently re-derives your first receive address to check it matches.
- Is a .btxwallet file a backup?
- No. A .btxwallet file contains your master seed in plaintext — it is a key, not a backup format. Handle it offline, briefly, then delete it, and use the node's encrypted archive format for routine backups. The release notes make this caveat explicitly, which is exactly the kind of sharp-edge documentation you want from custody software.
- Why does the WASM build refuse to read OS entropy or the filesystem?
- It's the custody model enforced at build time. The browser build takes randomness only from the caller and has its filesystem access compiled out entirely, so a signing module that structurally cannot touch your disk is a module you don't have to trust not to. Constraints like these are guarantees, not limitations.
- What does enabling ZMQ in the published binaries change?
- ZMQ is the event stream a node emits the instant a block or transaction lands — the mechanism exchanges, payment processors, and monitoring systems use for real-time integration. Previously you had to compile btxd yourself to get it; as of v0.33.1 the official signed binaries ship with it enabled, so integrators get enterprise-grade eventing out of the box.
- What do node operators need to do to upgrade?
- v0.33.1 changes no consensus rules and touches no wire formats, so the upgrade is uneventful by design: back up your wallets, stop the node cleanly, wait for it to exit, install the signed release binaries, and restart.
BTX v0.33.1 releases at github.com/btxchain/btx/releases — install only the signed, published artifacts. Node operators: back up wallets, shut down cleanly, replace binaries, restart; the release changes no consensus rules and no wire formats. The browser-to-node recovery flow is documented in doc/btxwallet-browser-node-interop.md in the repository.
- BTX — v0.33.1 release artifacts (signed)
- BTX — bug reports and issues
- btx.dev — project site and release notifications
- Whyte Consolidated — BTX: when the block reward is a matrix multiply
- Whyte Consolidated — One rail, no seams: BTX and the post-quantum money stack
- Whyte Consolidated — Tokenizing assets on BTX: settlement that outlives the asset
- Whyte Consolidated — When your bank becomes a datacenter
For informational purposes only. Not financial, investment, or legal advice. Self-custody carries operational risk: a lost seed or a mishandled wallet bundle is unrecoverable by design, and a .btxwallet file contains an unencrypted master seed that must be handled accordingly. Install only signed, published release artifacts, and verify signatures before running them. Software behavior described here reflects the v0.33.1 release notes at time of writing and may change in later releases.