Releases: paulmillr/noble-secp256k1
Releases · paulmillr/noble-secp256k1
1.5.3
1.5.2
- Fix library compatibility with bad parsers over bigint syntax
- New exported
utils.mod
utility recoverPublicKey
andPoint.fromSignature
now reducemsgHash
modulo n- Uint8Arrays are now always copied instead of using
.slice()
method of theirs - Hex parsing improvements
1.5.0
- Messages in ECDSA
sign()
are now reduced modulon
to match RFC6979. Contributed by @kklash.- Note: libsecp256k1 is awaiting pull request for the same bugfix
sign
can now receive{extraEntropy: true}
to auto-populatek
with random data. This is strongly recommended, see README- RFC6979 has been thoroughly refactored
1.4.0
- Important: signatures are now
canonical: true
by default. This mirrors libsecp256k1 behavior. If you'd like old (OpenSSL) behavior, usesign
withcanonical: false
- Important:
verify()
is nowstrict: true
by default. High-s signatures are rejected, which also mirrors libsecp behavior. - Important: removed
string
(hex) return type from public methods.Uint8Array
is now always returned - Added
extraEntropy
option tosign
. It allows to specifyk'
as per RFC6979 - Added
Signature#hasHighS()
andSignature#normalizeS()
methods - Rewrite DER parsing logic
- Improve hex parsing security
assertValidity
is now done inSignature
constructor, instead of a separate method- Remove
SignResult
deprecated class that clonedSignature
Full Changelog: 1.3.4...1.4.0
Thanks to @hank121314 for contribution
1.3.3
1.3.2
1.3.1
What's Changed
- Improve compatibility with non-compliant JS parsers: swap n format to Bigint() in #33
- ECMAScript Modules (ESM) support in #32
- Do not depend on
@types/dom
when using Typescript - Improve garbage collector behavior by not using array assignments that call ES6 iterator protocol
New Contributors
Full Changelog: 1.3.0...1.3.1