@smartledger/bsv 9.26.0 → 9.26.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +103 -0
- package/README.md +19 -19
- package/bsv-ecies.min.js +4 -1
- package/bsv-gdaf.min.js +38 -35
- package/bsv-ltp.min.js +1 -1
- package/bsv-smartcontract.min.js +1 -1
- package/bsv.bundle.js +38 -35
- package/bsv.min.js +38 -35
- package/docs/AUDIT_SCOPE.md +10 -10
- package/docs/MODULE_REFERENCE_COMPLETE.md +27 -27
- package/docs/advanced/UTXO_MANAGER_GUIDE.md +1 -1
- package/docs/audit-rfq/cure53.txt +2 -2
- package/docs/audit-rfq/ncc-group.txt +2 -2
- package/docs/audit-rfq/trail-of-bits.txt +2 -2
- package/docs/getting-started/INSTALLATION.md +23 -23
- package/docs/getting-started/QUICK_START.md +7 -7
- package/docs/migration/FROM_BSV_1_5_6.md +5 -5
- package/lib/crypto/ecdsa.js +6 -3
- package/lib/ecies/electrum-ecies.js +17 -1
- package/lib/notaryhash/index.js +49 -4
- package/package.json +1 -1
- package/version.js +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -7,6 +7,109 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|
|
7
7
|
|
|
8
8
|
## [Unreleased]
|
|
9
9
|
|
|
10
|
+
## [9.26.2] - 2026-10-07
|
|
11
|
+
|
|
12
|
+
### Fixed — the library printed to the console during ordinary operation
|
|
13
|
+
|
|
14
|
+
Both reported or surfaced by the `smartledger-wallet` session, which is on 9.26.1 in production.
|
|
15
|
+
|
|
16
|
+
**ECIES `decrypt()` wrote a `console.log` on every call** when the caller had set
|
|
17
|
+
`fixedPublicKey` — so a wallet decrypting a page of messages got one line per message, on a
|
|
18
|
+
channel it could not silence. The advice in the notice is worth giving; giving it repeatedly is
|
|
19
|
+
not. It now follows the same idiom as the interpreter's era hint: `console.warn`, **once per
|
|
20
|
+
process**, silenceable with `ECIES.notices = false` or `BSV_NO_ECIES_NOTICE=1`.
|
|
21
|
+
|
|
22
|
+
**`ECDSA#calci` wrote expected exceptions to stderr.** It tries all four recovery ids and most do
|
|
23
|
+
not yield a point — the throw *is* the signal that an id is wrong, and `continue` is the handling.
|
|
24
|
+
It called `console.error(e)` first, so ordinary message signing printed stack traces. Nothing is
|
|
25
|
+
swallowed that matters: if no id works the loop falls through and the caller is told.
|
|
26
|
+
|
|
27
|
+
Neither changes any returned value, and a test now asserts that signing a message and decrypting
|
|
28
|
+
three times write nothing to `console.log` or `console.error`.
|
|
29
|
+
|
|
30
|
+
**Not changed, having looked:** importing the package prints nothing, and the other `console` calls
|
|
31
|
+
in `lib/` are either interactive debugger tools where output is the purpose
|
|
32
|
+
(`script_interpreter.js`, `stack_examiner.js`, `covenant_builder.js`) or behind an explicit
|
|
33
|
+
`debug(enabled)` switch. `lib/smart_contract/opcode_list.js` prints at module top level but is
|
|
34
|
+
required by nothing, so it never fires for a consumer.
|
|
35
|
+
|
|
36
|
+
### Verified — the wallet's browser pins match this build exactly
|
|
37
|
+
|
|
38
|
+
They pin three browser files by SRI and asked to be told if our build disagreed. Computed from the
|
|
39
|
+
published 9.26.1 tarball:
|
|
40
|
+
|
|
41
|
+
```
|
|
42
|
+
bsv.bundle.js 1,096,275 bytes sha384-kMbrG7nRThsrLmHkucEADL5/… EXACT MATCH
|
|
43
|
+
bsv-ecies.min.js 141,453 bytes sha384-iX7ag/1sZMmIBter7ifc0XmH… EXACT MATCH
|
|
44
|
+
bsv-message.min.js 34,621 bytes sha384-eShyjd68/NEEh/6tumD9/8rV… EXACT MATCH
|
|
45
|
+
```
|
|
46
|
+
|
|
47
|
+
`bsv-message.min.js` is byte-identical to 9.10.0, as they reported — confirmed by comparing the two
|
|
48
|
+
published tarballs. **Note that `bsv-ecies.min.js` changes in this release**, since the notice fix
|
|
49
|
+
is in it.
|
|
50
|
+
|
|
51
|
+
### Fixed — `examples/gateway` reported a non-measurement as a verdict
|
|
52
|
+
|
|
53
|
+
**Repo only; `examples/` is not in the package's `files` list, so nothing published changed and
|
|
54
|
+
there is no new version.**
|
|
55
|
+
|
|
56
|
+
The adapter read `report.shape` as if it were a boolean. It is an **array** of problems, so
|
|
57
|
+
`triage.shape === false` never matched and the accurate diagnosis was discarded. And because
|
|
58
|
+
`NotaryHash.verify` returns **early** on a shape problem, `signature` and `proofIntegrity` are still
|
|
59
|
+
their initial `false` at that point — never measured. The adapter reported those two as findings.
|
|
60
|
+
|
|
61
|
+
```
|
|
62
|
+
mode = "zz" before: signature does not verify now: mode must be "full" or "hybrid"
|
|
63
|
+
version = 2.0 before: signature does not verify now: unsupported version: "2.0"
|
|
64
|
+
bad signature before: signature does not verify now: unchanged — it really is the signature
|
|
65
|
+
```
|
|
66
|
+
|
|
67
|
+
**The library was right throughout**; only the example mistranslated it. This was the file
|
|
68
|
+
reporting a non-measurement as a verdict, which is the distinction it spends two paragraphs at the
|
|
69
|
+
top insisting on, and the block-penn-station session reported the symptom three times before it was
|
|
70
|
+
fixed.
|
|
71
|
+
|
|
72
|
+
|
|
73
|
+
## [9.26.1] - 2026-10-07
|
|
74
|
+
|
|
75
|
+
### Fixed — relabelling a certificate as legacy bypassed the seal refusal
|
|
76
|
+
|
|
77
|
+
`version` is not signed. The proof hash begins with the fixed bytes `"NotaryHash/1.0"` and `u8(1)`
|
|
78
|
+
whatever the JSON member says, so **anyone could set `version: 1` on a current sealed certificate**
|
|
79
|
+
and a forged seal verified as `valid` again — the refusal added in 9.25.0 was optional for an
|
|
80
|
+
attacker. Found by the block-penn-station session's rerun about half an hour after it shipped.
|
|
81
|
+
|
|
82
|
+
The mechanism, which is the part worth keeping:
|
|
83
|
+
|
|
84
|
+
- `Certificate.normalize` rebuilds a **legacy** anchor from a fixed key set — `type`, `network`,
|
|
85
|
+
`txid`, `vout`, `blockHeight`, `blockTime` — and therefore **drops `anchor.seal`**;
|
|
86
|
+
- `NotaryHash.verify` normalizes on the line after it records `report.legacy`, **shadowing its own
|
|
87
|
+
parameter**, so every downstream check — including `verifyAnchorSPV`'s own seal check — reads
|
|
88
|
+
normalized input whether it knows it or not;
|
|
89
|
+
- so the seal check could not see a seal on a legacy certificate, and the legacy path kept the
|
|
90
|
+
height, time and format checks while silently losing this one.
|
|
91
|
+
|
|
92
|
+
`anchor.seal` is now captured **before** the translation and the verdict accounts for it, so the
|
|
93
|
+
refusal holds on both paths. A genuine legacy certificate — one with no seal — verifies unchanged,
|
|
94
|
+
and `allowUncheckedSeal` works on both paths.
|
|
95
|
+
|
|
96
|
+
**The general rule, now in the source:** *a refusal that exists only on one normalization path is
|
|
97
|
+
optional whenever the caller can choose the path.* Anything under `anchor` outside that fixed key
|
|
98
|
+
set is in the same position and must be checked before translation.
|
|
99
|
+
|
|
100
|
+
### And a correction to 9.26.0's release notes
|
|
101
|
+
|
|
102
|
+
9.26.0 said `version: 1` needed no change because it is the documented 8.3.0–9.8.0 marker. The
|
|
103
|
+
first half stands — reading it is deliberate, and `verify` reports `legacy: true`. The conclusion
|
|
104
|
+
did not: an unsigned discriminator that selects a *weaker* code path is a security boundary, not a
|
|
105
|
+
compatibility detail, and I had checked that the legacy path was intentional without checking that
|
|
106
|
+
it was equally strict.
|
|
107
|
+
|
|
108
|
+
9.26.0's replay of the vendored fixture reported zero undesigned differences while this was open,
|
|
109
|
+
which is true and less reassuring than it sounds: **the fixture is the set of differences as of
|
|
110
|
+
9.24.0, so it cannot contain a path that first opened in 9.25.0.** Their observation, and it belongs
|
|
111
|
+
next to every regression fixture.
|
|
112
|
+
|
|
10
113
|
## [9.26.0] - 2026-10-07
|
|
11
114
|
|
|
12
115
|
One rule, replacing a special case that had already caused a bug: **absent is absent, present and
|
package/README.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
Bitcoin SV library with an interpreter-verified script engine.
|
|
4
4
|
|
|
5
|
-
[](https://www.npmjs.com/package/@smartledger/bsv)
|
|
6
6
|
[](LICENSE)
|
|
7
7
|
[](STABILITY.md)
|
|
8
8
|
|
|
@@ -155,44 +155,44 @@ const bsv = require('@smartledger/bsv') // 128 modules
|
|
|
155
155
|
### **Core Modules**
|
|
156
156
|
| Module | Size | Use Case | CDN |
|
|
157
157
|
|--------|------|----------|-----|
|
|
158
|
-
| **bsv.min.js** | 1071KB | Core BSV + SmartContract | `unpkg.com/@smartledger/bsv@9.26.
|
|
159
|
-
| **bsv.bundle.js** | 1071KB | Everything in one file | `unpkg.com/@smartledger/bsv@9.26.
|
|
158
|
+
| **bsv.min.js** | 1071KB | Core BSV + SmartContract | `unpkg.com/@smartledger/bsv@9.26.2/bsv.min.js` |
|
|
159
|
+
| **bsv.bundle.js** | 1071KB | Everything in one file | `unpkg.com/@smartledger/bsv@9.26.2/bsv.bundle.js` |
|
|
160
160
|
|
|
161
161
|
### **W3C Verifiable Credentials**
|
|
162
162
|
| Module | Size | Use Case | CDN |
|
|
163
163
|
|--------|------|----------|-----|
|
|
164
|
-
| **🟢 bsv-didweb.min.js** | 166KB | **DID:web generation** | `unpkg.com/@smartledger/bsv@9.26.
|
|
165
|
-
| **🟢 bsv-vcjwt.min.js** | 166KB | **VC-JWT issue/verify** | `unpkg.com/@smartledger/bsv@9.26.
|
|
166
|
-
| **🟢 bsv-statuslist.min.js** | 256KB | **StatusList2021 revocation** | `unpkg.com/@smartledger/bsv@9.26.
|
|
167
|
-
| **🟢 bsv-anchor.min.js** | 164KB | **BSV anchoring (hash-only)** | `unpkg.com/@smartledger/bsv@9.26.
|
|
164
|
+
| **🟢 bsv-didweb.min.js** | 166KB | **DID:web generation** | `unpkg.com/@smartledger/bsv@9.26.2/bsv-didweb.min.js` |
|
|
165
|
+
| **🟢 bsv-vcjwt.min.js** | 166KB | **VC-JWT issue/verify** | `unpkg.com/@smartledger/bsv@9.26.2/bsv-vcjwt.min.js` |
|
|
166
|
+
| **🟢 bsv-statuslist.min.js** | 256KB | **StatusList2021 revocation** | `unpkg.com/@smartledger/bsv@9.26.2/bsv-statuslist.min.js` |
|
|
167
|
+
| **🟢 bsv-anchor.min.js** | 164KB | **BSV anchoring (hash-only)** | `unpkg.com/@smartledger/bsv@9.26.2/bsv-anchor.min.js` |
|
|
168
168
|
|
|
169
169
|
### **Smart Contract & Development**
|
|
170
170
|
| Module | Size | Use Case | CDN |
|
|
171
171
|
|--------|------|----------|-----|
|
|
172
|
-
| **bsv-smartcontract.min.js** | 141KB | Complete covenant framework | `unpkg.com/@smartledger/bsv@9.26.
|
|
173
|
-
| **bsv-covenant.min.js** | 35KB | Covenant operations | `unpkg.com/@smartledger/bsv@9.26.
|
|
174
|
-
| **bsv-script-helper.min.js** | 33KB | Custom script tools | `unpkg.com/@smartledger/bsv@9.26.
|
|
175
|
-
| **bsv-security.min.js** | 32KB | Security enhancements | `unpkg.com/@smartledger/bsv@9.26.
|
|
172
|
+
| **bsv-smartcontract.min.js** | 141KB | Complete covenant framework | `unpkg.com/@smartledger/bsv@9.26.2/bsv-smartcontract.min.js` |
|
|
173
|
+
| **bsv-covenant.min.js** | 35KB | Covenant operations | `unpkg.com/@smartledger/bsv@9.26.2/bsv-covenant.min.js` |
|
|
174
|
+
| **bsv-script-helper.min.js** | 33KB | Custom script tools | `unpkg.com/@smartledger/bsv@9.26.2/bsv-script-helper.min.js` |
|
|
175
|
+
| **bsv-security.min.js** | 32KB | Security enhancements | `unpkg.com/@smartledger/bsv@9.26.2/bsv-security.min.js` |
|
|
176
176
|
|
|
177
177
|
### **Legal & Compliance**
|
|
178
178
|
| Module | Size | Use Case | CDN |
|
|
179
179
|
|--------|------|----------|-----|
|
|
180
|
-
| **bsv-ltp.min.js** | 544KB | Legal Token Protocol | `unpkg.com/@smartledger/bsv@9.26.
|
|
181
|
-
| **bsv-gdaf.min.js** | 1071KB | Digital Identity & Attestation | `unpkg.com/@smartledger/bsv@9.26.
|
|
180
|
+
| **bsv-ltp.min.js** | 544KB | Legal Token Protocol | `unpkg.com/@smartledger/bsv@9.26.2/bsv-ltp.min.js` |
|
|
181
|
+
| **bsv-gdaf.min.js** | 1071KB | Digital Identity & Attestation | `unpkg.com/@smartledger/bsv@9.26.2/bsv-gdaf.min.js` |
|
|
182
182
|
|
|
183
183
|
### **Advanced Cryptography**
|
|
184
184
|
| Module | Size | Use Case | CDN |
|
|
185
185
|
|--------|------|----------|-----|
|
|
186
|
-
| **bsv-shamir.min.js** | 177KB | Threshold Cryptography | `unpkg.com/@smartledger/bsv@9.26.
|
|
186
|
+
| **bsv-shamir.min.js** | 177KB | Threshold Cryptography | `unpkg.com/@smartledger/bsv@9.26.2/bsv-shamir.min.js` |
|
|
187
187
|
|
|
188
188
|
### **Utilities**
|
|
189
189
|
| Module | Size | Use Case | CDN |
|
|
190
190
|
|--------|------|----------|-----|
|
|
191
|
-
| **bsv-ecies.min.js** | 139KB | Encryption | `unpkg.com/@smartledger/bsv@9.26.
|
|
192
|
-
| **bsv-message.min.js** | 34KB | Message signing | `unpkg.com/@smartledger/bsv@9.26.
|
|
193
|
-
| **bsv-mnemonic.min.js** | 320KB | HD wallets | `unpkg.com/@smartledger/bsv@9.26.
|
|
191
|
+
| **bsv-ecies.min.js** | 139KB | Encryption | `unpkg.com/@smartledger/bsv@9.26.2/bsv-ecies.min.js` |
|
|
192
|
+
| **bsv-message.min.js** | 34KB | Message signing | `unpkg.com/@smartledger/bsv@9.26.2/bsv-message.min.js` |
|
|
193
|
+
| **bsv-mnemonic.min.js** | 320KB | HD wallets | `unpkg.com/@smartledger/bsv@9.26.2/bsv-mnemonic.min.js` |
|
|
194
194
|
```html
|
|
195
|
-
<script src="https://unpkg.com/@smartledger/bsv@9.26.
|
|
195
|
+
<script src="https://unpkg.com/@smartledger/bsv@9.26.2/bsv.min.js"></script>
|
|
196
196
|
<script>
|
|
197
197
|
const key = bsv.PrivateKey.fromRandom()
|
|
198
198
|
</script>
|
|
@@ -240,4 +240,4 @@ MIT
|
|
|
240
240
|
|
|
241
241
|
---
|
|
242
242
|
|
|
243
|
-
**SmartLedger-BSV v9.26.
|
|
243
|
+
**SmartLedger-BSV v9.26.2**
|