public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Thomas Kerin <me@thomaskerin.io>
To: "Martin Habovštiak" <martin.habovstiak@gmail.com>
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] New BIP: protocol for multisignature payments
Date: Sat, 31 Jan 2015 02:10:45 +0000	[thread overview]
Message-ID: <20150131021045.h7SWfQRKytSYsa7dcAYymNizAUdkyAs1veGaRcVbiqA@z> (raw)

Ooh, I had a very similar proposal, except it involved sharing generic P2SH scripts. It also involved facilitating requesting of signatures.. We should talk.On 31 Jan 2015 01:30, 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 

             reply	other threads:[~2015-01-31  2:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-31  2:10 Thomas Kerin [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
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

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=20150131021045.h7SWfQRKytSYsa7dcAYymNizAUdkyAs1veGaRcVbiqA@z \
    --to=me@thomaskerin.io \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=martin.habovstiak@gmail.com \
    /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