public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Erik Aronesty <erik@q32.com>
To: nakagat@gmail.com,
	 Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Multisignature for bip-schnorr
Date: Wed, 29 Aug 2018 07:28:56 -0400	[thread overview]
Message-ID: <CAJowKgLGA0tc_uYMhZhB157b2--wcLyPeNhoxxbSh2r+fS+bJg@mail.gmail.com> (raw)
In-Reply-To: <CAHk9a9ct_h485MY4gk7S++FAu5FEH3PL9pd9mrrh+wA8nWaVUA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 953 bytes --]

It's cool but

- there's a lot of online steps.
- it's not a threshold system

Using a shamir scheme solves this and isn't subject to birthday attacks:

https://medium.com/@simulx/an-m-of-n-bitcoin-multisig-scheme-e7860ab34e7f



On Mon, Aug 13, 2018 at 7:08 AM nakagat via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> Hi all,
>
> I wrote a multisignature procedure using bip-schnorr.
>
> If you have time to review and give feedback, I’d really appreciate it.
> Thanks in advance!
>
> Multisignature
> https://gist.github.com/tnakagawa/0c3bc74a9a44bd26af9b9248dfbe598b
>
> Original
>
> https://github.com/sipa/bips/blob/bip-schnorr/bip-schnorr.mediawiki#Multisignatures_and_Threshold_Signatures
>
> --
> nakagawa
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

[-- Attachment #2: Type: text/html, Size: 1919 bytes --]

  reply	other threads:[~2018-08-29 11:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-07  6:35 [bitcoin-dev] Multisignature for bip-schnorr nakagat
2018-08-29 11:28 ` Erik Aronesty [this message]
2018-08-31  5:22 ` nakagat
2018-09-07  8:11 ` Jonas Nick
2018-09-12  6:00   ` nakagat

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=CAJowKgLGA0tc_uYMhZhB157b2--wcLyPeNhoxxbSh2r+fS+bJg@mail.gmail.com \
    --to=erik@q32.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=nakagat@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