public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Odinn Cyberguerrilla" <odinn.cyberguerrilla@riseup.net>
To: "Gavin Andresen" <gavinandresen@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
	kjj <bitcoin-devel@jerviss.org>
Subject: Re: [Bitcoin-development] Multisign payment protocol?
Date: Tue, 11 Mar 2014 10:41:44 -0700	[thread overview]
Message-ID: <4fca6b510dd57d2f92affeb988d2ee5d.squirrel@fulvetta.riseup.net> (raw)
In-Reply-To: <CABsx9T0Lvg84qFVRbc7Ef4vZEQj9eO7Jhup5PTRLLeuJFvXi-w@mail.gmail.com>

Hello,

I wanted to just add a very brief note to this discussion, that presently
for multisignature creation and management (new transaction etc) I've been
using this: https://coinb.in/multisig/

There were some initial bumps in the road but they were worked out,

see full thread more or less beginning from here:

https://bitcointalk.org/index.php?topic=390046.msg4687868#msg4687868

Curious as to what wallets actually support multisig / P2SH at this point?
Unsure.  Am assuming more than previously.



> On Tue, Mar 11, 2014 at 8:38 AM, Jeff Garzik <jgarzik@bitpay.com> wrote:
>
>> On Tue, Mar 11, 2014 at 7:43 AM, Drak <drak@zikula.org> wrote:
>> > I very much like the idea of assuming each party uses HD wallets, that
>> > certainly simplifies things greatly.
>>
>> It also assumes a reality different from our current one.
>>
>
> Multisig wallets are a different reality from our current one, so when we
> move to that new reality we should do it correctly from the beginning.
>
> --
> --
> Gavin Andrese
> ------------------------------------------------------------------------------
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and their
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> http://p.sf.net/sfu/13534_NeoTech_______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>





  parent reply	other threads:[~2014-03-11 17:41 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-10 17:39 [Bitcoin-development] Multisign payment protocol? Drak
2014-03-10 17:49 ` Gavin Andresen
2014-03-10 18:01   ` Alan Reiner
2014-03-11  0:04     ` kjj
2014-03-11  0:09       ` Alan Reiner
2014-03-11  0:14         ` Jeff Garzik
2014-03-11  1:15           ` Gavin Andresen
2014-03-11 11:43             ` Drak
2014-03-11 12:38               ` Jeff Garzik
2014-03-11 13:51                 ` Gavin Andresen
2014-03-11 14:13                   ` Jeff Garzik
2014-03-11 14:23                     ` Gavin Andresen
2014-03-11 14:34                       ` Jeff Garzik
2014-03-11 14:44                       ` Jeff Garzik
2014-03-11 14:53                         ` Gary Rowe
2014-03-11 15:18                           ` Mike Hearn
2014-03-11 17:11                             ` Miron
2014-03-11 15:37                           ` Thomas Voegtlin
2014-03-11 21:12                     ` Peter Todd
2014-03-11 17:41                   ` Odinn Cyberguerrilla [this message]
2014-03-12  0:29                     ` Jean-Pierre Rupp
2014-03-12  2:35                       ` Alan Reiner
2014-03-12  2:48                         ` Eric Lombrozo
2014-03-12  9:48                           ` Mike Hearn
2014-03-12 15:35                             ` Jeff Garzik
2014-03-12 16:02                               ` Mike Hearn
2014-03-12 16:09                                 ` Drak
2014-03-12 16:14                                   ` Mike Hearn
2014-03-12 16:24                                     ` Peter Todd
2014-03-12 16:33                                 ` Jeff Garzik
2014-03-12 16:41                                   ` Mike Hearn
2014-03-12 16:47                                     ` Peter Todd
2014-03-12 16:57                                     ` Jeff Garzik
2014-03-10 17:50 ` Mike Hearn
2014-03-10 18:12 ` Jeff Garzik

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=4fca6b510dd57d2f92affeb988d2ee5d.squirrel@fulvetta.riseup.net \
    --to=odinn.cyberguerrilla@riseup.net \
    --cc=bitcoin-devel@jerviss.org \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=gavinandresen@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