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!

[ghost]

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

[jacobheun]

Both libp2p/js-libp2p-delegated-peer-routing and libp2p/js-libp2p-delegated-content-routing are about ready for release. I've got a local branch I am working on to integrate those into libp2p. The biggest issue right now is that https://ipfs.io is not working for those two.

I will make sure the local tests aren't hitting external endpoints, but the default peer and content routing won't work until ipfs.io is fixed.

I'll make sure the endpoint is configurable. Do we have any expected eta on a fix or separate url for the ipfs.io delegate?

[ghost]

The biggest issue right now is that https://ipfs.io is not working for those two.

Ah yeah, there's a branch that needs merging. I'll be on it once the urgent DWeb Summit tasks are done.

[daviddias]

@jacobheun this is shipped, right?

[jacobheun]

@diasdavid this will ship with 0.24. The go-ipfs work is still not complete, but our support will be there in the next release.

[daviddias]

@jacobheun what's the go-ipfs work? @Stebalien can you help with this?

[jacobheun]

The outstanding PR in go-ipfs is ipfs/kubo#5565.
Once that is release we can get infra to deploy, ipfs/infra#426.

[vasco-santos]

This is done

[daviddias]

@vasco-santos is it tested, deployed and monitored?

[vasco-santos]

It is implemented, tested and deployed afaik (ipfs/js-ipfs/ipfs#configuring-delegate-routers).

Anyway, the scope of this issue seems to be the implementation on js-libp2p, which is released and tested. I suggest that we start to create more scoped issues, otherwise there is no visibility on what is done and what is expected from the issue. I am going through the issues on js-libp2p and there are several issues on this situation.

If we want to have this service monitored, it should live under its specific issue