Sync with upstream

[jojobyte]

This synchronizes our fork with the upstream version and should update the IIFE version to have the latest changes.

Breaking changes to be aware of:

• No longer exist:
  • Secp256k1.utils._normalizePrivateKey
  • Secp256k1.utils._bigintTo32Bytes
  • Secp256k1.utils.mod
  • Secp256k1.Point.BASE.multiplyAndAddUnsafe
    • Updated to use:
      • Secp256k1.utils.normPrivateKeyToScalar
      • Secp256k1.etc.numberToBytesBE
      • Secp256k1.etc.mod
      • Secp256k1.ProjectivePoint.BASE.mulAddQUns
• Now exports ProjectivePoint instead of Point, although I included both in our IIFE wrapper.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@noble/[email protected]	None	0	773 kB	paulmillr
npm/@paulmillr/[email protected]	None	0	6.12 kB	paulmillr
npm/[email protected]	None	+1	1.32 MB	ndubien
npm/[email protected]	None	0	9.58 kB	paulmillr
npm/[email protected]	environment	0	10.3 kB	paulmillr
npm/[email protected]	environment, eval Transitive: filesystem, shell	+11	4.12 MB	fabiosantoscode
npm/[email protected]	None	0	21.9 MB	typescript-bot

🚮 Removed packages: npm/@noble/[email protected], npm/@rollup/[email protected], npm/@rollup/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]

View full report↗︎

[coolaj86]

Since this is a major version change and major breaking change, and it's tracking a different repo, I think it makes more sense to save the current main as v1 and overwrite main with this v2 direct from the source repo, with a single commit overlaying the changes.

I think I can do that...

[jojobyte]

@coolaj86 That is more or less what this is doing just with tweaks to package.json & github workflow scripts.

[coolaj86]

@jojobyte Do we still need to maintain a fork with the new version? Or will it work without our modifications now?

[jojobyte]

@coolaj86 Do you mean if we're switching to ESM Imports by default and dropping IIFE/require? Not sure, but I can test it if that is what you're asking.

We may need to update our repos depending on the fork though to the import instead of require if you haven't already.