build(deps): bump @noble/curves from 1.9.7 to 2.3.0

[dependabot]

Bumps @noble/curves from 1.9.7 to 2.3.0.

Release notes

Sourced from @​noble/curves's releases.

2.3.0

Security & constant-timeness

• Hardened constant-time execution from best-effort to actual guarantees: no measurable timing behavior on 200K samples. Scalar multiplication now uses secret-scalar blinding via CSPRNG, un-precomputed points now use a constant-time fixed-window multiply instead of variable-time fallbacks, and modular arithmetic helpers were hardened. New CT benchmarks track timing behavior.
• General hardening across all modules
• Fixes from the Trail of Bits review: recovered ECDSA signatures are now bound to their recovery id, non-canonical BLS signature encodings are rejected, Edwards <-> Montgomery conversion helpers were corrected, and FROST DKG round-2 retry handling was hardened.

X25519 hardening

It was possible to execute a remote timing attack on X25519, across many samples, and learn up to 4.036 bits of long-term private key. Other 247 bits were NOT affected.

The impact: mainly fingerprinting (recognition of key across deployments), NOT key recovery, NOT X25519 breakage. Maintainer was also not able to escalate to co-residency (SMT).

Reported and found by:

• George Stergiopoulos, Department of Informatics, Athens University of Economics and Business, Greece (geostergiop@aueb.gr)
• Constantinos Patsakis, Department of Informatics, University of Piraeus, 80 Karaoli & Dimitriou str., 18534 Piraeus, Greece (kpatsak@unipi.gr)

Performance

• ECDSA/EdDSA verification up to +32%, Weierstrass ECDH up to +19%, x25519 getPublicKey 2.7×
• BLS signatures 2x
• Init time (first getPublicKey or sign) reduced ~2x for ed25519, p256, p384, p521
• Also faster verification of recovered signatures, pairing tower / FFT / Pippenger optimizations, and joint-MSM paths in FROST and OPRF
• getPublicKey / sign got slower because we've decreased window size (W=8 => W=6) and hardened CT execution (see above). Long-running apps that prefer 2.2.0-level speed can restore it with one line: secp256k1.Point.BASE.precompute(8) (likewise for other curves).

Misc

• Smaller bundles: improved tree-shaking across modules
• Better error messages and type checks
• Upgrade noble-hashes to 2.3.0, with performance boost
• Reduce on-disk size 1831kb → 1548kb (-282kb) by disabling source maps (they became less relevant).

Full Changelog: paulmillr/noble-curves@2.2.0...2.3.0

2.2.0

• March 2026 self-audit (all files): no major issues found
  • Audited for spec compliance and security
  • ed25519: make zip215 verification logic match spec more strictly (spec vectors were not enough)
  • ed448: turn off zip215 mode by default, use stricter one
  • schnorr: reduce rand by mod N instead of throwing
  • math: hardening of sqrt
  • babyjubjub: use correct curve and curve params
  • der: improve parsing
  • bls: improve point decoding
  • bls, bn: Fix Fp6 / Fp12 order
  • hash-to-curve: empty dst / count now throws
  • Apply Object.freeze to most primitives
  • Other minor hardening
• Fix all Byte Array types, to ensure proper work in both TypeScript 5.6 & TypeScript 5.9+

... (truncated)

Commits

• da60750 Release 2.3.0.
• 9092187 README
• ff189ce Minor comment reformatting
• 17fda00 jsr: prepare for publish
• e23353d Upgrade to noble-hashes 2.3.0
• 24db224 Minor fixes
• a1d1c85 Update jsbt to 0.6.5
• 243bdaf test: use new syntax
• dc0acf5 Disable source maps
• e229382 Improve tree-shaking
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​noble/curves since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[systemslibrarian]

Landed on main in commit 2e10c16, as part of one verified batch with this repo's other Dependabot PRs.

@noble/curves is now ^2.3.0. This lab imports it as @noble/curves/ed25519.js, which is already the v2-style extensioned subpath, so the v2 export-map change did not affect it.

Batched rather than merged individually because the only workflow that exercises this lab triggers on push to main, so a per-PR merge is verified only once it can already have broken the live demo. The full gate from deploy.yml was run locally on the combined result first: npm test (4 files, 19 tests passed), npm run build (tsc -b && vite build, clean), and npm run test:a11y (12 Playwright tests passed, axe WCAG A/AA plus the functional claims).

Superseded, so closing.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.