Delegated Routing

[daviddias]

Following ipfs/team-mgmt#492

Tasks:

• Expose findPeers and findProovs in the Gateway
• Create module that exposes:
  • Peer Routing - https://github.com/libp2p/js-libp2p-delegated-peer-routing
  • Content Routing - https://github.com/libp2p/js-libp2p-delegated-content-routing

[daviddias]

@lgierth any update on the first task of the list?

[daviddias]

@lgierth mind updating this issue with what we discussed and the latest developments? Thank you!

Here are my notes:

• expose dht/findpeer, dht/findprovs, swarm/connect, refs commands
  • gateway: expose commands for js-libp2p delegated routing ipfs/kubo#4595
• implement dht/putpeer command
• issue for "awesome delegated routing" endeavour
• update libp2p interfaces: peer-routing and content-routing
• comment on js-ipfs relay plans
  • announce /p2p-circuit addrs
  • configure static list of ~20 well-known relay nodes, pick 2
• debug /wss connection death bug
  • check out js-ipfs bootstrapper tests

[daviddias]

A couple more notes.

The Peer Routing flows will use the findPeer call directly. While the Content Routing flow will be:

• for providing:
  • Ask the delegated peer to fetch the content
  • Ask the delegated peer to become a provider (which happens by fetching the content in the first place)
• for finding providers
  • Ask the delegated peer to tell us who is providing
  • Ask the delegated peer to fetch that data
  • Fetch the data from the delegated peer.

[RangerMauve]

Where are the specs for this functionality?

[dignifiedquire]

Implementations are being done here:

• feat: initial implementation js-libp2p-delegated-peer-routing#1
• [WIP] feat: initial implementation js-libp2p-delegated-content-routing#1