<oembed><type>rich</type><version>1.0</version><author_name>npub12rkw0jajmsck4uwdtksdvtswrlkypusfryjzera7m4fhqta6jhdsz3aqxc</author_name><author_url>https://nostr.ae/npub12rkw0jajmsck4uwdtksdvtswrlkypusfryjzera7m4fhqta6jhdsz3aqxc</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2014-03-10&#xA;📝 Original message:I was wondering if there would be merit in a kind of BIP for a payment&#xA;protocol using multisig?&#xA;&#xA;Currently, setting up a multisig is quite a feat. Users have to exchange&#xA;public keys, work out how to get the public keys from their addresses. If&#xA;one of the parties are not savvy enough, an malicious party could easily be&#xA;setup that was 2 of 3 instead of 2 of 2 where the malicious party generates&#xA;the multisig address+script and thus be able to run off with funds anyway.&#xA;&#xA;It&#39;s also terribly complex to generate and keep track of. There&#39;s been a&#xA;nice attempt at creating an browser interface at coinb.in/multisig but it&#xA;still lacks the kind of ease with created by the payment protocol. If there&#xA;was a BIP then it would go a long way to aiding future usability of&#xA;multisig wallet implementations.&#xA;&#xA;What are your thoughts?&#xA;&#xA;Drak&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140310/0b5ecd92/attachment.html&gt;</html></oembed>