Switch from js-sha3 and blake to audited noble-hashes

[paulmillr]

noble cryptography (https://github.com/paulmillr/noble-hashes) is high-security, easily auditable set of contained cryptographic libraries and tools. It would be great to use it instead of some unknown library. Benefits:

• Audited, less resources would be necessary for end-users to audit dep trail
• Smaller bundle size
• Is used by millions of users (see npm)
• Since it's everywhere (e.g. in ethers.js), it would get de-duplicated by end-users when two packages depend on noble
• Is actually maintained, has modern features like esm / typescript / bun / deno friendliness

All PRs:

• PR to snarkjs for only sha3 Switch from js-sha3 to audited noble-hashes #546
• PR to snarkjs for sha3 and blake2 Switch from js-sha3 and blake to audited noble-hashes #547
• PR to wasmsnark Switch from blakejs to audited noble-hashes wasmsnark#32
• PR to circomlib Switch from blake-hash to audited noble-hashes circomlib#119
• PR to circomlibjs Switch from blake-hash and blake2b to audited noble-hashes circomlibjs#32

Originally proposed 15 months ago in #416

[OBrezhniev]

Hello @paulmillr!
Thank you for your contribution! I imagine it was a lot of work!
Can you please elaborate on this comment? Why is it unsafe?
Just because of the usage of internal API or there are other considerations?

[paulmillr]

It’s because it uses internal api.

stuff like this is never exposed in libraries.

[paulmillr]

Why do you need "partial hashes"?

[OBrezhniev]

@Kolezhniuk can you please test this build on our multiplatform tests setup?