The ranges ^1.3 resolve to @noble/curves 1.9 and @noble/hashes 1.8 for
everyone who installs this package, and those mark the calls used here
deprecated: the sha256/sha512/blake2b module paths, ProjectivePoint,
toRawBytes, px/py, Signature.fromCompact.
- hashes from @noble/hashes/sha2 and @noble/hashes/blake2
- secp256k1.Point with toBytes(true) for compression
- expand reads the affine x/y (toAffine) instead of the projective fields
- recover builds the signature with Signature.fromBytes(sig, 'compact') and
returns toBytes() (compressed, as toRawBytes() did). Its method form of
recoverPublicKey stays, with the reason on the line: the replacement is not
in @noble/curves 1.9's types, and 2.x, which types it, is ESM-only.
The minimum versions rise with this (package.json, next commit).
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
On TypeScript 5.5 (upstream's) require('@pezkuwi/util') in this CommonJS
shim reported an error the directive silenced; on 5.9, which this tree
resolves, the line is clean and the unused directive fails the build.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
The renamed chains (dicle, pezkuwi, pezkuwichain, zagros) were inserted where
their predecessors stood, which sort-keys rejects. The 57 entries are
unchanged; only their order is.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Import order and stray blank lines left by the scure-sr25519 swap, plus the
2026 headers of these files. eslint --fix output; no code changes.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
The header rule takes the current year as the end of the range, as upstream's
does; 581 sources still ended at 2025, which failed lint. Lint never ran to
completion here, so this went unseen.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
19c8d69 (2026-01-11) and later commits added the build's output to every
package directory: 1484 .js/.d.ts files under cjs/ and at the package roots,
plus 14 copies of LICENSE (identical to the root one, which the build copies
into each package itself). Upstream keeps none of it. With the source
manifests pointing at them, imports resolved to this stale output instead of
src, and a JavaScript-checking build (@pezkuwi/dev 0.85.12) reads them as
inputs (TS5055).
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
The root resolutions pointed @pezkuwi/scure-sr25519 at
portal:/home/mamostehp/pezkuwi-wasm/packages/scure-sr25519, a directory
that only existed on the machine 14.0.25 was published from. Everywhere
else `yarn install` stops with "Manifest not found", so this repository
could not be installed, built or tested, and the PR workflow had never run.
util-crypto already asks for ^0.2.1, which is on npm; its lib/ is identical
to packages/scure-sr25519 in pezkuwi-wasm (same "bizinikiwi" signing
context). Dropping the resolution resolves it there.
With this, install, lint and test run. They are not green yet: 161 of
3014 tests fail, most of them on @pezkuwi/wasm-crypto 7.5.17 stubs
(secp256k1, ed25519, scrypt, bip39Generate "not yet implemented"), which
pezkuwi-wasm#2 fixes as 7.5.19. That, the remaining failures and the
continue-on-error in pr-any.yml follow once 7.5.19 is published.
- Author: Dijital Kurdistan Tech Institute <dev@pezkuwichain.io>
- Fixed Uint8Array type errors in test files
- Added @types/react-native devDependency for x-randomvalues
- Added @pezkuwi/hw-ledger devDependency for networks tests
- Added @pezkuwi/x-randomvalues devDependency for util tests
- Updated all internal dependencies to 14.0.12
