Paul Miller

Creator of proposal mentioned they could engage auditors; and I told them that the library should be tested somewhere before audit, because if, while testing, some changes would become necessary,...

it's done https://github.com/paulmillr/scure-sr25519/tree/main/audit

@valentinfernandez1 feel free to take over the PR.

I wanted to make all my packages ESM-only+node20+, since node.js v20.19+ finally supports loading ESM modules from Common.js. And most people seem to be using babel / other transpilers anyway....

In fact, the only high-level thing changed from (already-released) sr25519 v0.2.0 is the RNG commit, which is really low-severity. I suggest using 0.2.0, if node v18 support is a must-have;...

just send me an email, you have it in my profile, no need to complicate anything

and why would you not post the issue publicly if it's only related to this particular PR? The pr has not been merged so it doesn't matter if the issue...

saw the issue and replied by email, to reiterate: not a big deal, we can proceed.

this also needs to be updated to most recent 0.3.0 (or 0.2.0, if node v18 support is a must-have)

I will dive into that. To ease the ramp up, could you please share a specific code sample & vector that fails?