Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1SErrc-000611-Qj for bitcoin-development@lists.sourceforge.net; Tue, 03 Apr 2012 00:44:48 +0000 X-ACL-Warn: Received: from zinan.dashjr.org ([173.242.112.54]) by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1SErrb-0002y0-QV for bitcoin-development@lists.sourceforge.net; Tue, 03 Apr 2012 00:44:48 +0000 Received: from ishibashi.localnet (unknown [97.96.85.141]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id 5C9BC5606E2; Tue, 3 Apr 2012 00:44:42 +0000 (UTC) From: "Luke-Jr" To: bitcoin-development@lists.sourceforge.net Date: Mon, 2 Apr 2012 20:44:37 -0400 User-Agent: KMail/1.13.7 (Linux/3.2.2-gentoo; KDE/4.7.4; x86_64; ; ) References: <4F7A1227.7070306@gmail.com> In-Reply-To: <4F7A1227.7070306@gmail.com> X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F X-PGP-Key-ID: BD02942421F4889F X-PGP-Keyserver: hkp://pgp.mit.edu MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201204022044.38861.luke@dashjr.org> X-Spam-Score: -0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1SErrb-0002y0-QV Subject: Re: [Bitcoin-development] Signature Blocks and URI Sign Requests 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: Tue, 03 Apr 2012 00:44:48 -0000 On Monday, April 02, 2012 4:55:03 PM Alan Reiner wrote: > Any thoughts? (I have no doubts that there are :) ) IMO, the sign-request URI should be an extension on the existing bitcoin: URI scheme; this way, sigNeeded can be omitted to imply "sign with a sending address".