public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: devrandom <c1.sf-bitcoin@niftybox.net>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] BIP for standard multi-signature P2SH addresses
Date: Wed, 11 Mar 2015 16:11:27 -0700	[thread overview]
Message-ID: <5500CB9F.8040602@niftybox.net> (raw)
In-Reply-To: <55002AD9.2060006@thomaskerin.io>

ACK.  CryptoCorp uses this method for our external signer service.

On 2015-03-11 04:45 AM, Thomas Kerin wrote:
> 
> Hi all,
> 
> I just created a PR on bitcoin/bips for a proposed standard for creating
> standard multisignature P2SH addresses given m, and a set of public keys.
> 
> https://github.com/bitcoin/bips/pull/146
> 
> I used BIP0090 as a place-holder, but I would like to request a BIP
> number for this now.
> 
> All the best,
> 
> 
> 
> 
> ------------------------------------------------------------------------------
> 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
> 

-- 
devrandom / Miron

-- 
devrandom / Miron



      parent reply	other threads:[~2015-03-11 23:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-11 11:45 [Bitcoin-development] BIP for standard multi-signature P2SH addresses Thomas Kerin
2015-03-11 17:16 ` Mike Hearn
2015-03-11 20:16 ` Gregory Maxwell
2015-03-11 23:24   ` Pindar Wong
2015-03-11 23:34     ` Gregory Maxwell
2015-03-11 23:50       ` Pindar Wong
2015-03-11 23:11 ` devrandom [this message]

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=5500CB9F.8040602@niftybox.net \
    --to=c1.sf-bitcoin@niftybox.net \
    --cc=bitcoin-development@lists.sourceforge.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