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

Support maintaining multiple network configs #19

Open
bmcd opened this issue Nov 13, 2019 · 1 comment
Open

Support maintaining multiple network configs #19

bmcd opened this issue Nov 13, 2019 · 1 comment
Labels
enhancement New feature or request

Comments

@bmcd
Copy link
Contributor

bmcd commented Nov 13, 2019 •
edited by Krish1979

Screen Shot 2019-11-13 at 11 13 50 AM

Screen Shot 2019-11-13 at 11 13 37 AM

Add the ability to keep the connection information of multiple nodes. This will make it easy to switch between nodes quickly, like when you are playing around with privateFor in the 7nodes example.

I don't know what the edit screen will look like yet, but probably:

  • Name
  • Geth RPC url
  • Tessera 3rd party url (optional)
  • Private From/For Keys (fetched from server if using the tessera url)

Deployed contracts should probably be saved and reloaded on network switch like in #10.
@bmcd bmcd added the enhancement New feature or request label Nov 13, 2019
@bmcd bmcd mentioned this issue Nov 13, 2019
Closed
@bmcd
Copy link
Contributor Author

bmcd commented Mar 19, 2020

Some more mockups:

Multiple Networks 1
Multiple Networks 2
Multiple Networks 3
Multiple Networks 4
Multiple Networks 5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bmcd