fix(deps): update dependency @noble/curves to v1.9.7

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@noble/curves (source)	1.8.1 → 1.9.7

---

Release Notes

paulmillr/noble-curves (@​noble/curves)

v1.9.7

Compare Source

• Renamed the newly introduced, experimental Edwards method toMontgomeryPriv to toMontgomerySecret.
• Restored SignatureConstructor for Weierstrass curves.
• Added more deprecations and preparations for version 2.

v1.9.6

Compare Source

• Exposed nBitLength and nByteLength for Edwards curves.
• Renamed secret and public to secretKey and publicKey in the experimental CurveLengths interface.
• Began point precomputation earlier, within weierstrass(), while retaining lazy calculation until the first call.
• Added the new internal version-2 tower implementation to BLS.
• Ensured Ed448 and Decaf44 use separate Fn fields with different BITS lengths.

v1.9.5

Compare Source

• Fixed Rollup warnings from #​205.
• Restored aliases for secp256r1, secp384r1, and secp521r1 from #​203.
• Restored CURVE.nByteLength from #​202.
• Added more preparations and deprecations for the future version-2 release.

v1.9.4

Compare Source

• Fixed #​201, an invalid renaming of ProjConstructor.
• Added more deprecations for the upcoming version-2 release.

v1.9.3

Compare Source

This release contains bug fixes and improvements that pave the way for version 2. Existing code continues to work unchanged, while old APIs are visually flagged as deprecated through JSDoc in TypeScript-aware environments.

• Renamed *privateKey to *secretKey throughout for consistency with post-quantum and non-noble libraries.
• Added keygen, which creates both secret and public keys.
• Made the Weierstrass endomorphism generic for all Koblitz curves.
• Added fromBytes and toBytes to Weierstrass signatures and deprecated fromDER, fromCompact, toDERRawBytes, and toCompactRawBytes.
• Moved Edwards edwardsToMontgomery into utils.toMontgomery.
• Added a new Decaf and Ristretto interface that is more consistent with other points.
• Added ED448_TORSION_GROUP for Ed448.
• Added curve.info to all curves for better interoperability.
• Changed the public wNAF API.
• Added sqrt9mod16 to modular arithmetic.
• Moved all hash-to-curve hashers into _hasher properties, such as secp256k1_hasher.
• Added ACVP test vectors.

Sensitive code changes

• Primarily renamed wNAF internals.
• Added field-bound validation for scalar fields (Fn) and curve fields (Fp).

v1.9.2

Compare Source

This release contains bug fixes and improvements that pave the way for version 2.

• Substantially refactored Edwards and Weierstrass curves with a simpler ECDSA and EdDSA API in #​192.
  • The old code continues to work until version 2.
  • The new API is experimental until the next patch release.
  • Renamed toRawBytes to toBytes.
  • Renamed ExtendedPoint and ProjectivePoint to Point.
  • Added static Fp and Fn field properties to Point.
• Added support for ECDSA on curves with a cofactor greater than one.
• Added support for points with an x-coordinate of zero in Weierstrass curves.
• Substantially refactored BLS, improved types, and added the new bls.longSignatures and bls.shortSignatures APIs.
  • The old code continues to work until version 2.
  • The new API is experimental until the next patch release.
• Reused noble-hashes utilities.
• Used randomBytes and HMAC from noble-hashes by default.

Sensitive code changes

• Refactored range-check logic for Edwards and Weierstrass curves.
• Improved Weierstrass sign() logic for nonce generation.
• Hardened multiplyUnsafe and stopped using multiplyAndAddUnsafe for Weierstrass curves.

New Contributors

• @​randombit added a test that BLS12-381 augmented signatures can be verified in #​191.

v1.9.1

Compare Source

• Added an experimental FFT/NTT implementation in abstract/fft.
• Verified Edwards curve parameters against the curve equation during initialization.
• Verified Weierstrass curve parameters against the discriminant during initialization.
• Improved getSharedSecret argument validation for rare Weierstrass curves.
• Fixed invalid signature-recovery decoding lengths for rare Weierstrass curves.
• Improved modular square-root calculation.
• Allowed X25519 and X448 to accept more valid private- and public-key inputs.
• Improved secp256k1 tree-shaking.

v1.9.0

Compare Source

This release contains bug fixes and improvements that pave the way for version 2.

• Modules are now available with a .js extension.
  • Old: @noble/curves/ed25519
  • New: @noble/curves/ed25519.js
  • The old path remains available.
  • This simplifies native browser usage without transpilers.
• Added sponge and Grain LFSR support to Poseidon.
• Merged P-256, P-384, and P-521 into the new nist module.
• Prohibited y-coordinates of zero during Weierstrass initialization.
• Used inv0 throughout hash-to-curve to ensure zero elements are returned in exceptional cases.
• Improved modular square-root logic, including Tonelli-Shanks and Legendre calculations.
• Fixed FpInvertBatch creating sparse arrays instead of arrays containing undefined.
• Deprecated Pasta curves.
• Updated noble-hashes to 1.8.0.

v1.8.2

Compare Source

• Important: adjusted wNAF scalar multiplication logic.
  • The adjustment is small and deduplicates code, but wNAF is sensitive code that handles private keys.
  • Review the change in #​184.
• Made Edwards curves such as Ed25519 and Ed448 always use the complete addition formula.
• Prohibited Edwards points with z = 0; zero points have z = 1.
• Used a slower but more precise CURVE.a definition for Ed25519.
• Froze Weierstrass signatures on creation.
• Fixed Weierstrass curves in the Pale Moon browser (#​176).
• Improved the hash-to-curve error for zero in mapToCurve.
• Fixed the incorrect Fp12 fields type in tower.
• Added the misc module containing Jubjub and Baby Jubjub.
• Updated utils to use built-in Uint8Array toHex and fromHex when available, providing a 13× speed-up on 256-byte arrays and a 20× speed-up on 32 KB arrays.

Other changes

• Updated noble-hashes to 1.7.2.
• Reduced the standalone build by 500 bytes.
• Standalone build files are now attested in CI. See the README for the verification guide.
• TypeScript source can now be used without compilation in Node.js 24 due to erasableSyntaxOnly.

New Contributors

• @​tuantran-genetica made their first contribution in #​181.
• @​kigawas made their first contribution in #​183.

Acknowledgments

Thanks to @​ChALkeR for spotting the Edwards bug.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "every weekend"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​noble/​curves@​1.8.1 ⏵ 1.9.7				+2

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm @noble/hashes is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/@noble/curves@1.9.7 → npm/@noble/hashes@1.8.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@noble/hashes@1.8.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm @noble/hashes is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/@noble/curves@1.9.7 → npm/@noble/hashes@1.8.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@noble/hashes@1.8.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report