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-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YHbhv-0006Uj-6d for bitcoin-development@lists.sourceforge.net; Sat, 31 Jan 2015 17:19:43 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.172 as permitted sender) client-ip=74.125.82.172; envelope-from=mh.in.england@gmail.com; helo=mail-we0-f172.google.com; Received: from mail-we0-f172.google.com ([74.125.82.172]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YHbht-0005JJ-Uk for bitcoin-development@lists.sourceforge.net; Sat, 31 Jan 2015 17:19:43 +0000 Received: by mail-we0-f172.google.com with SMTP id q59so32143775wes.3 for ; Sat, 31 Jan 2015 09:19:36 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.180.107.164 with SMTP id hd4mr6660467wib.7.1422724775882; Sat, 31 Jan 2015 09:19:35 -0800 (PST) Sender: mh.in.england@gmail.com Received: by 10.194.188.9 with HTTP; Sat, 31 Jan 2015 09:19:35 -0800 (PST) In-Reply-To: <1422667849.25602.6.camel@TARDIS> References: <1422667849.25602.6.camel@TARDIS> Date: Sat, 31 Jan 2015 18:19:35 +0100 X-Google-Sender-Auth: 9WftNmSV69TWVVKlymNSLdeQAxU Message-ID: From: Mike Hearn To: =?UTF-8?Q?Martin_Habov=C5=A1tiak?= Content-Type: multipart/alternative; boundary=e89a8f3ba085e1396e050df5ec12 X-Spam-Score: -0.5 (/) 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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 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: 1YHbht-0005JJ-Uk Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] New BIP: protocol for multisignature payments 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: Sat, 31 Jan 2015 17:19:43 -0000 --e89a8f3ba085e1396e050df5ec12 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Martin, You're on the right lines. Your writeup is pretty similar to the high level overview given here though: https://en.bitcoin.it/wiki/Contracts#Example_2:_Escrow_and_dispute_mediatio= n To make 2-of-3 dispute mediation works requires implementing a wallet that supports it, and the tools mediators need to manage incoming tickets, etc. The BIP70 extension is probably the smallest part of the project. On Sat, Jan 31, 2015 at 2:30 AM, Martin Habov=C5=A1tiak < martin.habovstiak@gmail.com> wrote: > Hello, > > I've been thinking about how to solve security problems of the servers > holding huge amounts of bitcoins (exchanges, markets...) and came up > with this idea: https://gist.github.com/Kixunil/2ec79cf40a53fb899ac5 > > TL;DR: it's extension of BIP70 (but not fully compatible due to security > reasons) which supports making of multisig transactions dynamically. > (The most important thing is that the user provides his address.) > > What do you think? Is it a good way to solve the problem or do you know > about something better? I would really like this or something similar > implemented by wallets. > > Thank you for your feedback! > > Martin > > > -------------------------------------------------------------------------= ----- > Dive into the World of Parallel Programming. The Go Parallel Website, > sponsored by Intel and developed in partnership with Slashdot Media, is > your > hub for all things parallel software development, from weekly thought > leadership blogs to news, videos, case studies, tutorials and more. Take = a > look and join the conversation now. http://goparallel.sourceforge.net/ > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > > --e89a8f3ba085e1396e050df5ec12 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Martin,

You're on the right line= s. Your writeup is pretty similar to the high level overview given here tho= ugh:


<= div>To make 2-of-3 dispute mediation works requires implementing a wallet t= hat supports it, and the tools mediators need to manage incoming tickets, e= tc. The BIP70 extension is probably the smallest part of the project.
=


On Sat, Jan 31, 2015 at 2:30 AM, Martin Habov=C5=A1tiak <mar= tin.habovstiak@gmail.com> wrote:
Hello,

I've been thinking about how to solve security problems of the servers<= br> holding huge amounts of bitcoins (exchanges, markets...) and came up
with this idea: https://gist.github.com/Kixunil/2ec79cf40a53fb899ac= 5

TL;DR: it's extension of BIP70 (but not fully compatible due to securit= y
reasons) which supports making of multisig transactions dynamically.
(The most important thing is that the user provides his address.)

What do you think? Is it a good way to solve the problem or do you know
about something better? I would really like this or something similar
implemented by wallets.

Thank you for your feedback!

Martin

---------------------------------------------------------= ---------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is you= r
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a<= br> look and join the conversation now. http://goparallel.sourceforge.net/
_______= ________________________________________
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment


--e89a8f3ba085e1396e050df5ec12--