Confusing description of sending/receiving address #15230

issue andronoob opened this issue on January 22, 2019
  1. andronoob commented at 10:33 PM on January 22, 2019: none

    I think the current descriptions of sending/receiving address list is somewhat confusing to the user:

    These are your Bitcoin addresses for sending payments. Always check the amount and the receiving address before sending coins.

    These are your Bitcoin addresses for receiving payments. It is recommended to use a new receiving address for each transaction.

    So what is exactly "your" Bitcoin addresses? For example, a confused user might think that he could "fake" the sending address when he is trying to pay another people.

    I think this might be improved, for example:

    You may send payments to these known Bitcoin addresses. Always check the amount and the receiving address before sending coins.

    These Bitcoin addresses are yours, you may use them to receive payments. It is recommended to use a new receiving address for each transaction.

  2. fanquake added the label GUI on Jan 22, 2019
  3. andronoob commented at 10:37 PM on January 22, 2019: none

    There is another problem: Bitcoin Core currently allows the user to import watch-only addresses - these addresses might not belong to the user.

  4. promag commented at 7:05 PM on January 28, 2019: member

    Agree, it's confusing. I'd remove those messages though — currently it promotes reusing addresses.

  5. andronoob commented at 12:53 AM on January 29, 2019: none

    @promag I think what Electrum did is pretty good. Electrum doesn't support importing keys/addrs into existing wallet, so there are less confusions around backuping. Screwups caused by change address like #11827 are also avoided. Watch-only wallets and spendable wallets have clear distinction. The address panel of Electrum clearly showed how many times an address has been used.

  6. andronoob commented at 1:10 AM on January 29, 2019: none

    Edited. I've submitted a new issue: #15281

  7. MarcoFalke commented at 3:24 PM on April 26, 2020: member

    The feature request didn't seem to attract much attention in the past. Also, the issue seems not important enough right now to keep it sitting around idle in the list of open issues.

    Closing due to lack of interest. Pull requests with improvements are always welcome.

  8. MarcoFalke closed this on Apr 26, 2020

  9. MarcoFalke locked this on Feb 15, 2022

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-21 18:15 UTC

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