@ninsei-labs/sdk 0.44.2 → 0.44.3
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 +9 -0
- package/package.json +1 -1
- package/src/sweep-restore.mjs +4 -1
- package/src/version.mjs +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,3 +1,12 @@
|
|
|
1
|
+
## 0.44.3 — 2026-10-20
|
|
2
|
+
|
|
3
|
+
A RESCAN THAT THE LIBRARY REFUSES DOES NOT STOP THE RESTORE.
|
|
4
|
+
|
|
5
|
+
- `sweep.restore` still asks for the rescan first. If the wallet library refuses it, the pass continues to the
|
|
6
|
+
sync and the balance, exactly as a failed sync already did. A wallet opened from keys carries its height from
|
|
7
|
+
creation, so a library that cannot rescan a chain can still serve the withdrawal. The spendable balance stays
|
|
8
|
+
the verdict, not the rescan.
|
|
9
|
+
|
|
1
10
|
## 0.44.2 — 2026-10-20
|
|
2
11
|
|
|
3
12
|
REGTEST HAS A NAME THE PACKAGE KNOWS.
|
package/package.json
CHANGED
package/src/sweep-restore.mjs
CHANGED
|
@@ -92,7 +92,10 @@ export async function restoreWallet(request = {}) {
|
|
|
92
92
|
// A RESCAN IS REQUIRED, NOT OPTIONAL: without it the height only applies to a wallet that has not scanned yet,
|
|
93
93
|
// and a wallet restored from a key has. A driver that cannot rescan is the caller's mistake, named here.
|
|
94
94
|
if (typeof driver.rescanBlockchain !== "function") throw new SdkError("bad-input", { field: "wallet.driver.rescanBlockchain" });
|
|
95
|
-
|
|
95
|
+
// A RESCAN IS BEST-EFFORT, LIKE THE SYNC BELOW. A wallet built from keys already carries the height it was opened
|
|
96
|
+
// with, and a library that cannot rescan a chain (monero-ts against a regtest node answers "failed to get hashes")
|
|
97
|
+
// would otherwise stop a withdrawal the sync can still serve. The balance below is the verdict, not the rescan.
|
|
98
|
+
try { await step("rescanBlockchain", () => driver.rescanBlockchain()); } catch { /* the balance decides */ }
|
|
96
99
|
|
|
97
100
|
// A FAILED SYNC IS BEST-EFFORT, exactly as in the signing step: what blocks a withdrawal is the spendable
|
|
98
101
|
// remainder, and it is read below. The library throws low-level while scanning a chain it cannot read; that must
|
package/src/version.mjs
CHANGED
|
@@ -6,4 +6,4 @@
|
|
|
6
6
|
// tools/sync-version.mjs. Do not edit it by hand - set the version in package.json and run `npm run sync:version`.
|
|
7
7
|
// The `version` check in tools/check.mjs refuses a mismatch, and refuses a runtime read of package.json here.
|
|
8
8
|
|
|
9
|
-
export const SDK_VERSION = "0.44.
|
|
9
|
+
export const SDK_VERSION = "0.44.3";
|