{"type":"rich","version":"1.0","author_name":"npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2","author_url":"https://nostr.ae/npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2015-09-17\n📝 Original message:-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA512\n\n\n\nOn 17 September 2015 12:14:38 GMT-07:00, \"Jorge Timón via bitcoin-dev\" \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003eFill or kill us normally used for trades and I think it can be\n\u003econfusing.\n\u003ePrevious times this has been discussed it has been discussed under\n\u003enExpiryTime or op_height (which enables expiration), for example, in\n\u003ethe\n\u003efreimarkets white paper.\n\u003e\n\u003eAs Mark points out this can be made safe by requiring that all the\n\u003eoutputs\n\u003eof a transaction that can expire have op_maturity/csv/rcltv of 100.\n\u003eThat\n\u003emakes them as reorg-safe as coinbase transactions. Unfortunately this\n\u003edoesn't play very well with p2sh...\n\nWhy wouldn't that work with p2sh? It can be implemented by a \"treat like Coinbase\" flag in the UTXO set, set when the output is created.\n-----BEGIN PGP SIGNATURE-----\n\niQE9BAEBCgAnIBxQZXRlciBUb2RkIDxwZXRlQHBldGVydG9kZC5vcmc+BQJV+0Ip\nAAoJEMCF8hzn9Lncz4MIAIQpz7tKbmjEuETX6BnPatJ50I+kS6CQ4eE+e1irXpbb\nOCMe0A2TGzw9G5t7DgMU1lCcbcbuqOxMOrHYXuGsGkpVtRrLFbkS/F9vCS2RJT0w\nkRkL2ecN8riAjh1lUUgY1CEgVyhkwh6Rw1ZALu3Ba2tISysMfXjAW1GiLHlgxP7g\nxD6zS0OTTokG/7+s1hGK2Nd4q/ZHnfOO1JgiBzrykGNq4enp7nRhiZKhnc/0ILJA\n3WAsAMI14ZUxs95onjey7J3100tZBetYr14jzLRvf+w1klBNSvcen9dr+VhdyXYk\nMPMOwuUtq4OI1vt3HDoMjNFT6olg0gTxzWe8Grn96S4=\n=pP3Q\n-----END PGP SIGNATURE-----"}