{"type":"rich","version":"1.0","author_name":"npub1g6vxlp4e0nyhs2dqxxcryztyf5f5hyuaq93nw4r87zcnv0sdsa0qqsl5wd","author_url":"https://nostr.ae/npub1g6vxlp4e0nyhs2dqxxcryztyf5f5hyuaq93nw4r87zcnv0sdsa0qqsl5wd","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2016-08-03\n📝 Original message:On Wed, Aug 3, 2016 at 7:16 PM, Matthew Roberts via bitcoin-dev \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e The reason why I bring this up is existing OP codes and TX types don't\n\u003e seem suitable for a secure clearing mechanism;\n\u003e\n\nI think reversing transactions is not likely to be acceptable.  You could\nadd an opcode that requires that an output be set to something.\n\n[target script] SPENDTO\n\nThis would require that [target script] is the script for the corresponding\noutput.  This is a purely local check.\n\nFor example, if SPENDTO executes as part of the script for input 3, then it\nchecks that output 3 uses the given script as its scriptPubKey.  The value\nof input 3 and output 3 would have to be the same too.\n\nThis allows check sequence verify to be used to lock the spending script\nfor a while.  This doesn't allow reversal, but would give a 24 hour window\nwhere the spenders can reverse the transaction.\n\n[IF \u003c1 day\u003e CSV DROP \u003clive public key\u003e CHECKSIG ELSE \u003coffline protected\nkey\u003e CHECKSIG] SPENDTO \u003clive public key2\u003e CHECKSIG\n\nSomeone with the live public key can create a transaction that spends the\nfunds to the script in the square brackets.\n\nOnce that transaction hits the blockchain, then someone with the \u003coffline\nprotected key\u003e has 24 hours to spend the output before the person with the\nlive keys can send the funds onward.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20160804/3e551535/attachment-0001.html\u003e"}