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

Composable DHT Open Questions #69

Open
dennis-tra opened this issue Jul 24, 2023 · 0 comments
Open

Composable DHT Open Questions #69

dennis-tra opened this issue Jul 24, 2023 · 0 comments

Comments

@dennis-tra
Copy link
Contributor

During our Paris meeting, we went through the composable DHT design page and had a couple of questions.

  • Do we really need to learn the feature preference list of the remote peer? We don't think so
  • Couldn't the identify protocol serve as a feature discovery? -> it would be great if we could avoid inventing a new protocol for feature discovery
  • Generally, the Feature/Protocol search must be clarified
    • Currently, FIND_NODE requests will return any nodes in the routing table of the remote peer and not necessarily the ones that support the feature that I'm searching for
    • sparsly populated features will be hard to find
  • This could be solved with two not-really satisfying ways. Add a new FIND_NODE_WITH_FEATURE protocol. Connect to all peers that get returned from a FIND_NODE RPC.
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