chore: update libp2p-crypto

[achingbrain]

libp2p-crypto@0.20.0 uses noble-ed25519 and noble-secp256k1 which
is smaller and faster than the version in https://www.npmjs.com/package/secp256k1

This PR updates the dep so we don't pull in 0.19.x and 0.20.x in
consuming bundles.

Ref: libp2p/js-libp2p-crypto#202

[codecov-commenter]

Codecov Report

Merging #113 (50b9330) into master (735f287) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #113   +/-   ##
=======================================
  Coverage   89.13%   89.13%           
=======================================
  Files          16       16           
  Lines        1832     1832           
  Branches      243      243           
=======================================
  Hits         1633     1633           
  Misses        199      199           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 735f287...50b9330. Read the comment docs.

[dapplion]

Would be nice to benchmark and consider using native bindings for Lodestar at least

[achingbrain]

@dapplion native bindings are much, much faster 😁 , though require node 15+ - libp2p/js-libp2p-crypto#211

This is ok, I think, as officially libp2p supports LTS+Current which as of a couple of weeks ago is 16 and 17.

Actually, scratch that, I updated the libp2p-crypto PR to fall back to the pure-js implementation if Ed25519 isn't supported.

[dapplion]

@dapplion native bindings are much, much faster grin , though require node 15+ - libp2p/js-libp2p-crypto#211

This is ok, I think, as officially libp2p supports LTS+Current which as of a couple of weeks ago is 16 and 17.

Actually, scratch that, I updated the libp2p-crypto PR to fall back to the pure-js implementation if Ed25519 isn't supported.

Oh! Very interested! gossip encryption shows up in our Lodestar benchmarks. Do you have benchmarks comparing native bindings, current lib and noble's? We just bumped Lodestar to use NodeJS v16 by default so it shouldn't be an issue 👍

[dapplion]

@dapplion native bindings are much, much faster grin , though require node 15+ - libp2p/js-libp2p-crypto#211

This is ok, I think, as officially libp2p supports LTS+Current which as of a couple of weeks ago is 16 and 17.

Actually, scratch that, I updated the libp2p-crypto PR to fall back to the pure-js implementation if Ed25519 isn't supported.

Oh! Very interested! We just bumped Lodestar to use NodeJS v16 by default so it shouldn't be an issue 👍

Damn with those benchmarks, crazy differences

[achingbrain]

Superseded by #115

[achingbrain]

And/or #116