4035c796a40dc69a36883d4f4a9738e5df1230
1 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] 2 helo=mx.sourceforge.net) 3 by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) 4 (envelope-from <mh.in.england@gmail.com>) id 1YHbhv-0006Uj-6d 5 for bitcoin-development@lists.sourceforge.net; 6 Sat, 31 Jan 2015 17:19:43 +0000 7 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com 8 designates 74.125.82.172 as permitted sender) 9 client-ip=74.125.82.172; envelope-from=mh.in.england@gmail.com; 10 helo=mail-we0-f172.google.com; 11 Received: from mail-we0-f172.google.com ([74.125.82.172]) 12 by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) 13 (Exim 4.76) id 1YHbht-0005JJ-Uk 14 for bitcoin-development@lists.sourceforge.net; 15 Sat, 31 Jan 2015 17:19:43 +0000 16 Received: by mail-we0-f172.google.com with SMTP id q59so32143775wes.3 17 for <bitcoin-development@lists.sourceforge.net>; 18 Sat, 31 Jan 2015 09:19:36 -0800 (PST) 19 MIME-Version: 1.0 20 X-Received: by 10.180.107.164 with SMTP id hd4mr6660467wib.7.1422724775882; 21 Sat, 31 Jan 2015 09:19:35 -0800 (PST) 22 Sender: mh.in.england@gmail.com 23 Received: by 10.194.188.9 with HTTP; Sat, 31 Jan 2015 09:19:35 -0800 (PST) 24 In-Reply-To: <1422667849.25602.6.camel@TARDIS> 25 References: <1422667849.25602.6.camel@TARDIS> 26 Date: Sat, 31 Jan 2015 18:19:35 +0100 27 X-Google-Sender-Auth: 9WftNmSV69TWVVKlymNSLdeQAxU 28 Message-ID: <CANEZrP2V0+M5B0P3T6cUqmSh-0FTP5_VgNcegwQTQQM7XMfMsA@mail.gmail.com> 29 From: Mike Hearn <mike@plan99.net> 30 To: =?UTF-8?Q?Martin_Habov=C5=A1tiak?= <martin.habovstiak@gmail.com> 31 Content-Type: multipart/alternative; boundary=e89a8f3ba085e1396e050df5ec12 32 X-Spam-Score: -0.5 (/) 33 X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. 34 See http://spamassassin.org/tag/ for more details. 35 -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for 36 sender-domain 37 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider 38 (mh.in.england[at]gmail.com) 39 -0.0 SPF_PASS SPF: sender matches SPF record 40 1.0 HTML_MESSAGE BODY: HTML included in message 41 0.1 DKIM_SIGNED Message has a DKIM or DK signature, 42 not necessarily valid 43 -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 44 X-Headers-End: 1YHbht-0005JJ-Uk 45 Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net> 46 Subject: Re: [Bitcoin-development] New BIP: protocol for multisignature 47 payments 48 X-BeenThere: bitcoin-development@lists.sourceforge.net 49 X-Mailman-Version: 2.1.9 50 Precedence: list 51 List-Id: <bitcoin-development.lists.sourceforge.net> 52 List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, 53 <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> 54 List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> 55 List-Post: <mailto:bitcoin-development@lists.sourceforge.net> 56 List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> 57 List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, 58 <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> 59 X-List-Received-Date: Sat, 31 Jan 2015 17:19:43 -0000 60 61 --e89a8f3ba085e1396e050df5ec12 62 Content-Type: text/plain; charset=UTF-8 63 Content-Transfer-Encoding: quoted-printable 64 65 Hi Martin, 66 67 You're on the right lines. Your writeup is pretty similar to the high level 68 overview given here though: 69 70 https://en.bitcoin.it/wiki/Contracts#Example_2:_Escrow_and_dispute_mediatio= 71 n 72 73 To make 2-of-3 dispute mediation works requires implementing a wallet that 74 supports it, and the tools mediators need to manage incoming tickets, etc. 75 The BIP70 extension is probably the smallest part of the project. 76 77 78 On Sat, Jan 31, 2015 at 2:30 AM, Martin Habov=C5=A1tiak < 79 martin.habovstiak@gmail.com> wrote: 80 81 > Hello, 82 > 83 > I've been thinking about how to solve security problems of the servers 84 > holding huge amounts of bitcoins (exchanges, markets...) and came up 85 > with this idea: https://gist.github.com/Kixunil/2ec79cf40a53fb899ac5 86 > 87 > TL;DR: it's extension of BIP70 (but not fully compatible due to security 88 > reasons) which supports making of multisig transactions dynamically. 89 > (The most important thing is that the user provides his address.) 90 > 91 > What do you think? Is it a good way to solve the problem or do you know 92 > about something better? I would really like this or something similar 93 > implemented by wallets. 94 > 95 > Thank you for your feedback! 96 > 97 > Martin 98 > 99 > 100 > -------------------------------------------------------------------------= 101 ----- 102 > Dive into the World of Parallel Programming. The Go Parallel Website, 103 > sponsored by Intel and developed in partnership with Slashdot Media, is 104 > your 105 > hub for all things parallel software development, from weekly thought 106 > leadership blogs to news, videos, case studies, tutorials and more. Take = 107 a 108 > look and join the conversation now. http://goparallel.sourceforge.net/ 109 > _______________________________________________ 110 > Bitcoin-development mailing list 111 > Bitcoin-development@lists.sourceforge.net 112 > https://lists.sourceforge.net/lists/listinfo/bitcoin-development 113 > 114 > 115 116 --e89a8f3ba085e1396e050df5ec12 117 Content-Type: text/html; charset=UTF-8 118 Content-Transfer-Encoding: quoted-printable 119 120 <div dir=3D"ltr">Hi Martin,<div><br></div><div>You're on the right line= 121 s. Your writeup is pretty similar to the high level overview given here tho= 122 ugh:</div><div><br></div><div><a href=3D"https://en.bitcoin.it/wiki/Contrac= 123 ts#Example_2:_Escrow_and_dispute_mediation">https://en.bitcoin.it/wiki/Cont= 124 racts#Example_2:_Escrow_and_dispute_mediation</a><br></div><div><br></div><= 125 div>To make 2-of-3 dispute mediation works requires implementing a wallet t= 126 hat supports it, and the tools mediators need to manage incoming tickets, e= 127 tc. The BIP70 extension is probably the smallest part of the project.</div>= 128 <div><br></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quo= 129 te">On Sat, Jan 31, 2015 at 2:30 AM, Martin Habov=C5=A1tiak <span dir=3D"lt= 130 r"><<a href=3D"mailto:martin.habovstiak@gmail.com" target=3D"_blank">mar= 131 tin.habovstiak@gmail.com</a>></span> wrote:<br><blockquote class=3D"gmai= 132 l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left= 133 :1ex">Hello,<br> 134 <br> 135 I've been thinking about how to solve security problems of the servers<= 136 br> 137 holding huge amounts of bitcoins (exchanges, markets...) and came up<br> 138 with this idea: <a href=3D"https://gist.github.com/Kixunil/2ec79cf40a53fb89= 139 9ac5" target=3D"_blank">https://gist.github.com/Kixunil/2ec79cf40a53fb899ac= 140 5</a><br> 141 <br> 142 TL;DR: it's extension of BIP70 (but not fully compatible due to securit= 143 y<br> 144 reasons) which supports making of multisig transactions dynamically.<br> 145 (The most important thing is that the user provides his address.)<br> 146 <br> 147 What do you think? Is it a good way to solve the problem or do you know<br> 148 about something better? I would really like this or something similar<br> 149 implemented by wallets.<br> 150 <br> 151 Thank you for your feedback!<br> 152 <span class=3D"HOEnZb"><font color=3D"#888888"><br> 153 Martin<br> 154 </font></span><br>---------------------------------------------------------= 155 ---------------------<br> 156 Dive into the World of Parallel Programming. The Go Parallel Website,<br> 157 sponsored by Intel and developed in partnership with Slashdot Media, is you= 158 r<br> 159 hub for all things parallel software development, from weekly thought<br> 160 leadership blogs to news, videos, case studies, tutorials and more. Take a<= 161 br> 162 look and join the conversation now. <a href=3D"http://goparallel.sourceforg= 163 e.net/" target=3D"_blank">http://goparallel.sourceforge.net/</a><br>_______= 164 ________________________________________<br> 165 Bitcoin-development mailing list<br> 166 <a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo= 167 pment@lists.sourceforge.net</a><br> 168 <a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development= 169 " target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de= 170 velopment</a><br> 171 <br></blockquote></div><br></div> 172 173 --e89a8f3ba085e1396e050df5ec12-- 174 175