Skip to content

v9.35.0

@codenlighten codenlighten tagged this 14 Oct 12:00
PUBLISHED to npm 2026-10-14. This commit is the PUBLISHED tree, reproduced from a fresh clone
of it before publishing:

  shasum     fbfa8dcca5e1d903337d8fb4ed7fb40d03d95a65
  integrity  sha512-ep7LYZze9g6ye[...]Q3sdsjg0J9zJw==
  files      284
  node       v22.23.3

git status was empty in the clone after build-all, so the committed bundles reproduce too.

THE TAG WAS MOVED, deliberately, from d26b74b to here before publishing. d26b74b carried a
CHANGELOG claim that two implementations' flag words had been confirmed against each other;
they are not comparable (ours numbers that set 0x3d586f, the reference 0x3d406f), and the
correction is in this tree. lib/, the bundles and bsv.d.ts are byte-identical between the two
commits — only CHANGELOG.md, one doc and one test file differ — so no published code changed,
but the CHANGELOG ships inside the tarball and a tag pointing at a tree that is not what was
published is the failure this project has already paid for once.

All 22 node-judged rows agree. 452-case conformance corpus unchanged. 5536 passing.
Assets 2
Loading