Skip to content

feat: signed peer records data types #681

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.

Sign up for GitHub

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

Merged
vasco-santos merged 7 commits into from
Jul 15, 2020
Merged

feat: signed peer records data types #681

Changes from 1 commit
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
aa423ff
feat: signed peer records record manager
vasco-santos Jun 3, 2020
e7356a0
chore: apply suggestions from code review
vasco-santos Jun 24, 2020
19c9c24
chore: refactor and better docs
vasco-santos Jun 24, 2020
5a7b8de
fix: signature compliant with spec
vasco-santos Jun 26, 2020
b4fa13a
chore: address review
vasco-santos Jul 15, 2020
08b086e
chore: update pending deps
vasco-santos Jul 15, 2020
55d63bf
chore: apply suggestions from code review
vasco-santos Jul 15, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
chore: apply suggestions from code review 
Co-authored-by: Jacob Heun <[email protected]>
  • Loading branch information
@vasco-santos @jacobheun
vasco-santos and jacobheun authored Jul 15, 2020
commit 55d63bf7d6f7fc57d6a9c7e96ad7084d45060e7d
2 changes: 1 addition & 1 deletion src/record/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,7 +60,7 @@ const rec = ExampleRecord.createFromProtobuf(e.payload)

All libp2p nodes keep a `PeerStore`, that among other information stores a set of known addresses for each peer, which can come from a variety of sources.

Libp2p peer records were created to enable the distribution of verifiable address records, which we can prove originated from the addressed peer itself. With such guarantees, libp2p is able to prioritize addresses based on their authenticity, with the most strict strategy being to only dial certified addresses (no strategies implemented at the time of writing).
Libp2p peer records were created to enable the distribution of verifiable address records, which we can prove originated from the addressed peer itself. With such guarantees, libp2p is able to prioritize addresses based on their authenticity, with the most strict strategy being to only dial certified addresses (no strategies have been implemented at the time of writing).

A peer record contains the peers' publicly reachable listen addresses, and may be extended in the future to contain additional metadata relevant to routing. It also contains a `seqNumber` field, a timestamp per the spec, so that we can verify the most recent record.

Expand Down