ResNetLab was present at Open Tech Will Save Us virtual meetup, an event organized by the Matrix.org team during which participants could watch a live stream provided by Jitsi and ask questions using the Matrix protocol (often through a client like Riot).
Matrix is both a project and an ecosystem that focuses on providing secure and federated platform for all types of communication. We are big fans of Matrix at Protocol Labs, both taking inspiration from their innovations (e.g. the Olm and MegaOlm cryptographic ratchets) and bridging the IPFS and libp2p IRC channels with Matrix.
Back to the meetup. I delivered a talk on the recent updates on the Gossipsub protocol, one of the most scalable P2P PubSub solutions, whose recent v1.1 release includes additional security-hardening features. In this talk, you can learn about:
- The motivation for P2P PubSub
- libp2p PubSub and its evolution from Floodsub to Gossipsub
- Gossipsub v1.0
- Gossipsub v1.1 and the new security-hardening features
- The Gossipsub testing infrastructure
For those who couldn’t be present, the Matrix team made the recording available. We’ve also made the slide deck available.
There were a number of interesting questions from the audience. You can watch the Q&A portion of the recording or read the summary below.
Q: If one uses two different libp2p implementations, will they share the same network?
A: By default, yes. We call the default network the “Main Network” and this is shared between libp2p, IPFS, and other protocols that started relying on it. If you’d like to have a disjoint network, you achieve it in a few ways:
- Isolate your nodes using a firewall so they cannot connect to the outside world (the traditional way).
- Change the config of your libp2p/IPFS node to not use the default bootstrapper nodes. If you don’t connect to the bootstrappers or any of the other nodes in the main network, your node will be unable to find the network by itself.
- Use a libp2p-pnet. Essentially, with libp2p-pnet, you configure a PSK (pre-shared key) on the nodes that you want on your disjoint network. Once they find other nodes, they will run a special handshake that only peers that have the same PSK can complete. You can watch Jacob Heun’s talk at the IPFS Dev Meetings, in which he demonstrates this feature.
Q: How much work is it to use Gossipsub / libp2p PubSub in an application?
Q: How do the rules for the message validators get expressed?
A: Today, these are simply expressed programmatically using a message handler pattern. We went a bit mad-science/sci-fi on this one, so maybe it’s best to watch the related passage.
Q: How do you reconcile the initial goal of a real-time protocol with the eventual consistency of Gossip?
A: Instead of making a decision for the user, what we do is provide as much power to the user as possible, along with recommendations on how to set the right parameters for the different types of interaction patterns and network scales.
Q: Does Gossipsub have presence support?
A: Not by default. This has to be built by the application, but requires establishing a link between the keys that identify the user and the keys that identify the user’s nodes.
I recommend watching the other two talks in this event! You can learn more about:
- How Jitsi scaled from 10s to 1000s of Servers to provide an invaluable communication service during the COVID-19 pandemic
- How Matrix.org figured out the UX to deploy full end-to-end encryption for all of its users
We really appreciate the invitation. It was a fun way to catch up and learn about some of the projects that inspire us, while also getting to see the people that we’d normally be meeting in in-person events. Thank you and looking forward to the next one!