From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Vasd9-0005yu-CC for bitcoin-development@lists.sourceforge.net; Mon, 28 Oct 2013 19:37:39 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of taplink.co designates 50.117.27.232 as permitted sender) client-ip=50.117.27.232; envelope-from=jeremy@taplink.co; helo=mail.taplink.co; Received: from mail.taplink.co ([50.117.27.232]) by sog-mx-3.v43.ch3.sourceforge.com with smtp (Exim 4.76) id 1Vasd8-0006mX-Aa for bitcoin-development@lists.sourceforge.net; Mon, 28 Oct 2013 19:37:39 +0000 Received: from laptop-air ([192.168.168.135]) by mail.taplink.co ; Mon, 28 Oct 2013 12:47:14 -0700 Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes To: "Gregory Maxwell" , "John Dillon" References: Date: Mon, 28 Oct 2013 12:37:30 -0700 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Jeremy Spilman" Organization: TapLink Message-ID: In-Reply-To: User-Agent: Opera Mail/1.0 (Win32) oclient: 192.168.168.135#jeremy@taplink.co#465 X-Spam-Score: -2.1 (--) 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 SPF_PASS SPF: sender matches SPF record -0.5 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: taplink.co] -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: 1Vasd8-0006mX-Aa Cc: Bitcoin Development Subject: Re: [Bitcoin-development] Payment protocol for onion URLs. 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: Mon, 28 Oct 2013 19:37:39 -0000 Just an aside... The 1BTC bountry John references below is a 1BTC P2SH output, where the redeemScript he provided does hash to the expected value, and is itself a 2-of-3 multisig, with the following pubkeys, expressed as addresses: 1BrufViLKnSWtuWGkryPsKsxonV2NQ7Tcj 1FCYd7j4CThTMzts78rh6iQJLBRGPW9fWv 1GMaxweLLbo8mdXvnnC19Wt2wigiYUKgEB By comparison, the signatories for the 4BTC bountry are: 1L9p6QiWs2nfinyF4CnbqysWijMvvcsnxe 1FCYd7j4CThTMzts78rh6iQJLBRGPW9fWv 1GMaxweLLbo8mdXvnnC19Wt2wigiYUKgEB On the one hand, the vanity address makes it easy to guess who one of the signatories is, on the other hand, is it bad form to reuse keys for signing? John, you mentioned wanting to disambiguate bounties, perhaps through a bounty-specific pubkey. I'm not sure I follow, how is that better than just referencing the address of the output, or the TxID, in a 'Table of Bounties'? Or you want to embed a hash of your signed message announcing the bounty? Out of curiosity, I suppose right now you just keep pubkeys for the signatories you want to appoint and reuse the same pubkey to create these multi-sigs, or you have to ask for a new one each time? From the signatories perspective, I imagine we're a long way off from a wallet receiving or importing the p2sh, tracking that these outputs as "yours", and even more, which contract/bounty they correspond to, and finally a usable way to accumulate signatures and ultimately spend the output to the bounty winner. And of course, thanks for posting the bounties! On Sun, 27 Oct 2013 22:58:13 -0700, John Dillon wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > On Sat, Oct 26, 2013 at 3:31 AM, Gregory Maxwell > wrote: >> One limitation of the payment protocol as speced is that there is no >> way for a hidden service site to make use of its full authentication >> capability because they are unable to get SSL certificates issued to >> them. >> >> Thoughts? > > I think this is a great idea and wish to see it done. Here is 1BTC for > you, > redeemable when you finish this task. I trust either Jeff Garzik or > Peter Todd > to evaluate your finished product, or possibly someone elses: > > 37NDa6iFLEozbvw8vj38ri5D6SLw5xQujS > > 22e067d3317e6300a9edda84fd0e24d8bfb86cf91540c3fe7acff45e4dc64dd3:0 > > redeemScript : > "5241045f4bba15dbfe94a45f362aa13bbaef8bbf21ff84fec1be5b27fa628f4b3acca1a2e5711503c8b8fe2e228229b8b8814f9e33e0f7a314a089d7140269ffd51fe44104d34775baab521d7ba2bd43997312d5f663633484ae1a4d84246866b7088297715a049e2288ae16f168809d36e2da1162f03412bf23aa5f949f235eb2e71417834104f005d39733ec09a1efa0cf8dcf3df50691e22c2374ff9a96d1d9ecb98a1e866c9f558a9fa1ba8ef0bbbad01f396768c0cb2dda9924dc0aaee1481604a8bd9ce453ae" > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > > iQEcBAEBCAAGBQJSbfy2AAoJEEWCsU4mNhiPrMMH/jd+AgVYUKd1vmP1BfaZum1s > X186JulwF659YHOx94dLs+NOjvjMfY6cPbHm+B0j20CnhWrZrXzcXvwTHnzOSuoc > 1AAXg0KDbvyo+7PvTrsGQfHhT1FZSRzIUToofVmFlvEIO6/LiYMAYWCgIiX9nPvv > RlvdtavTST+cY19yZamo5X0XU5cgI2tbtVWKEHJQ2VcglCgwFg5K0kZ0O1NMKbcZ > KBagY3PVTiHnYP+LwSTW6EU9DNq0eLYG39mz4N6CqGkXZjGgh2YXZ6Sl2qRuO/5e > Rd9HcJXKqPKqMuRpQ2PA5U3U6QSyrUz7/fmi5dsOxnR6pdR53kjUVSvbOqBFHXw= > =I1/R > -----END PGP SIGNATURE----- > > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most > from > the latest Intel processors and coprocessors. See abstracts and register > > > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development