-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Circuit Relay Integration #4090
Comments
@vyzo should we close this? or use it as a place to track information about further relay integrations? |
Up to you. The basic issue has been resolved, but we do need a place to track further integration information, so we can keep it open. |
@whyrusleeping @vyzo Should this be closed? |
once project flare is fully deployed, yes |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Type: Feature
Severity: Medium
Description:
Circuit Relay provides us with the means to indirectly connect peers who cannot directly connect to each other, either because of NAT or because of protocol incompatibilities (eg: js interop).
The relay specification has been implemented in Go as a transport in go-libp2p-circuit.
Integration approach:
Per discussion with @whyrusleeping:
For initial deployment, the relay functionality should be purely manual: peers would have to manually connect to relays and explicitly open connections to each other by directly using
/p2p-circuit
addresses withipfs swarm connect
.The relay transport should be enabled by default, with hop relay functionality an opt-in feature.
No relay addresses should be announced by the host through the DHT, until we better understand the heuristics for automatically using them
The text was updated successfully, but these errors were encountered: