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.

Sign up for GitHub

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

Jump to bottom

Desktop Client should attach to gateway websocket #193

Closed
futurechimp opened this issue Apr 21, 2020 · 0 comments · Fixed by #208
Closed

Desktop Client should attach to gateway websocket #193

futurechimp opened this issue Apr 21, 2020 · 0 comments · Fixed by #208
Projects
Core systems
Milestone
0.7.0

Comments

@futurechimp
Copy link
Contributor

The desktop client currently uses TCP sockets to connect to the provider. It should go to the (new) gateway node and use websockets.

Let's have it connect to the same websocket that the wasm client uses, and prepend first mixnode address to the sent Sphinx packet in the same way that the wasm client does.
@futurechimp futurechimp added this to the 0.7.0 milestone Apr 21, 2020
@futurechimp futurechimp added this to Backlog in Core systems via automation Apr 21, 2020
@jstuczyn jstuczyn mentioned this issue Apr 29, 2020
Merged
Core systems automation moved this from Backlog to Done Apr 30, 2020
@snyk-bot snyk-bot mentioned this issue Jan 4, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
Core systems
Archived in project
Core systems
  
Done
Milestone
0.7.0
Development

Successfully merging a pull request may close this issue.

Feature/gateway provider merge nymtech/nym
1 participant
@futurechimp