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

noencryptwallet does not display seed #1832

Closed
sputn1ck opened this issue Sep 3, 2018 · 4 comments
Closed

noencryptwallet does not display seed #1832

sputn1ck opened this issue Sep 3, 2018 · 4 comments

Comments

@sputn1ck
Copy link
Collaborator

sputn1ck commented Sep 3, 2018

Background

when creating a lnd environment with noencryptwallet set, the wallet gets created without displaying a seed.

Your environment

  • lnd v0.5-beta-rc1
  • windows 10 64-bit
  • bitcoind as backend

Steps to reproduce

start a new lnd with --noencryptwallet

Expected behaviour

the wallet should wait for lncli create

Actual behaviour

the wallet creates a wallet.db without showing a seed

@cfromknecht
Copy link
Contributor

That is expected behavior, remove the --noencryptwallet flag if you require a seed.

@Roasbeef Roasbeef closed this as completed Sep 3, 2018
@jonasnick
Copy link

jonasnick commented Sep 4, 2018

It's not exactly obvious to users that this is expected behavior. Especially first-time users like me who read https://github.com/lightningnetwork/lnd/blob/master/docs/INSTALL.md#disabling-wallet-encryption and dismiss the this argument must only be used for testing purposes as being overly careful. My expectation was that --noencryptwallet just does what it says without affecting backupability. I only realized much later that I've never seen and therefore never backed up the seed. Maybe it would make sense to stress that part in the documentation to reduce a footgun opportunity.

@Roasbeef
Copy link
Member

Roasbeef commented Sep 4, 2018

@jonasnick agreed that we can modify the documentation (even just remove the documentation for that option) to make it less of a foot gun. A related issue to this is: #899, which is to allow the user to input an "empty" passphrase rather than force them to use a non-empty one.

@cfromknecht
Copy link
Contributor

@jonasnick 100% agree that the naming and docs could be improved. I recall bringing this up in the past that the name does not suit the behavior, though the naming stuck and it was not revisited. I've made a PR to help address the confusion as we flesh out a full plan for deprecation.

#1843

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

4 participants