< gmaxwell> luke-jr: in the meantime, if reuse is really a concern for you lets work on improving the UI flow to politely discourage it.
< gmaxwell> I think there is a lot we can do to shift the norms.
< gmaxwell> and also make things safer even from the perspective of someone that thinks reuse is totally fine.
< gmaxwell> (in particular, I've seen quite a few users accidentally pay someone twice... e.g. going down a spreadsheet to make payments and just processing the same line twice)
< luke-jr> gmaxwell: is there? I would like to hope so, but it really does seem like most people use other wallets now. :/
< luke-jr> I mean, we can certainly improve it anyway, but I'm not sure how effective it would be in shifting norms
< gmaxwell> luke-jr: at least by transaction count bitcoin core usage appears to outpace electrum something like 5:1
< luke-jr> :o
< luke-jr> that's surprisingly positive
< gmaxwell> you get a distorted perspective from seeing what people post about.
< gmaxwell> It's probably the case that more _people_ use electrum, but they're transacting infrequently.
< gmaxwell> plus half those people just lost all their bitcoins anyways. :-/
< luke-jr> are you sure you're not mixing up other light wallets for Core?
< echeveria> electrum has some interesting usage stats that came out of the malware attack (trying to see a silver lining). information about the number of users and what sort of money they store there.
< echeveria> gmaxwell: one mistake in MultiBit that caused duplicate payments was that it saved the previous address you paid, for some reason. so people would see the form partly filled out and assume that was the address they intended to pay, and then sent money there.
< * luke-jr> wonders if running an Electrum server would enable him to get reasonable estimates of total Electrum wallets and their economic influence
< echeveria> it would, roughly speaking. the RPC interface just has a literal list of addresses pushed to the server. there's a number of these which appear to be set up expressly for the task.
< luke-jr> echeveria: a few years ago, someone decided to tip me unknownst to me, and googled "luke-jr bitcoin address", then paid a random address on the bc.i page (which luckily happened to be my *change* address in the transaction that came up)
< luke-jr> echeveria: but do Electrum clients often pick a random server to use? or typically peg to the same one(s)?
< echeveria> I sort of caution about making assumptions based on this sort of data. Bread Wallet used a privacy leak in their "sell BCH" function to determine that the average user who used the feature had X BTC in their wallet, and then multiplied by the number of installs to come to the conclusion that their users were storing billions of dollars. this is obviously not correct.
< luke-jr> heh
< luke-jr> I wish mobile wallets published their "number of current installs" numbers
< echeveria> luke-jr: there's logic for pinning servers you've seen, but generally speaking it's random based on a returned list (which currently contains about 800 sybil servers and 150 or so real ones).
< luke-jr> O.o
< gmaxwell> luke-jr: in the last several releases core has made varrious changes that make its transactions readily identifyable.
< jarthur> Re Electrum server selection, the server pool collection code: https://github.com/spesmilo/electrum/blob/master/electrum/network.py#L460 <- basically hardcoded servers, recently connected, and learned peers from servers we've connected to are aggregated prior to random selection.
< jarthur> Good servers are blacklisting known evil peers.
< provoostenator> Speaking of discouring address reuse, too late for v0.18 but otherwise pretty close to finish line: #13756
< gribble> https://github.com/bitcoin/bitcoin/issues/13756 | wallet: "avoid_reuse" wallet flag for improved privacy by kallewoof · Pull Request #13756 · bitcoin/bitcoin · GitHub
< provoostenator> *discouraging
< provoostenator> It would help if more people, who work on functional tests, installed PyEnv. #14884 is only a partial solution to preventing too modern Python syntax from entering the codebase.
< gribble> https://github.com/bitcoin/bitcoin/issues/14884 | Travis: enforce Python 3.4 support through linter by Sjors · Pull Request #14884 · bitcoin/bitcoin · GitHub
< provoostenator> Otherwise we should probably install PyEnv on one of the Travis machines which run the test suite.
< provoostenator> #15439 fixes the exsting issues
< gribble> https://github.com/bitcoin/bitcoin/issues/15439 | tests: remove byte.hex() to keep compatibility by AkioNak · Pull Request #15439 · bitcoin/bitcoin · GitHub
< jl2012> luke-jr: which part do you not understand?
< jl2012> I think what you want is the ability to tell the payer not to reuse a specific address?
< luke-jr> jl2012: no addresses should ever be reused
< luke-jr> jl2012: but there was a rather long convo here yesterday, not sure it's productive to go over again unless there's something new to add
< jl2012> alright, I'll read it first
< bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/38429c4b6228...f9775a865597
< bitcoin-git> bitcoin/master 1a062b8 Akio Nakamura: tests: remove byte.hex() to keep compatibility
< bitcoin-git> bitcoin/master f9775a8 MarcoFalke: Merge #15439: tests: remove byte.hex() to keep compatibility
< bitcoin-git> [bitcoin] MarcoFalke merged pull request #15439: tests: remove byte.hex() to keep compatibility (master...keep_compatiblity) https://github.com/bitcoin/bitcoin/pull/15439
< bitcoin-git> [bitcoin] ryanofsky opened pull request #15448: bitcoin-cli: Eliminate "Error parsing JSON" errors (master...pr/unistr) https://github.com/bitcoin/bitcoin/pull/15448
< promag_> sipa: could you see #15443?
< gribble> https://github.com/bitcoin/bitcoin/issues/15443 | qa: Add getdescriptorinfo functional test by promag · Pull Request #15443 · bitcoin/bitcoin · GitHub
< bitcoin-git> [bitcoin] achow101 opened pull request #15450: [GUI] Create wallet menu option (master...gui-create-wallet) https://github.com/bitcoin/bitcoin/pull/15450
< bitcoin-git> [bitcoin] HashUnlimited opened pull request #15451: [doc] clarify getdata limit after #14897 (master...patch-2) https://github.com/bitcoin/bitcoin/pull/15451
< bitcoin-git> [bitcoin] instagibbs opened pull request #15452: Replace CScriptID and CKeyID in CTxDestination with dedicated types (master...key_script_dest) https://github.com/bitcoin/bitcoin/pull/15452
< bitcoin-git> [bitcoin] achow101 opened pull request #15454: Remove the automatic creation and loading of the default wallet (master...no-default-wallet) https://github.com/bitcoin/bitcoin/pull/15454