From: "Martin Habovštiak" <martin.habovstiak@gmail.com>
To: Mike Hearn <mike@plan99.net>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] New BIP: protocol for multisignature payments
Date: Sat, 31 Jan 2015 19:47:07 +0200 [thread overview]
Message-ID: <CALkkCJav7gQuDuPvWc_SOgVJGyfAorSWGHMvUjUTGZBJcGnNYQ@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP2V0+M5B0P3T6cUqmSh-0FTP5_VgNcegwQTQQM7XMfMsA@mail.gmail.com>
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 <mike@plan99.net>:
> 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_mediation
>
> 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štiak
> <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
>>
>
next prev parent reply other threads:[~2015-01-31 17:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-31 1:30 [Bitcoin-development] New BIP: protocol for multisignature payments Martin Habovštiak
2015-01-31 17:19 ` Mike Hearn
2015-01-31 17:47 ` Martin Habovštiak [this message]
2015-01-31 18:07 ` Mike Hearn
2015-01-31 21:50 ` Gavin Andresen
2015-01-31 23:02 ` Martin Habovštiak
2015-02-01 13:43 ` Mike Hearn
2015-02-01 14:14 ` Martin Habovštiak
2015-01-31 2:10 Thomas Kerin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CALkkCJav7gQuDuPvWc_SOgVJGyfAorSWGHMvUjUTGZBJcGnNYQ@mail.gmail.com \
--to=martin.habovstiak@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=mike@plan99.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox