Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <gmaxwell@gmail.com>) id 1W2eCB-0001SZ-TL for bitcoin-development@lists.sourceforge.net; Mon, 13 Jan 2014 09:52:35 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.215.41 as permitted sender) client-ip=209.85.215.41; envelope-from=gmaxwell@gmail.com; helo=mail-la0-f41.google.com; Received: from mail-la0-f41.google.com ([209.85.215.41]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1W2eC8-0007dk-IG for bitcoin-development@lists.sourceforge.net; Mon, 13 Jan 2014 09:52:35 +0000 Received: by mail-la0-f41.google.com with SMTP id mc6so1196706lab.28 for <bitcoin-development@lists.sourceforge.net>; Mon, 13 Jan 2014 01:52:25 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.152.4.99 with SMTP id j3mr6790971laj.31.1389606745181; Mon, 13 Jan 2014 01:52:25 -0800 (PST) Received: by 10.112.198.65 with HTTP; Mon, 13 Jan 2014 01:52:25 -0800 (PST) In-Reply-To: <CABsx9T2G=yqSUGr0+Ju5-z9P++uS20AwLC+c3DnFMHtcQjQK6w@mail.gmail.com> References: <20140106120338.GA14918@savin> <op.w9c5o7vgyldrnw@laptop-air.hsd1.ca.comcast.net> <20140110102037.GB25749@savin> <op.w9kkxcityldrnw@laptop-air.hsd1.ca.comcast.net> <CABsx9T2G=yqSUGr0+Ju5-z9P++uS20AwLC+c3DnFMHtcQjQK6w@mail.gmail.com> Date: Mon, 13 Jan 2014 01:52:25 -0800 Message-ID: <CAAS2fgTz0TaGhym_35V3N2-vHVzU9BeuV8q+QJjwh5bg77FEZg@mail.gmail.com> From: Gregory Maxwell <gmaxwell@gmail.com> To: Gavin Andresen <gavinandresen@gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (gmaxwell[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1W2eC8-0007dk-IG Cc: "bitcoin-development@lists.sourceforge.net" <bitcoin-development@lists.sourceforge.net> Subject: Re: [Bitcoin-development] Stealth Addresses X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: <bitcoin-development.lists.sourceforge.net> List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> List-Post: <mailto:bitcoin-development@lists.sourceforge.net> List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> X-List-Received-Date: Mon, 13 Jan 2014 09:52:36 -0000 On Sun, Jan 12, 2014 at 1:18 PM, Gavin Andresen <gavinandresen@gmail.com> w= rote: > No, please. Make it easy for non-geeks, extend the payment protocol, or > we'll spend the next two years writing code that tries to ignore linebrea= ks > and spaces and changing <input> elements in HTML forms to <textarea> .... However, if you're able to use the payment protocol then you probably don't need stealth addresses to prevent reuse. E.g. What can I put for a donation address on a totally static webpage? or on a billboard? At least thats what I understood these things were trying to solve=E2=80=94 fix privacy where realtime two way communication just isn't available.