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

Overhaul libp2p-crypto #586

Closed
vasco-santos opened this issue Mar 11, 2020 · 1 comment
Closed

Overhaul libp2p-crypto #586

vasco-santos opened this issue Mar 11, 2020 · 1 comment
Labels
exp/wizard Extensive knowledge (implications, ramifications) required kind/enhancement A net-new feature or improvement to an existing feature status/ready Ready to be worked

Comments

@vasco-santos
Copy link
Member

  • Version: N/A
  • Platform: N/A
  • Subsystem: N/A

Type: Enhancement

Description:

One of the pain points of development within a browser context is the bundle size of a web app, which easily gets quite big and makes web pages take longer times to run. In js-libp2p land, we have been working over the last months on reducing the bundle size of the library to the minimum possible, so that js-libp2p users in the browser don't need to have a large bundle size just for using this library.

One of the outstanding issues to have our bundle size in a considerably good shape is the crypto libraries that we need to carry. The JS ecosystem around cryptography is far from perfect, which has made us use several different libraries to achieve different cryptographic primitives.

Taking into account that libp2p is a composable and modular stack, most of the times js-libp2p bundle contains heavy crypto code that is not needed. In this context, js-libp2p crypto should be modular and pluggable, so that the users can bring just what they need instead of the all thing.

@maschad
Copy link
Member

maschad commented Sep 28, 2023

Moving conversation to #2086

@maschad maschad closed this as completed Sep 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
exp/wizard Extensive knowledge (implications, ramifications) required kind/enhancement A net-new feature or improvement to an existing feature status/ready Ready to be worked
Projects
None yet
Development

No branches or pull requests

2 participants