From: Justus Ranvier <justusranvier@gmail•com>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] mid-term bitcoin security (Re: Warning message when running wallet in Windows XP (or drop support?))
Date: Fri, 18 Apr 2014 14:39:14 +0000 [thread overview]
Message-ID: <53513912.6050302@gmail.com> (raw)
In-Reply-To: <20140416110627.GA8131@netbook.cypherspace.org>
[-- Attachment #1: Type: text/plain, Size: 1631 bytes --]
-----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-----
[-- Attachment #2: 0x1B438BF4.asc --]
[-- Type: application/pgp-keys, Size: 21191 bytes --]
next prev parent reply other threads:[~2014-04-18 14:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 8:14 [Bitcoin-development] Warning message when running wallet in Windows XP (or drop support?) Wladimir
2014-04-16 8:45 ` Melvin Carvalho
2014-04-16 9:41 ` Wladimir
2014-04-16 11:06 ` [Bitcoin-development] mid-term bitcoin security (Re: Warning message when running wallet in Windows XP (or drop support?)) Adam Back
2014-04-18 14:26 ` Jeff Garzik
2014-04-18 14:39 ` Justus Ranvier [this message]
2014-04-16 15:12 ` [Bitcoin-development] Warning message when running wallet in Windows XP (or drop support?) Kevin
2014-04-16 15:20 ` Pieter Wuille
2014-04-16 15:28 ` Wladimir
2014-04-16 16:27 ` Kevin
2014-04-16 16:35 ` Mark Friedenbach
2014-04-16 16:41 ` Chris Williams
2014-04-16 16:44 ` Mark Friedenbach
2014-04-16 16:50 ` Chris Williams
2014-04-16 18:59 ` Kevin
2014-04-16 19:43 ` Adam Back
2014-04-16 20:42 ` Roy Badami
2014-04-16 21:10 ` Laszlo Hanyecz
2014-04-16 21:29 ` Kevin
2014-04-16 21:39 ` Mark Friedenbach
2014-04-16 22:00 ` Pieter Wuille
2014-04-16 15:23 ` Mark Friedenbach
2014-04-16 22:06 ` Gregory Maxwell
2014-04-17 7:39 ` Wladimir
[not found] ` <CACKnu1prEkZb5L4bGeKfjHtW+1CLmAuYr2-OWq0z5z+SvxhLTg@mail.gmail.com>
2014-04-17 7:27 ` Wladimir
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53513912.6050302@gmail.com \
--to=justusranvier@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox