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

Gossipsub v1.1 #652

Closed
vasco-santos opened this issue Jun 2, 2020 · 2 comments
Closed

Gossipsub v1.1 #652

vasco-santos opened this issue Jun 2, 2020 · 2 comments
Labels
Epic P1 High: Likely tackled by core team if no one steps up status/ready Ready to be worked

Comments

@vasco-santos
Copy link
Member

vasco-santos commented Jun 2, 2020

https://github.com/libp2p/specs/blob/master/pubsub/gossipsub/gossipsub-v1.1.md

Background

Gossipsub is a pubsub router implementation that succeeded Floodsub as the default pubsub router for libp2p and IPFS. Over the last months, the IPFS/libp2p teams have been working on extending the initial version of gossipsub to improve bootstrapping and protocol attack resistance. The extensions change the algorithms that prescribe local peer behaviour and are fully backwards compatible with v1.0 of the protocol. Peers that implement these extensions, advertise v1.1 of the protocol using /meshsub/1.1.0 as the protocol string.

References:

Milestones

Milestone Issue PR
0) Refactor Pubsub base protocol N/A ChainSafe/js-libp2p-gossipsub#74
1) Support topic validators N/A ChainSafe/js-libp2p-gossipsub#75
2) Full gossipsub v1.1 implementation N/A TODO
3) Integrate signed peer records TODO TODO
4) Integration on libp2p and ipfs, with interop tests running N/A TODO

libp2p/js-libp2p-pubsub#67

@vasco-santos
Copy link
Member Author

cc @wemeetagain

I created this Issue to track the gossipsub update work and provide visibility for the libp2p@0.29 release work. Feel free to change/decouple milesones if it is easier for your side. Meanwhile, we are going to start working on the signed peer records as we need this to gossipsub and rendezvous (#651).

@vasco-santos vasco-santos added P1 High: Likely tackled by core team if no one steps up status/ready Ready to be worked labels Jun 2, 2020
@jacobheun
Copy link
Contributor

Done and released in 0.29 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Epic P1 High: Likely tackled by core team if no one steps up status/ready Ready to be worked
Projects
None yet
Development

No branches or pull requests

2 participants