Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YHc8Y-0005om-KZ for bitcoin-development@lists.sourceforge.net; Sat, 31 Jan 2015 17:47:14 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.192.52 as permitted sender) client-ip=209.85.192.52; envelope-from=martin.habovstiak@gmail.com; helo=mail-qg0-f52.google.com; Received: from mail-qg0-f52.google.com ([209.85.192.52]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YHc8X-0006KL-Ai for bitcoin-development@lists.sourceforge.net; Sat, 31 Jan 2015 17:47:14 +0000 Received: by mail-qg0-f52.google.com with SMTP id z107so42499204qgd.11 for ; Sat, 31 Jan 2015 09:47:07 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.140.34.67 with SMTP id k61mr23326977qgk.95.1422726427860; Sat, 31 Jan 2015 09:47:07 -0800 (PST) Received: by 10.140.19.18 with HTTP; Sat, 31 Jan 2015 09:47:07 -0800 (PST) In-Reply-To: References: <1422667849.25602.6.camel@TARDIS> Date: Sat, 31 Jan 2015 19:47:07 +0200 Message-ID: From: =?UTF-8?Q?Martin_Habov=C5=A1tiak?= To: Mike Hearn Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -1.6 (-) 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 (martin.habovstiak[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -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: 1YHc8X-0006KL-Ai 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:47:14 -0000 I know about that wiki page. I just wanted to design protocol which would make it easier in practice. (now it would be done manually) I could look at implementing it someday, but now I'd like to receive feedback from community. 2015-01-31 19:19 GMT+02:00 Mike Hearn : > Hi Martin, > > You're on the right lines. Your writeup is pretty similar to the high lev= el > overview given here though: > > https://en.bitcoin.it/wiki/Contracts#Example_2:_Escrow_and_dispute_mediat= ion > > To make 2-of-3 dispute mediation works requires implementing a wallet tha= t > 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 > 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 >> >