📅 Original date posted:2014-03-10
📝 Original message:Payment protocol currently supports payments to multi-sig addresses.
In general, almost all wallet software sucks RE multisig. Just try
any of these actions in Bitcoin-Qt or another wallet:
* obtain a public key you control, given a bitcoin address
* easily share public keys
* easily share partially signed transactions
* build a P2SH multisig address from public keys, reliably. Right
now, participants have no idea about pubkey order, leading various N
possible P2SH addresses, given a list of public keys. Reproducing the
P2SH address is harder than it should be.
* track "partially controlled" balance (balance of coins of which you
may sign at least 1 of N)
* support for remote oracles and services that provide 1-of-N signatures
etc.
On Mon, Mar 10, 2014 at 1:39 PM, Drak <drak at zikula.org> wrote:
> 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
>
> ------------------------------------------------------------------------------
> 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 at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
Jeff Garzik [ARCHIVE] /
npub1kf…f3f58
2023-06-07 15:15:03
in reply to nevent1q…qs3c
Author Public Key
npub1kf0ppcjaguxekg24yx6smgxlu73qn0k8lm0t2wrqc0scpl7u3sgsmf3f58Seen on
wss://relay.noswhere.comPublished at
2023-06-07 15:15:03Event JSON
{
"id": "5fa70ed38fc46fee1f8f5c6b3ea8fddcda1070563619294740168a1647054d5e",
"pubkey": "b25e10e25d470d9b215521b50da0dfe7a209bec7fedeb53860c3e180ffdc8c11",
"created_at": 1686150903,
"kind": 1,
"tags": [
[
"e",
"07851d213f227977a351770e7dfc2e7354779fae77670cd215beec4023ffb144",
"",
"root"
],
[
"e",
"4b489cf88f3d909baee5df7e73391e06562f8039e1ceb8115df0ab8b784a7a1a",
"",
"reply"
],
[
"p",
"f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2"
]
],
"content": "📅 Original date posted:2014-03-10\n📝 Original message:Payment protocol currently supports payments to multi-sig addresses.\n\nIn general, almost all wallet software sucks RE multisig. Just try\nany of these actions in Bitcoin-Qt or another wallet:\n* obtain a public key you control, given a bitcoin address\n* easily share public keys\n* easily share partially signed transactions\n* build a P2SH multisig address from public keys, reliably. Right\nnow, participants have no idea about pubkey order, leading various N\npossible P2SH addresses, given a list of public keys. Reproducing the\nP2SH address is harder than it should be.\n* track \"partially controlled\" balance (balance of coins of which you\nmay sign at least 1 of N)\n* support for remote oracles and services that provide 1-of-N signatures\netc.\n\n\n\n\nOn Mon, Mar 10, 2014 at 1:39 PM, Drak \u003cdrak at zikula.org\u003e wrote:\n\u003e I was wondering if there would be merit in a kind of BIP for a payment\n\u003e protocol using multisig?\n\u003e\n\u003e Currently, setting up a multisig is quite a feat. Users have to exchange\n\u003e public keys, work out how to get the public keys from their addresses. If\n\u003e one of the parties are not savvy enough, an malicious party could easily be\n\u003e setup that was 2 of 3 instead of 2 of 2 where the malicious party generates\n\u003e the multisig address+script and thus be able to run off with funds anyway.\n\u003e\n\u003e It's also terribly complex to generate and keep track of. There's been a\n\u003e nice attempt at creating an browser interface at coinb.in/multisig but it\n\u003e still lacks the kind of ease with created by the payment protocol. If there\n\u003e was a BIP then it would go a long way to aiding future usability of multisig\n\u003e wallet implementations.\n\u003e\n\u003e What are your thoughts?\n\u003e\n\u003e Drak\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e Learn Graph Databases - Download FREE O'Reilly Book\n\u003e \"Graph Databases\" is the definitive new guide to graph databases and their\n\u003e applications. Written by three acclaimed leaders in the field,\n\u003e this first edition is now available. Download your free book today!\n\u003e http://p.sf.net/sfu/13534_NeoTech\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e\n\n\n\n-- \nJeff Garzik\nBitcoin core developer and open source evangelist\nBitPay, Inc. https://bitpay.com/",
"sig": "b4e45e338ae308dc3e8468034c626c5f6b1e7caa921389bc175d4d60229e89f958e61387fecdb7315f329c8b328a2b50b68cda02d4a90e897b2b21ef32dadb70"
}