[WIP] Roadmap

[cheatfate]

Cryptography

• NIST P-256/384/521 curves, required to perform DHE.
• NIST P-256/384/521 ECDSA required for peer identification.
• RSA required for peer identification
• ED25519 required for peer identification
• SECP256k1 required for peer identification
• ASN.1 DER encoder/decoder for (ECDSA, RSA public keys/private keys/signatures)
• Key interface
• Curve25519 required for noise-libp2p
• Poly1305 required for noise-libp2p
• ChaCha20 required for noise-libp2p

https://github.com/libp2p/go-libp2p-crypto

Network Interfaces

• https://github.com/libp2p/go-addr-util

Storage and utility

• https://github.com/libp2p/go-libp2p-peerstore
• https://github.com/libp2p/go-libp2p-peer

Protocol negotiation

• https://github.com/multiformats/go-multistream
• https://github.com/libp2p/go-conn-security-multistream

Stream Multiplexer

• https://github.com/libp2p/go-stream-muxer
• https://github.com/libp2p/go-mplex (baseline multiplexer supported by most implementations)
• Additional multiplexers that different implementations support - can be implemented when the need arises
  • https://github.com/whyrusleeping/go-smux-yamux
  • https://github.com/whyrusleeping/go-smux-muxado
  • https://github.com/whyrusleeping/go-smux-multiplex
  • https://github.com/whyrusleeping/go-smux-spdystream

Connections

• https://github.com/libp2p/go-conn-security
• https://github.com/libp2p/go-libp2p-secio
• noise-libp2p (Standardise Noise handshake for libp2p libp2p/specs#195, Draft of noise-libp2p spec libp2p/specs#202)

Connection manager

• https://github.com/libp2p/go-libp2p-interface-connmgr

Transports

• https://github.com/libp2p/go-libp2p-transport
• https://github.com/libp2p/go-libp2p-transport-upgrader
• https://github.com/libp2p/go-tcp-transport

Protocols

• https://github.com/libp2p/go-libp2p-protocol
• https://github.com/libp2p/go-libp2p/tree/master/p2p/protocol/identify (base protocol)
• https://github.com/libp2p/go-libp2p/tree/master/p2p/protocol/ping (base protocol)
• https://github.com/libp2p/go-libp2p-pubsub (required for Ethereum2)

Name resolution

• https://github.com/libp2p/go-libp2p-kad-dht (this is actually protocol as all the above).
• Discovery version 5

Metrics

• https://github.com/libp2p/go-libp2p-metrics
• https://github.com/libp2p/go-flow-metrics

Swarm

This is actually main loop of any libp2p node which performs all the logic

• https://github.com/libp2p/go-libp2p-swarm

[arnetheduck]

Related eth2 ticket: ethresearch/p2p#4

[sinkingsugar]

About Curve25519 if @cheatfate and @dryajov agree I can refactor the current ed25519 code which actually includes (not sure if entirely) Curve25519, although very scalar code.
We also need X25519 for noise btw, again depends on Curve25519.
Let me know what you guys think please.
Or actually including a more optimized C library (since C is nim's assembly) could be another option.

[cheatfate]

@sinkingsugar we do not need optimized C library, because we already has one - nim-bearssl.

Also i'm not sure what you mean under word refactor, because ed25519 is constant-time implementation and so i'm not sure it needs any refactor process. For some reason ed25519 is not part of TLS standard, while Curve25519 is, so i'm not sure is ed25519 implementation is enough to build Curve25519.

[sinkingsugar]

@cheatfate I used bearssl fully anyway so don't worry about it!

[Menduist]

Closing this since almost everything on this list is done now (except exotic multiplexers)