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

Signed Peer Records #653

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

Signed Peer Records #653

vasco-santos opened this issue Jun 2, 2020 · 1 comment
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

libp2p/specs#217

Background

A libp2p node shares its data publicly (e.g through the DHT) or relies on potentially untrustworthy intermediaries to relay information. This might have consequences as the peer data can be tempered by a third party.

A Signed Peer Record is an all-purpose data container that includes a signature of the data, so we can verify that the data came from a specific peer and that it hasn't been tampered with.

Milestones

Milestone Issue PR
1) Implementation of Signed Peer Records N/A #681
2) Identify protocols use Signed Peer Records N/A #682
3) Certified Address Book N/A #683
4) Pubsub routers use Signed Peer Records N/A TODO
@vasco-santos vasco-santos added Epic 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