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

Merge gateway and provider nodes #192

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

Merge gateway and provider nodes #192

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

Comments

@futurechimp
Copy link
Contributor

I guess it'd be simpler to copy the current gateway websocket code into the sfw-provider, and rename the latter to gateway, than to go the other way? I can see advantages of going either way, but that seems like it'll disturb the lowest number of things.

This issue is just to get the basics running so that the WASM client can still send mixnet packets to a merged codebase.
@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 self-assigned this Apr 21, 2020
@futurechimp futurechimp moved this from Backlog to In progress in Core systems Apr 21, 2020
@jstuczyn jstuczyn mentioned this issue Apr 29, 2020
Merged
Core systems automation moved this from In progress 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

@jstuczyn jstuczyn

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
2 participants
@futurechimp @jstuczyn