Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: use native crypto if available #385

Merged

Conversation

achingbrain
Copy link
Collaborator

@achingbrain achingbrain commented Nov 10, 2023

Adds the lodestar crypto implementation to this module for use in node.

I'm trying to get js-libp2p back onto the libp2p performance dashboard and in local testing this change increases streaming throughput from around 60 MB/s to almost 300 MB/s.

Adds the lodestar [crypto
implementation](https://github.com/ChainSafe/lodestar/blob/6f27ac6e5f439577906cbfe5f9e01c59586c2af3/packages/beacon-node/src/network/libp2p/noise.ts#L3) to this module
for use in node.

I'm trying to get js-libp2p back onto the [libp2p performance dashboard](https://observablehq.com/@libp2p-workspace/performance-dashboard) and in testing this change
increases streaming throughput from around 60 MB/s to almost 300 MB/s.
@achingbrain achingbrain requested a review from a team as a code owner November 10, 2023 06:57
src/crypto/index.ts Outdated Show resolved Hide resolved
@mpetrunic mpetrunic merged commit 3dee1dc into ChainSafe:master Nov 10, 2023
13 checks passed
@achingbrain achingbrain deleted the fix/use-native-crypto-if-available branch November 10, 2023 17:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants