wallet: Restore -usehd=0 option #11582

pull luke-jr wants to merge 1 commits into bitcoin:master from luke-jr:usehd changing 3 files +10 −9
  1. luke-jr commented at 6:49 PM on October 30, 2017: member

    Simply avoiding setting a master key is sufficient to have a non-HD wallet, with the latest wallet version (ie, no-default-key)

    Motivation: I intend to rebase #9662 on top of this, and from there add support for generic external wallet interfaces (such as HD wallets).

  2. wallet: Restore -usehd=0 option
    Simply avoiding setting a master key is sufficient to have a non-HD wallet, with the latest wallet version (ie, no-default-key)
    bab2ddd664
  3. achow101 commented at 7:02 PM on October 30, 2017: member

    Why are non-hd wallets needed for #9662?

  4. luke-jr commented at 7:20 PM on October 30, 2017: member

    Because the goal of #9662 is to not have the internal wallet generating ANY keys. It's to watch specific addresses only.

  5. TheBlueMatt commented at 11:04 PM on October 30, 2017: member

    Please no. We really don't need a combinatoric blowup in the number of supported wallet options and setups. How about instead support having a public-only HD seed (and if none is provided generate one, who cares, you're just watching a few extra addresses that will never be used).

  6. fanquake added the label Wallet on Oct 30, 2017
  7. luke-jr commented at 11:20 PM on October 30, 2017: member

    @TheBlueMatt That assumes all wallets are HD. Additionally, using public derivation is contentious. Finally, watching addresses not part of the real wallet has risks - someone could gain read access to your wallet and send to those addresses, and you'd mistakenly think they were safe on your hardware wallet.

  8. TheBlueMatt commented at 11:22 PM on October 30, 2017: member

    All newly-created wallets will be HD, though, and supporting a matrix of HD, Segwit, Watch-Only, etc, etc and all combinations thereof blows up maintinence complexity a ton. In any case, a watch-only wallet is going to need a mode that forces it to never generate new addresses, so having an HD seed or not having an HD seed wont matter - you still wont get new addresses.

  9. achow101 commented at 12:09 AM on October 31, 2017: member

    Since #9662 should be disabling all forms of key generation, I don't see why you need to have -usehd=0. Why can't you just have a wallet type which has no private keys whatsoever? Instead of doing -usehd=0, you just have -disablehot which then doesn't generate a HD master key or any other key.

  10. luke-jr commented at 12:42 AM on October 31, 2017: member

    @TheBlueMatt Watchonly-only wallets aren't HD. Maintenance complexity isn't affected, because we still need to support non-HD wallets regardless. I see no value in writing an ignored HD seed - it only creates the risk that we accidentally use it rather than crash or fail. @achow101 I suppose that's a possibility, but I don't see the harm in having the option...

  11. morcos commented at 1:15 PM on October 31, 2017: member

    From a user perspective, if we don't support creating new non-HD wallets, then it makes no sense to provide a -usehd=0 option.

  12. MarcoFalke commented at 3:13 PM on October 31, 2017: member

    Agree with @achow101. There is really no need to set hd/nohd when key generation is turned off completely.

  13. MarcoFalke commented at 10:16 PM on November 9, 2017: member

    Closing for now.

  14. MarcoFalke closed this on Nov 9, 2017

  15. DrahtBot locked this on Sep 8, 2021

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-13 21:15 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me