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

Peer Discovery For Graphsync Metadata Request #2

Open
hannahhoward opened this issue Mar 30, 2022 · 0 comments
Open

Peer Discovery For Graphsync Metadata Request #2

hannahhoward opened this issue Mar 30, 2022 · 0 comments

Comments

@hannahhoward
Copy link
Collaborator

hannahhoward commented Mar 30, 2022

What

To kick off a lightning storm request, we need to make a Graphsync metadata request(s) to a peer who has the content. But even before that, we need to discover which peer has the content.

There are a couple ways we could do this:

  • Utilize Bitswap sessions to broadcast the initial want-haves, and expose the sessions ([ipfs/go-bitswap] Exposing the session peers boxo#75)
  • Just start with a metadata graphsync request to all local peers (not clear how much duplicate data this actually is)
  • Just start with a metedata graphsync request for the root block with a pure matcher selector to limit duplication (not actually a great one-block selector as large bytes nodes could get auto traversed)
  • Build an actually graphsync want-have protocol, or peer discovery protocol

The approaches merits further discussion and this ticket should be done after Lightning-Storm has been proven out in testbeds

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant