{"type":"rich","version":"1.0","author_name":"npub1xpryrka5nmn2vq9uum4qfjcvkfdne95l3ug4sxhdkcnndu4uu6eqrc6eq0","author_url":"https://nostr.ae/npub1xpryrka5nmn2vq9uum4qfjcvkfdne95l3ug4sxhdkcnndu4uu6eqrc6eq0","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2011-08-24\n🗒️ Summary of this message: Gavin Andresen requested open-source, patent-free, and thoroughly-tested code for DSA-key-splitting. A third-party solution was suggested for a more traditional escrow setup.\n📝 Original message:On Aug 24, 2011 10:12 AM, \"Gavin Andresen\" \u003cgavinandresen at gmail.com\u003e wrote:\n\u003e\n\u003e If anybody has some open-source, patent-free, thoroughly-tested code\n\u003e that already does DSA-key-splitting, speak up please.\n\u003e\n\nIf the caveat of a trusted third party is acceptable and, as greg mentioned,\nif there was a way to export unsigned transactions and then import/broadcast\nafter signing this becomes fairly trivial.\n\nShamir's + 3rd party to combine and sign means no protocol level changes.\n\nProcess could work something like this:\n\nParties agree to endpoint destination address and provide it to third party.\nThird party generates key and provides shares to each party in the txn and\nthe resulting address to both as well.\nThird party destroys (preferably, never stores) private key.\nSender sends to address.\nBoth parties after confirmation of reciept of goods or what have you provide\nshares back to third party who uses the privkey to xfer inputs to the\npreviously agreed upon destination subtracting their fee.\n\nThis resembles more traditional escrow setups and relies on the trust of a\nthird party, which is not ideal, but would be fairly simple to implement\nuntil the other proposals could be better investigated and implemented.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20110824/a6faa861/attachment.html\u003e"}