-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 04/16/2014 11:06 AM, Adam Back wrote:
> Btw not to reignite the stealth vs reusable address bike shedding,
> but contrarily I was thinking it maybe actually better to try to
> rebrand address as "invoice number".  People understand double
> paying an invoice is not a good idea.  And if they receive the same
> invoice twice they'll query it.

"Invoice number" is still too coarse-grained.

If anyone cared about user privacy, then whatever was supplied to
users as an "invoice number" would be a BIP32 extended public key, or
something equivalent to that, which would allow the payer to create as
many unique addresses as they needed to avoid merging inputs.

Also, from a business accounting perspective it's broken and wrong to
assume a 1:1 relationship between payment transactions and invoices
anyway:

http://bitcoinism.blogspot.com/2014/01/business-accounting-and-bitcoin-privacy.html

- -- 
Support online privacy by using email encryption whenever possible.
Learn how here: http://www.youtube.com/watch?v=bakOKJFtB-k
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTUTkSAAoJECoisBQbQ4v0t44H/1dl/QFBbJKNatghyaCnrcYE
eQlq6RtUo9ZCGTehg4K8Q3wlHcNxTi5ojkZ0ccf9O6lWFAO3Dij9jeiUB0irX1SP
leGVV6I3CU6DYMLN+1AHqeHfGQ6T367zdlc69TO5E3Z3nEfStWVAnp6BwraDpgLs
OslTSlWiqAFZRrP9G18E7OF/jZcjxdW5QUuQk1ktW0yyZpL6LuwWHqRwoJ0LuR/V
nL/OeUUHD3k563c4et5uejVkoGRkLOnk9rLiAQNeX6FfL5T4t2Ae/45PywiLmXoN
7Egd9g7pDU0qZMnXTd9/JLMi1Vlx61pKogg3xSj/NLQuUwJJDTbua7dxjXOtC8I=
=9KG3
-----END PGP SIGNATURE-----