⚡️ 0.24 RELEASE 🚀

[jacobheun]

Delegated Peer/Content Routing Support and improved control of Libp2p nodes are coming!

🗺 What's left for release

• Custom Content/Peer Routing Support
• Relay enabled by default
• Libp2p as a State Machine

🔦 Highlights

🚦 Custom Content/Peer Routing Support

Libp2p will now support custom content and peer routers, which will enable users to better customize their DHT experience. The new release allows for using the new Delegated Peer Routing and Delegated Content Routing modules to leverage an external nodes DHT instead of or in conjunction with their own. This enables nodes in more resource restricted environments to use an external DHT instead of running their own, which can be very resource intensive.

🔌 Relay enabled by default

In an effort to improve default connectivity, circuit relay is now enabled by default. Hop is still disabled by default to prevent relaying traffic for other nodes out of the box, as this is expensive for the node. By enabling circuit relay by default, nodes will now be able to accept and dial to other circuit relay nodes. This improves a nodes default ability to communicate in isolated environments.

🤖 State Machine

Libp2p is now a state machine. When starting and stopping the node you can now listen for the stop and start events. Libp2p also exposes a new method, dialFSM, which calls back with a Connection State Machine. This gives users the ability to listen to more events on individual connections. You can find out more about these events in libp2p-switch readme.

🏗 API Changes

• Added method dialFSM(peer, protocol, callback) which allows users to hook into more connection level activity. You can read more about in the readme.
• Libp2p now emits start and stop events on node start and stop respectively.
  • Callbacks for .start() and .stop() are now optional. You can instead listen to the error, start, and stop events.

✅ Release Checklist

• Robustness and quality
  • Ensure that all tests are passing, this includes:
    • unit
  • Run tests of the following projects with the new release:
    • js-ipfs
• Documentation
  • Ensure that README.md is up to date
  • Ensure that all the examples run
• Communication
  • Create the release issue
  • Announcements (both pre-release and post-release)
    • Twitter
    • IRC
    • Reddit
  • Blog post

🙌🏽 Want to contribute?

Would you like to contribute to the libp2p project and don't know how? Well, there are a few places you can get started:

• Check the issues with the help wanted label at the Ready column in our waffle board - https://waffle.io/libp2p/js-libp2p?label=help%20wanted
• Join an IPFS All Hands, introduce yourself and let us know where you would like to contribute - https:/ipfs/team-mgmt#weekly-ipfs-all-hands
• Hack with IPFS and show us what you made! The All Hands call is also the perfect venue for demos, join in and show us what you built
• Join the discussion at http://discuss.ipfs.io/ and help users finding their answers.
• Join the ⚡️ⒿⓈ Core Dev Team Weekly Sync 🙌🏽 and be part of the Sprint action!

⁉️ Do you have questions?

The best place to ask your questions about libp2p, how it works and what you can do with it is at discuss.ipfs.io. We are also available at the #libp2p channel on Freenode.

[jacobheun]

Release Candidate 0.24.0-rc.1 has been published to npm and can be installed via npm i libp2p@next. We'll be doing integration testing this week to make sure there are no regression issues.

[daviddias]

What's the ETA on this one?

[jacobheun]

I'm fixing some issues with the examples and working on a dependency issue with libp2p-spdy. This should get released tomorrow at the latest!

[jacobheun]

Release candidate 0.24.0-rc.3 has been published to npm and can be installed via npm i libp2p@next. If you run into issues, let us know. This should be fully backwards compatible with 0.23.

[jacobheun]

0.24 is out! https://ipfs.io/blog/55-js-libp2p-0-24/

[daviddias]

@jacobheun @vasco-santos mind following up with agoric-labs/PlaygroundVat#8 given that the 0.24 released happened? :)