From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1UpIpw-0001vx-14 for bitcoin-development@lists.sourceforge.net; Wed, 19 Jun 2013 13:54:12 +0000 X-ACL-Warn: Received: from vps7135.xlshosting.net ([178.18.90.41]) by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1UpIpu-0007bU-Q2 for bitcoin-development@lists.sourceforge.net; Wed, 19 Jun 2013 13:54:11 +0000 Received: by vps7135.xlshosting.net (Postfix, from userid 1000) id CE1F833C82D; Wed, 19 Jun 2013 15:54:04 +0200 (CEST) Date: Wed, 19 Jun 2013 15:54:04 +0200 From: Pieter Wuille To: Alan Reiner Message-ID: <20130619135403.GA1783@vps7135.xlshosting.net> References: <51BFD886.8000701@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <51BFD886.8000701@gmail.com> X-PGP-Key: http://sipa.ulyssis.org/pubkey.asc User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Score: -0.1 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (pieter.wuille[at]gmail.com) 0.0 DKIM_ADSP_CUSTOM_MED No valid author signature, adsp_override is CUSTOM_MED -1.3 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 1.2 NML_ADSP_CUSTOM_MED ADSP custom_med hit, and not from a mailing list X-Headers-End: 1UpIpu-0007bU-Q2 Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Optional "wallet-linkable" address format - Payment Protocol X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jun 2013 13:54:12 -0000 On Mon, Jun 17, 2013 at 11:48:22PM -0400, Alan Reiner wrote: > _*Goal*_: An alternative address format made possible by BIP 32, which > allows one to specify a "Wallet ID" and "One-time payment" code, instead > of the standard one-use Base58-Hash160 addresses. This allows parties > with a persistent relationship to be able to prove that payment > addresses they provide each other are linked to a particular wallet, > reducing exposure to MitM attacks without the need for SSL or a web of > trust, and without compromising the privacy of either party. For > instance, this could be used between businesses that frequently do > business, by exchanging and verifying public keys beforehand, or could > be used by an exchange to identify if a customer withdrawal address is > related to their last deposit address, and if not enforce extra > authentication measures. Have you seen Timo Hanke's pay-to-contract presentation at the San Jose conference? It seems very related: http://www.youtube.com/watch?v=qwyALGlG33Q -- Pieter