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

Discussion on where sui network start/stop/genesis should occur in Rest Server #553

Closed
arun-koshy opened this issue Feb 24, 2022 · 1 comment
Assignees

Comments

@arun-koshy
Copy link
Contributor

For context, as part of the GDC deliverables we have been pushing to get a game demo created that interacts with the sui network via rest endpoints. To do this we are hosting a rest server on AWS for the game developers to use. This rest server (PR#454) currently exposes network related endpoints (start/stop/genesis of sui) so that the developers can start and stop the network as they see fit. This has caused some confusion as this is not something that would typically be done in a Rest Server.

Post GDC the rest server should operate independently of the Sui Network startup/genesis. However this is only the case if we have a shared network that clients will all be using. It is also possible that we are going to be allowing game developers to all spawn up their own networks in which case maybe the rest server binary would include startup/genesis code.

This issue is to clarify what the expectations are of the Sui network moving forward and how the Rest Server can properly be designed around that.

@arun-koshy
Copy link
Contributor Author

Completed in PR#1123 which removed start/stop/genesis from Rest Server

mwtian pushed a commit that referenced this issue Sep 12, 2022
mwtian pushed a commit to mwtian/sui that referenced this issue Sep 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants