chore(deps): update dependency @noble/secp256k1 to v2

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@noble/secp256k1 (source)	^1.7.1 -> ^2.1.0

---

Release Notes

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

v2.1.0

Compare Source

This release comes one year after v2.0.0, following rare update schedule for easy auditability.

• Point.fromAffine: convert ZERO points properly
• au8: improve Uint8Array check to work in extension context
• Signature: add normalizeS method
• Signature: addRecoveryBit should return more precise type, SignatureWithRecovery
• randomPrivateKey: fetch 48 bytes from CSPRNG instead of 40, to reduce bias

New Contributors

• @​thejoelw made their first contribution in https://github.com/paulmillr/noble-secp256k1/pull/100
• @​MicahZoltu made their first contribution in https://github.com/paulmillr/noble-secp256k1/pull/102
• @​legobeat made their first contribution in https://github.com/paulmillr/noble-secp256k1/pull/108
• @​Elli610 made their first contribution in https://github.com/paulmillr/noble-secp256k1/pull/121

Full Changelog: paulmillr/noble-secp256k1@2.0.0...2.1.0

v2.0.0

Compare Source

noble-secp256k1 v2 features improved security and smaller attack surface.
The goal of v2 is to provide minimum possible JS library which is safe and fast.

That means the library was reduced 4x, to just over 400 lines. Library size is now just 4KB gzipped.
In order to achieve the goal, some features were moved to noble-curves, which is
even safer and faster drop-in replacement library with same API.
Switch to curves if you intend to keep using these features:

• DER encoding: toDERHex, toDERRawBytes, signing / verification of DER sigs
• Schnorr signatures
• Using utils.precompute() for non-base point
• Support for environments which don't support bigint literals
• Common.js support
• Support for node.js 18 and older without shim

Other changes for upgrading from @​noble/secp256k1 1.7 to 2.0:

• getPublicKey
  • now produce 33-byte compressed signatures by default
  • to use old behavior, which produced 65-byte uncompressed keys, set
    argument isCompressed to false: getPublicKey(priv, false)
• sign
  • is now sync; use signAsync for async version
  • now returns Signature instance with { r, s, recovery } properties
  • canonical option was renamed to lowS
  • recovered option has been removed because recovery bit is always returned now
  • der option has been removed. There are 2 options:
    1. Use compact encoding: fromCompact, toCompactRawBytes, toCompactHex.
       Compact encoding is simply a concatenation of 32-byte r and 32-byte s.
    2. If you must use DER encoding, switch to noble-curves (see above).
• verify
  • strict option was renamed to lowS
• getSharedSecret
  • now produce 33-byte compressed signatures by default
  • to use old behavior, which produced 65-byte uncompressed keys, set
    argument isCompressed to false: getSharedSecret(a, b, false)
• recoverPublicKey(msg, sig, rec) was changed to sig.recoverPublicKey(msg)
• number type for private keys have been removed: use bigint instead
• Point (2d xy) has been changed to ProjectivePoint (3d xyz)
• utils were split into utils (same api as in noble-curves) and
  etc (hmacSha256Sync and others)

Pull request: https://github.com/paulmillr/noble-secp256k1/pull/92

Full Changelog: paulmillr/noble-secp256k1@1.7.1...2.0.0

---

Configuration

📅 Schedule: Branch creation - "after 5pm,every weekend" in timezone America/Los_Angeles, Automerge - "after 5pm,every weekend" in timezone America/Los_Angeles.

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.

[jeanregisser]

This new version is apparently ESM only, skip until we can switch to ESM too.
See react-native-community/cli#2167

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 2.x releases. But if you manually upgrade to 2.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.