May 29, 2026
Zero starts drama again
Bijou64: A variable-length integer encoding
A tiny number trick fixed a security headache — and sparked a nerd fight over whether it’s genius or overkill
TLDR: Bijou64 is a new way to store numbers that was built to stop subtle security mistakes and unexpectedly came out faster too. Commenters are split between calling it a smart cleanup of an old annoyance and wondering why anyone needed this much effort to stop weird edge-case number formats in the first place.
A humble little way of writing numbers has somehow turned into the internet’s latest micro-drama. The team behind Bijou64 says they built it to solve a sneaky security problem: with older number formats, the same number can be written in multiple byte patterns, which is bad news when signatures and trust are on the line. Their new approach makes each number have one and only one valid form — and, plot twist, it also ended up being faster.
That should have been an easy win, right? Absolutely not. In the comments, one camp basically yelled, “Why are we making this so complicated just to stop zero from dressing up in fake mustaches?” RedShift1 called it “quite convoluted,” capturing the vibe of readers who think this is a lot of machinery for a very niche edge case. But the fans came in hot too. One commenter said it looks “so much nicer” than the old standard for many real-world uses, praising the cleaner design even while admitting there’s a tradeoff in file size.
Then came the confused-comedian energy. Willtemperley was openly baffled about why an encoder would ever create the weird padded forms the old system allows, basically asking the digital equivalent of, “Who is out here doing this, and why?” Another commenter calmly translated the whole thing into simpler terms, while a practical engineer shrugged and said if speed matters and size doesn’t, maybe just use fixed-size numbers and move on. Classic comment-section split: elegant breakthrough, needless complexity, or just another Tuesday on Hacker News.
Key Points
- •The article introduces bijou64 as a varint encoding built for the Subduction CRDT sync protocol.
- •bijou64 was designed to ensure that each integer has exactly one valid representation, addressing a signature-verification problem.
- •The article says bijou64 also turned out to be several times faster than LEB128.
- •LEB128 is described as allowing multiple byte encodings for the same value, including zero, unless canonical forms are explicitly enforced.
- •The article argues that embedding canonicality into the encoding format can prevent a class of security bugs that otherwise depend on decoder validation checks.