-
Notifications
You must be signed in to change notification settings - Fork 14
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
Update go-libp2p and redeploy #26
Comments
@aschmahmann As part of this task (are you taking this on?) can we also document the deployment process, and maybe automate it as well? |
Note: While not strictly required we may also want to update the backend to send back enough information for the user to learn that the only addresses they were reachable on were upgraded relay connections and then update the frontend to explain the tradeoffs with having a node only reachable via upgraded relay connections. |
Fixed by #35 |
go-libp2p has been updated and resolved a number of issues around WSS as well as Circuit Relay v2 usage (e.g. not getting issues with trying to use transient connections for non-DCuTR data like Bitswap requests). This repo needs to be correspondingly updated and the backend redeployed.
The text was updated successfully, but these errors were encountered: