{"type":"rich","version":"1.0","author_name":"npub12ftsvulestm9ztkjkgkl7cfurm6u6dau835evhcs3jwxyctn4y6qsk0jt6","author_url":"https://nostr.ae/npub12ftsvulestm9ztkjkgkl7cfurm6u6dau835evhcs3jwxyctn4y6qsk0jt6","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2016-08-03\n📝 Original message:This would honestly work. It forces the attacker to go through with the\nclearing phase which simultaneously makes it possible to \"cancel\" the TX\nthrough another logic branch before the timeout occurs. I'd say that would\nmeet the needs of a clearing mechanism / fraud prevention system for an\nexchange perfectly while requiring minimal changes to the software.\n\nVery, very smart idea. A++, would read again.\n\nOn Thu, Aug 4, 2016 at 9:55 AM, Tier Nolan via bitcoin-dev \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e On Wed, Aug 3, 2016 at 7:16 PM, Matthew Roberts via bitcoin-dev \u003c\n\u003e bitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e\n\u003e\u003e The reason why I bring this up is existing OP codes and TX types don't\n\u003e\u003e seem suitable for a secure clearing mechanism;\n\u003e\u003e\n\u003e\n\u003e I think reversing transactions is not likely to be acceptable.  You could\n\u003e add an opcode that requires that an output be set to something.\n\u003e\n\u003e [target script] SPENDTO\n\u003e\n\u003e This would require that [target script] is the script for the\n\u003e corresponding output.  This is a purely local check.\n\u003e\n\u003e For example, if SPENDTO executes as part of the script for input 3, then\n\u003e it checks that output 3 uses the given script as its scriptPubKey.  The\n\u003e value of input 3 and output 3 would have to be the same too.\n\u003e\n\u003e This allows check sequence verify to be used to lock the spending script\n\u003e for a while.  This doesn't allow reversal, but would give a 24 hour window\n\u003e where the spenders can reverse the transaction.\n\u003e\n\u003e [IF \u003c1 day\u003e CSV DROP \u003clive public key\u003e CHECKSIG ELSE \u003coffline protected\n\u003e key\u003e CHECKSIG] SPENDTO \u003clive public key2\u003e CHECKSIG\n\u003e\n\u003e Someone with the live public key can create a transaction that spends the\n\u003e funds to the script in the square brackets.\n\u003e\n\u003e Once that transaction hits the blockchain, then someone with the \u003coffline\n\u003e protected key\u003e has 24 hours to spend the output before the person with the\n\u003e live keys can send the funds onward.\n\u003e\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20160804/4eda2f65/attachment.html\u003e"}