@smartledger/bsv 9.25.0 → 9.26.1

package/CHANGELOG.md

@@ -7,6 +7,93 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [9.26.1] - 2026-10-07
+
+### Fixed — relabelling a certificate as legacy bypassed the seal refusal
+
+`version` is not signed. The proof hash begins with the fixed bytes `"NotaryHash/1.0"` and `u8(1)`
+whatever the JSON member says, so **anyone could set `version: 1` on a current sealed certificate**
+and a forged seal verified as `valid` again — the refusal added in 9.25.0 was optional for an
+attacker. Found by the block-penn-station session's rerun about half an hour after it shipped.
+
+The mechanism, which is the part worth keeping:
+
+- `Certificate.normalize` rebuilds a **legacy** anchor from a fixed key set — `type`, `network`,
+  `txid`, `vout`, `blockHeight`, `blockTime` — and therefore **drops `anchor.seal`**;
+- `NotaryHash.verify` normalizes on the line after it records `report.legacy`, **shadowing its own
+  parameter**, so every downstream check — including `verifyAnchorSPV`'s own seal check — reads
+  normalized input whether it knows it or not;
+- so the seal check could not see a seal on a legacy certificate, and the legacy path kept the
+  height, time and format checks while silently losing this one.
+
+`anchor.seal` is now captured **before** the translation and the verdict accounts for it, so the
+refusal holds on both paths. A genuine legacy certificate — one with no seal — verifies unchanged,
+and `allowUncheckedSeal` works on both paths.
+
+**The general rule, now in the source:** *a refusal that exists only on one normalization path is
+optional whenever the caller can choose the path.* Anything under `anchor` outside that fixed key
+set is in the same position and must be checked before translation.
+
+### And a correction to 9.26.0's release notes
+
+9.26.0 said `version: 1` needed no change because it is the documented 8.3.0–9.8.0 marker. The
+first half stands — reading it is deliberate, and `verify` reports `legacy: true`. The conclusion
+did not: an unsigned discriminator that selects a *weaker* code path is a security boundary, not a
+compatibility detail, and I had checked that the legacy path was intentional without checking that
+it was equally strict.
+
+9.26.0's replay of the vendored fixture reported zero undesigned differences while this was open,
+which is true and less reassuring than it sounds: **the fixture is the set of differences as of
+9.24.0, so it cannot contain a path that first opened in 9.25.0.** Their observation, and it belongs
+next to every regression fixture.
+
+## [9.26.0] - 2026-10-07
+
+One rule, replacing a special case that had already caused a bug: **absent is absent, present and
+wrong is wrong.** From the block-penn-station session, whose rerun of its differential fuzz against
+9.25.0 found a regression 9.25.0 itself introduced, hours old.
+
+### Fixed — `examples/gateway` called a wrong-typed `spv` member "not mined yet"
+
+9.25.0 made a certificate with **no** `spv` member return `indeterminate`, which was right: the
+service issues certificates in that state and fills the envelope when a block arrives. It was
+written as `!certificate.spv || typeof certificate.spv !== 'object'`, which also swallowed
+`spv: "zz"`, `spv: 0`, `spv: true` and `spv: 42` — **66 inputs** told to re-fetch a certificate that
+re-fetching will never repair.
+
+`indeterminate` is now only for `undefined` and `null`. A member that is present and is a string, a
+boolean or a number is a malformed certificate, and invalid.
+
+### Changed — a null `anchor.seal` or `spv.format` is a malformed member, not an absent one
+
+Both shipped with a null exemption: `seal !== undefined && seal !== null`. The argument against it
+is theirs and is better than mine was — a verifier that reads a wrong-typed member as absent has to
+decide the same for `false`, `0` and `''` next, and **that exemption is exactly what produced the
+`spv` bug above**, in this library and in the notaryhash SDK on the same day.
+
+So `anchor.seal: null` and `spv.format: null` are now refused as malformed members. And
+`allowUncheckedSeal` does **not** wave a malformed seal through: that opt-out means "I will check
+the seal myself", which nobody can do with a seal that is not a seal.
+
+### Added — the independent verifier's differences, vendored as a regression fixture
+
+`test/data/differential/penn-station-9.24.0-differences.jsonl` — 436 inputs, 1,494,064 bytes,
+sha256 `fe5007e3179fccd9ebec813fe5eaa924e70dccf9ea4ff9a1aee53ee60b9e5fb0`. **Theirs, not ours**,
+vendored with permission because the directory it was produced in is git-ignored on their side.
+Every input where our adapter disagreed with their Python verifier at 9.24.0.
+
+`test/notaryhash/differential_fixture.js` replays it. The remaining differences are by design and
+named in the test: the opt-in `anchor.network` label, our stricter refusal of a wrong `mode` on a
+batch certificate, and `version: 1`.
+
+### Not changed — `version: 1` is the legacy marker, and I was wrong to accept that one
+
+I told them I would tighten `version` as the **number** 1, since the reference format says the
+string `"1.0"`. Checking before changing it: `LEGACY_VERSION = 1`, `Certificate.isLegacy` treats it
+as an 8.3.0–9.8.0 certificate, and `verify` reports `legacy: true` beside the verdict. It is a
+documented compatibility path, not loose typing, and tightening it would stop us reading
+certificates that format actually produced. Retracted.
+
 ## [9.25.0] - 2026-10-07
 
 Two claims a certificate can carry that this library does not verify, and answered `valid` about

package/README.md

@@ -2,7 +2,7 @@
 
 Bitcoin SV library with an interpreter-verified script engine.
 
-[![Version](https://img.shields.io/badge/version-9.25.0-blue.svg)](https://www.npmjs.com/package/@smartledger/bsv)
+[![Version](https://img.shields.io/badge/version-9.26.1-blue.svg)](https://www.npmjs.com/package/@smartledger/bsv)
 [![License](https://img.shields.io/badge/license-MIT-green.svg)](LICENSE)
 [![Stability](https://img.shields.io/badge/9.x%20stable%20until-2027--09--01-brightgreen.svg)](STABILITY.md)
 
@@ -155,44 +155,44 @@ const bsv = require('@smartledger/bsv')                 // 128 modules
 ### **Core Modules**
 | Module | Size | Use Case | CDN |
 |--------|------|----------|-----|
-| **bsv.min.js** | 1070KB | Core BSV + SmartContract | `unpkg.com/@smartledger/bsv@9.25.0/bsv.min.js` |
-| **bsv.bundle.js** | 1070KB | Everything in one file | `unpkg.com/@smartledger/bsv@9.25.0/bsv.bundle.js` |
+| **bsv.min.js** | 1071KB | Core BSV + SmartContract | `unpkg.com/@smartledger/bsv@9.26.1/bsv.min.js` |
+| **bsv.bundle.js** | 1071KB | Everything in one file | `unpkg.com/@smartledger/bsv@9.26.1/bsv.bundle.js` |
 
 ### **W3C Verifiable Credentials**
 | Module | Size | Use Case | CDN |
 |--------|------|----------|-----|
-| **🟢 bsv-didweb.min.js** | 166KB | **DID:web generation** | `unpkg.com/@smartledger/bsv@9.25.0/bsv-didweb.min.js` |
-| **🟢 bsv-vcjwt.min.js** | 166KB | **VC-JWT issue/verify** | `unpkg.com/@smartledger/bsv@9.25.0/bsv-vcjwt.min.js` |
-| **🟢 bsv-statuslist.min.js** | 256KB | **StatusList2021 revocation** | `unpkg.com/@smartledger/bsv@9.25.0/bsv-statuslist.min.js` |
-| **🟢 bsv-anchor.min.js** | 164KB | **BSV anchoring (hash-only)** | `unpkg.com/@smartledger/bsv@9.25.0/bsv-anchor.min.js` |
+| **🟢 bsv-didweb.min.js** | 166KB | **DID:web generation** | `unpkg.com/@smartledger/bsv@9.26.1/bsv-didweb.min.js` |
+| **🟢 bsv-vcjwt.min.js** | 166KB | **VC-JWT issue/verify** | `unpkg.com/@smartledger/bsv@9.26.1/bsv-vcjwt.min.js` |
+| **🟢 bsv-statuslist.min.js** | 256KB | **StatusList2021 revocation** | `unpkg.com/@smartledger/bsv@9.26.1/bsv-statuslist.min.js` |
+| **🟢 bsv-anchor.min.js** | 164KB | **BSV anchoring (hash-only)** | `unpkg.com/@smartledger/bsv@9.26.1/bsv-anchor.min.js` |
 
 ### **Smart Contract & Development**
 | Module | Size | Use Case | CDN |
 |--------|------|----------|-----|
-| **bsv-smartcontract.min.js** | 141KB | Complete covenant framework | `unpkg.com/@smartledger/bsv@9.25.0/bsv-smartcontract.min.js` |
-| **bsv-covenant.min.js** | 35KB | Covenant operations | `unpkg.com/@smartledger/bsv@9.25.0/bsv-covenant.min.js` |
-| **bsv-script-helper.min.js** | 33KB | Custom script tools | `unpkg.com/@smartledger/bsv@9.25.0/bsv-script-helper.min.js` |
-| **bsv-security.min.js** | 32KB | Security enhancements | `unpkg.com/@smartledger/bsv@9.25.0/bsv-security.min.js` |
+| **bsv-smartcontract.min.js** | 141KB | Complete covenant framework | `unpkg.com/@smartledger/bsv@9.26.1/bsv-smartcontract.min.js` |
+| **bsv-covenant.min.js** | 35KB | Covenant operations | `unpkg.com/@smartledger/bsv@9.26.1/bsv-covenant.min.js` |
+| **bsv-script-helper.min.js** | 33KB | Custom script tools | `unpkg.com/@smartledger/bsv@9.26.1/bsv-script-helper.min.js` |
+| **bsv-security.min.js** | 32KB | Security enhancements | `unpkg.com/@smartledger/bsv@9.26.1/bsv-security.min.js` |
 
 ### **Legal & Compliance**
 | Module | Size | Use Case | CDN |
 |--------|------|----------|-----|
-| **bsv-ltp.min.js** | 544KB | Legal Token Protocol | `unpkg.com/@smartledger/bsv@9.25.0/bsv-ltp.min.js` |
-| **bsv-gdaf.min.js** | 1070KB | Digital Identity & Attestation | `unpkg.com/@smartledger/bsv@9.25.0/bsv-gdaf.min.js` |
+| **bsv-ltp.min.js** | 544KB | Legal Token Protocol | `unpkg.com/@smartledger/bsv@9.26.1/bsv-ltp.min.js` |
+| **bsv-gdaf.min.js** | 1071KB | Digital Identity & Attestation | `unpkg.com/@smartledger/bsv@9.26.1/bsv-gdaf.min.js` |
 
 ### **Advanced Cryptography**
 | Module | Size | Use Case | CDN |
 |--------|------|----------|-----|
-| **bsv-shamir.min.js** | 177KB | Threshold Cryptography | `unpkg.com/@smartledger/bsv@9.25.0/bsv-shamir.min.js` |
+| **bsv-shamir.min.js** | 177KB | Threshold Cryptography | `unpkg.com/@smartledger/bsv@9.26.1/bsv-shamir.min.js` |
 
 ### **Utilities**
 | Module | Size | Use Case | CDN |
 |--------|------|----------|-----|
-| **bsv-ecies.min.js** | 139KB | Encryption | `unpkg.com/@smartledger/bsv@9.25.0/bsv-ecies.min.js` |
-| **bsv-message.min.js** | 34KB | Message signing | `unpkg.com/@smartledger/bsv@9.25.0/bsv-message.min.js` |
-| **bsv-mnemonic.min.js** | 320KB | HD wallets | `unpkg.com/@smartledger/bsv@9.25.0/bsv-mnemonic.min.js` |
+| **bsv-ecies.min.js** | 139KB | Encryption | `unpkg.com/@smartledger/bsv@9.26.1/bsv-ecies.min.js` |
+| **bsv-message.min.js** | 34KB | Message signing | `unpkg.com/@smartledger/bsv@9.26.1/bsv-message.min.js` |
+| **bsv-mnemonic.min.js** | 320KB | HD wallets | `unpkg.com/@smartledger/bsv@9.26.1/bsv-mnemonic.min.js` |
 ```html
-<script src="https://unpkg.com/@smartledger/bsv@9.25.0/bsv.min.js"></script>
+<script src="https://unpkg.com/@smartledger/bsv@9.26.1/bsv.min.js"></script>
 <script>
   const key = bsv.PrivateKey.fromRandom()
 </script>
@@ -240,4 +240,4 @@ MIT
 
 ---
 
-**SmartLedger-BSV v9.25.0**
+**SmartLedger-BSV v9.26.1**