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

The credentials for btcd should be saved by default #30

Open
davecgh opened this issue Feb 15, 2016 · 2 comments
Open

The credentials for btcd should be saved by default #30

davecgh opened this issue Feb 15, 2016 · 2 comments

Comments

@davecgh
Copy link
Member

davecgh commented Feb 15, 2016

Ideally the credentials for btcd should be saved and the connection dialog only shown if the saved credentials are invalid.

@jrick
Copy link
Member

jrick commented Feb 16, 2016

We could save the credentials and autofill the dialogs, but i don't want to perform autoconnect since that prevents you from using another btcd if you wanted to for some reason. This is assumming btcd is left unmanaged by Paymetheus. If it's started by Paymetheus as a service, that's another story, and could be made even more streamlined by removing the prompt altogether.

@davecgh
Copy link
Member Author

davecgh commented Feb 16, 2016

That makes sense. As discussed in IRC, I do think managing btcd from Paymetheus would be the best case. Along these same lines, I don't imagine it would be overly difficult to allow a flag to specify a remote btcd instance which uses the code that already exists today.

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