Knuth v0.80.0 is live. 🚀
Big one: the Bitcoin Cash VM and script interpreter are now
directly exposed through the C-API. Python, WASM, Node.js, C#,
any higher-level binding can now drive Script execution step by
step, straight from Knuth's core.
This is the foundation for the Knuth wallet and for dApp
development tooling, anything that needs to run, inspect or
debug Bitcoin Script from outside the node can now do it.
Plus: every chain, wallet and VM binding in the C-API has been
unified around consistent handles and lifetime contracts, so
language wrappers can rebuild cleanly without drift.
https://t.co/pWmnvXqVLL
#BitcoinCash #BCH #Knuth #WASM
🚀 Knuth v0.78.0 is out.
This release is all about the foundation for our upcoming BCH wallet:
🪙 Token-aware coin selection — new coin_selection module with UTXO selection that understands CashTokens.
🔧 Wallet utilities & C-API improvements — more building blocks for multi-language integrations.
⚡ Emscripten upgraded from 3.x to 5.0.3 — our WASM builds now use the latest emsdk, keeping the browser-side library up to date.
🔗 https://t.co/gZrhlqvbY6
#BitcoinCash #BCH #Knuth #WASM
Dev update :
Currently exploring full node infrastructure that will serve as the core data layer for RabbitExplorer. Experimenting with Knuth after previously working with BCHN and Chaingraph.
@KnuthNode@bch_1_official@bch
Great question.
They are functionally equivalent in terms of consensus behavior, but we don’t claim strict implementation-level identity.
The reason we keep both is basically risk management. In a consensus system, even very small differences can have serious consequences. Having the BCHN VM available, which is the same code as the reference implementation, gives a conservative path for users who want maximum assurance.
At the same time, the Knuth VM is built with a different goal in mind. It exposes much richer internals, things like detailed error reporting, execution tracing, stack inspection and metrics. That makes it much more suitable for debugging and building developer tooling, which is hard to achieve cleanly in the reference VM without major changes.
We’ve validated the Knuth VM quite extensively. We ported and adapted the BCHN script test suite, including more than 1,700 script vectors, 23K BigInt tests and VM limits tests. We also ran a full IBD from genesis to tip using the Knuth VM with no checkpoints, verifying every script, and got zero errors.
That gives us a high degree of confidence, but absolute equivalence is very hard to prove, especially because even the process of adapting tests can introduce subtle differences.
If we could guarantee perfect equivalence, we probably wouldn’t need two VMs. But in a consensus-critical system, we prefer to keep that safety net.
🚀 Knuth v0.77.0 is out — and this is a big one.
We just brought our native Script VM back to the frontier.
Knuth is the only Bitcoin Cash node with two VMs:
• A native VM built for developers
• The BCHN consensus VM (same code BCHN runs in production)
👉 Switch between them with a single build flag.
🧠 The upgrade:
Our native VM was way behind. Not anymore.
It now matches consensus rules through the May 2026 upgrade
(we call it Leibniz, BCHN calls it Upgrade 12).
And we didn’t just “update it” — we proved it:
• 1,700+ script test vectors
• 23K+ BigInt tests
• 165 VM limits tests
All ported, adapted, and cross-validated against BOTH VMs.
🔬 Why this actually matters:
This isn’t just another interpreter.
The Knuth VM is built like a real debugger for Bitcoin Script:
• Step-by-step execution
• Breakpoints on opcodes
• Full stack & alt-stack inspection
• Per-opcode error reporting
• Execution tracing through branches
• Metrics: sigchecks, hashes, op cost
👉 This is the kind of tooling Bitcoin Script never really had.
A foundation for debuggers, analyzers, and serious dev tooling.
🧪 Validation:
Full IBD. Genesis → tip.
✔ Knuth VM
✔ No checkpoints
✔ Every script verified
Result: zero errors
🛡️ Don’t trust it yet?
Perfect.
Run Knuth with the BCHN VM — and still get:
• Modern C++23 codebase
• Better networking
• UTXO-Z + improved DB architecture
• Real parallel block validation
(no global cs_main bottleneck 👀)
• Multi-language bindings (C, C#, Python, TS, JS, WASM)
💥 Scale of this release:
PR #188 touched 1,154 files
Yeah… we went all in.
🔗 Release:
https://t.co/zGyJ13YcRE
#Bitcoin #Cash #BCH #Knuth
UTXO-Z v0.3.0 released.
https://t.co/ZXOf8uyztF
Production-scale benchmarks.
Persistent metadata.
Correctness and regression tests.
Storage and sizing optimizations.
UTXO-Z is maturing as the next-generation UTXO DB.
Integration into Knuth is underway.
#Bitcoin#Cash#Scales
UTXO-Z v0.1.0 is now public.
https://t.co/wRhWbEJGna
Months of research are now real code.
This is an alpha release. The implementation and API will evolve.
Integration into the Knuth node is underway.
This is just the beginning.
#Bitcoin#Cash#Scales
Knuth JS-WASM v2.11.0 released
Updated to Knuth v0.75.0 core: faster deserialization, Merkle root optimizations, and continued cleanup toward a leaner, modern core.
Also migrated npm publishing to OIDC trusted publishing — no more token management.
📦 npm install @knuth/[email protected]
Release notes: https://t.co/uWiNHDsoD3
#BitcoinCash #BCH #WebAssembly #TypeScript
🚀 Knuth v0.75.0 released
This update continues the low-level performance and infrastructure work:
faster deserialization, Merkle root optimizations, experimental storage benchmarks, and more cleanup toward a leaner, modern core.
Part of the ongoing effort to reduce technical debt and prepare for what’s coming next.
Full changelog:
https://t.co/d4FOc2e1cm
#BitcoinCash #BCH #Knuth #Bitcoin #Cash
UTXO-Z development continues.
We’re focused on scaling UTXO validation with real data,
real workloads, and real performance gains.
More soon.
#Bitcoin#Cash#Scales
Sneak peek 👀
This is an early look at the new Knuth node interface planned for 2026.
Still work in progress, but the goal is clear: better visibility, better tooling, better UX for node operators and developers.
Curious what you think. Does this direction make sense?
#BitcoinCash #BCH #Knuth #FullNode #CryptoDev
Adding cores shouldn’t make your node slower.
UTXO-Z minimizes contention by design, so parallel lookups actually scale instead of fighting over locks.
That’s the difference between “multi-threaded” and built for concurrency.
#Bitcoin#Cash#Scales
UTXO databases don’t need to be “general”.
They need to do only three things extremely well:
• lookup
• insert
• delete
UTXO-Z is built around exactly these operations — nothing more, nothing less.
That focus is what unlocks massive throughput and real scalability.
33M UTXO lookups/sec didn’t happen by accident.
Most UTXOs are spent shortly after creation, temporal locality dominates real blockchain workloads.
UTXO-Z is built around that reality: fast, parallel access to recent UTXOs, without slowing down on older data.
Scaling Bitcoin Cash is not about blocks or bandwidth.
The real bottleneck is the UTXO database.
With domain-specific data structures (not general-purpose DBs), UTXO-Z achieves:
• Up to 33M UTXO lookups/sec
• ~45× faster than general-purpose databases
...
Knuth JS-WASM v2.10.0 released
Updated to Knuth v0.74.0 core, which includes modernized encoding APIs, improved endian functions using C++23, and continued
cleanup of legacy code dating back to 2011.
📦 npm install @knuth/[email protected]
Release notes: https://t.co/OoDMMmJQbk
#BitcoinCash #BCH #WebAssembly #TypeScript