Release on BXM.net

BXM 0.1.0 Launches With Canon and Memo, Two Open Source Tools for Repeatable Results

Thu, 22 Oct 2026 00:00:00 +0000

BXM 0.1.0 is out. It’s two small command-line tools in one repository, open source under the Apache License 2.0, with builds for Linux, macOS and Windows.

They share one idea. Same input, same bytes, same result. Canon applies it to data and Memo applies it to work.

BXM Canon is a binary encoding with exactly one valid form for every value. Two programs that encode the same data get the same bytes, whatever order they wrote the keys in and however they spelled the numbers. A hash or a signature taken on one machine holds on every other. The decoder refuses any byte string that isn’t the one encoding of its value, so a second spelling can’t sneak in through the back door.

BXM Canon 0.2.0 Brings the Same Bytes to JavaScript With One Rust Core Compiled to WebAssembly

Thu, 22 Oct 2026 00:00:00 +0000

BXM Canon 0.2.0 adds a JavaScript package. It runs in Node 18 and later and in browsers, and it gives exactly the bytes and hashes the bxm-canon command gives, because it is the same Rust code compiled to WebAssembly.

That matters more for Canon than for most libraries. A canonical encoding is only as good as the agreement between the programs that use it. If the Node service and the Go service each carry their own implementation, a single corner case they read differently, a float spelled one way or a key compared another, brings back the problem Canon exists to remove.

BXM Canon 0.3.0 Adds Python, With Ints, Floats and Bytes Kept Apart and the Same Hash as Every Other Build

Thu, 22 Oct 2026 00:00:00 +0000

BXM Canon 0.3.0 adds a Python package. It’s the same Rust core again, this time called through PyO3, with wheels for Linux, macOS and Windows and any Python from 3.9 up. A value hashed in Python gives the hash the command line, the C library and the JavaScript package give, because all of them run the same code.

Python turned out to be the most natural fit so far. JavaScript has one number type, so a JavaScript caller has to think about whether 1 should be an integer or a float. Python already keeps int and float apart, and it has a real bytes type, which is exactly what Canon distinguishes. So the Python package can take a value straight from your program, no text step in between.