BXM Canon gives every value exactly one binary encoding, so hashes and signatures never depend on who wrote the bytes. BXM Memo skips a command when its inputs have not changed and says why when they have.
2,000,000
Random and damaged byte strings fed to the Canon decoder, with none accepted in a second form
60
Conformance vectors in the Canon spec, for anyone writing another implementation
61 ms
Memo restoring 200 files from cache, for a step that took 2.6 s to run
16
Processes sharing one Memo cache at once, every one with the right result
Measured on a 2-CPU Linux machine with BXM 0.1.0. The test output is in test/results in the repository.
release
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 …
explainer
Here’s a bug that shows up in almost every system that signs or hashes structured data. Service A builds a record, serializes it as JSON, hashes it and signs the …
explainer
Watch a CI log for a week and count the steps that produced exactly the same output as last time. Code generation from schemas that didn’t change. Image resizing …
case study
Here’s a familiar review. The config for a checkout service comes back from someone’s editor and the diff is a wall of red and green. The editor saved with …
release
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 …
release
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 …
case study
Event pipelines get the same event twice. A producer times out, retries, and the retry goes through a different service that writes JSON its own way. The usual dedupe is …
testing
Each BXM tool makes one main promise. Canon promises that every value has exactly one encoding. Memo promises that it never hands you a wrong or half-restored output. …
case study
Most CI jobs build the same thing again and again. A docs fix or a typo in a README triggers the whole pipeline, and the release build runs as if the code had changed. …
Issues and pull requests are welcome on GitHub. For anything else, write to the project.