From: Drak <drak@zikula.org>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] Multisign payment protocol?
Date: Mon, 10 Mar 2014 17:39:03 +0000 [thread overview]
Message-ID: <CANAnSg3Bt0e7CfUcJXe96xhU6nqif9ey_vurZMZkSa9OHjHStw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 827 bytes --]
I was wondering if there would be merit in a kind of BIP for a payment
protocol using multisig?
Currently, setting up a multisig is quite a feat. Users have to exchange
public keys, work out how to get the public keys from their addresses. If
one of the parties are not savvy enough, an malicious party could easily be
setup that was 2 of 3 instead of 2 of 2 where the malicious party generates
the multisig address+script and thus be able to run off with funds anyway.
It's also terribly complex to generate and keep track of. There's been a
nice attempt at creating an browser interface at coinb.in/multisig but it
still lacks the kind of ease with created by the payment protocol. If there
was a BIP then it would go a long way to aiding future usability of
multisig wallet implementations.
What are your thoughts?
Drak
[-- Attachment #2: Type: text/html, Size: 1000 bytes --]
next reply other threads:[~2014-03-10 17:39 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 17:39 Drak [this message]
2014-03-10 17:49 ` [Bitcoin-development] Multisign payment protocol? 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
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=CANAnSg3Bt0e7CfUcJXe96xhU6nqif9ey_vurZMZkSa9OHjHStw@mail.gmail.com \
--to=drak@zikula.org \
--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