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

Kademlia DHT for multi-hop relay/NAT traversal #108

Closed
robert-cronin opened this issue Sep 17, 2020 · 1 comment · Fixed by #118
Closed

Kademlia DHT for multi-hop relay/NAT traversal #108

robert-cronin opened this issue Sep 17, 2020 · 1 comment · Fixed by #118
Assignees
Labels
development Standard development

Comments

@robert-cronin
Copy link
Contributor

This is kind of a cleanup as well as an extension of existing features. At the moment we have a NAT traversal based on public peers but a polykey node can have only one relay peer set. We want this to be completely abstracted away from the user.

Kademlia will provide this ability. Any node can act as a relay peer. Kademlia is usually used for content routing but in our situation, the content will be public keys of polykey nodes.

@robert-cronin robert-cronin added development Standard development cleanup labels Sep 17, 2020
@robert-cronin robert-cronin self-assigned this Sep 17, 2020
@CMCDragonkai
Copy link
Member

The "relay" is just an ephemeral concept used encapsulated inside the pk system. It should never be exposed to the end user. The end user should not need to specify anything or know anything about relays UNLESS it's a special circumstance, or the user is doing something custom. Like ourselves Matrix AI.

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

Successfully merging a pull request may close this issue.

2 participants