< sipa>
cluelessperson: i don't think an address should be shown until you request one
< cluelessperson>
sipa: why?
< sipa>
it's very hard to prevent reuse otherwise
< cluelessperson>
sipa: Have core generate a new address when it detects a transaction come through
< sipa>
cluelessperson: that's what we used to do. it makes people freak out their address changed
< cluelessperson>
sipa: Or, just have it start out blank, and it won't show you one until you ask for it. :)
< sipa>
still shouldn't show it afterwards anymore
< sipa>
the whole "this is your address" causes more problems than understanding
< cluelessperson>
sipa: then I'll add the subtext, "old addresses are stored in history" and you make them show up in the transactions/history tab
< sipa>
an address is something that is per requested paymemt
< sipa>
not something "belonging" to you
< cluelessperson>
sipa: What?
< cluelessperson>
of course addresses belond to you
< sipa>
yes, of course they do
< sipa>
but i mean people shouldn't see them as such
< sipa>
they should see it as an invoice number
< sipa>
more than as an account number
< cluelessperson>
sipa: Sure, you definitely want to make it easy as hell to use, just toss out a QR code to scan, but you cannot hide it when people want it
< cluelessperson>
it's also currently a fundamental of how people understand bitcoin to work.
< sipa>
cluelessperson: i don't care about easy as hell
< cluelessperson>
sipa: That's a good resolve to have, you're right, so let's do both. :)
< cluelessperson>
Easy as hell AND No losing of funds.
< sipa>
i dislike "your current receiving address" :)
< sipa>
that sounds like ot's still sometging designed to last for a period of timr
< cluelessperson>
sipa: That's just verbiage, I'm absolutely open to changing that and the layout. My mock up is to demonstrate the fundamental requirements that should be on the receiving tab, and the organization that would make sense "no questions asked" to all users.
< sipa>
ok
< sipa>
sure
< cluelessperson>
sipa: I agree with you, what would you like to rename the "current receiving addrss" assuming I myself try to patch together a ... pull request
< cluelessperson>
sipa: Thanks for your input, you are absolutely right
< cluelessperson>
I'll put more thought into how to handle it as well
< bitcoin-git>
[bitcoin] PierreRochard opened pull request #11923: Wallet : remove unused fNoncriticalErrors variable from CWalletDB::FindWalletTx (master...2017-12-17-FindWalletTx) https://github.com/bitcoin/bitcoin/pull/11923
< adminj>
cluelessperson it can be helpful to draw proposed design changes on top of an existing screenshot, as it makes it easier to understand the relative change. Your last sketch looks completely different from the current look and feel. As much as I'd love a complete revamp, smaller incremental improvements are more likely to actually happen.
< cluelessperson>
adminj: that's a good suggestion
< sturles>
I have been education my users for a while to use segwit compatible wallets. The result is that now most of my outgoing transactions are to bc1.. and 3.. type addresses, with the change output being the only one to and1...