Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1R7F4X-0000g8-6c for bitcoin-development@lists.sourceforge.net; Fri, 23 Sep 2011 23:22:21 +0000 X-ACL-Warn: Received: from zinan.dashjr.org ([173.242.112.54]) by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1R7F4W-0003Yo-Dn for bitcoin-development@lists.sourceforge.net; Fri, 23 Sep 2011 23:22:21 +0000 Received: from ishibashi.localnet (fl-184-4-160-40.dhcp.embarqhsd.net [184.4.160.40]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id EC848204034; Fri, 23 Sep 2011 23:22:13 +0000 (UTC) From: "Luke-Jr" To: bitcoin-development@lists.sourceforge.net Date: Fri, 23 Sep 2011 19:21:58 -0400 User-Agent: KMail/1.13.7 (Linux/2.6.39-gentoo; KDE/4.6.5; x86_64; ; ) References: <20110923162102.GA13532@ulyssis.org> <4E7CC428.6020500@jerviss.org> <20110923231547.GA28700@ulyssis.org> In-Reply-To: <20110923231547.GA28700@ulyssis.org> X-PGP-Key-Fingerprint: CE5A D56A 36CC 69FA E7D2 3558 665F C11D D53E 9583 X-PGP-Key-ID: 665FC11DD53E9583 X-PGP-Keyserver: x-hkp://subkeys.pgp.net MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201109231922.01269.luke@dashjr.org> X-Spam-Score: -0.5 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.5 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1R7F4W-0003Yo-Dn Subject: Re: [Bitcoin-development] Beyond IP transactions: towards a bitcoin 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: Fri, 23 Sep 2011 23:22:21 -0000 On Friday, September 23, 2011 7:15:48 PM Pieter Wuille wrote: > What I want to do is to standardize part of that out-of-band communication > inside a protocol. Email and XMPP are suitable. Just sign the message with the "from" key. > The first observation is that if you want a freshly negotiated key each > time, some form of bidirectional communication is necessary anyway, and a > static txout template does not suffice anymore. False. Deterministic keypairs remove the necessity of bidirectional communication. A standard for a "public key root" "address" could be worthwhile. Both of these combined retain pseudonomity, while providing stateless transactions with out-of-band data.