rich1.0npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2https://nostr.ae/npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2njumphttps://nostr.ae📅 Original date posted:2015-09-17 📝 Original message:-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 17 September 2015 12:14:38 GMT-07:00, "Jorge Timón via bitcoin-dev" <bitcoin-dev at lists.linuxfoundation.org> wrote: >Fill or kill us normally used for trades and I think it can be >confusing. >Previous times this has been discussed it has been discussed under >nExpiryTime or op_height (which enables expiration), for example, in >the >freimarkets white paper. > >As Mark points out this can be made safe by requiring that all the >outputs >of a transaction that can expire have op_maturity/csv/rcltv of 100. >That >makes them as reorg-safe as coinbase transactions. Unfortunately this >doesn't play very well with p2sh... Why 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. -----BEGIN PGP SIGNATURE----- iQE9BAEBCgAnIBxQZXRlciBUb2RkIDxwZXRlQHBldGVydG9kZC5vcmc+BQJV+0Ip AAoJEMCF8hzn9Lncz4MIAIQpz7tKbmjEuETX6BnPatJ50I+kS6CQ4eE+e1irXpbb OCMe0A2TGzw9G5t7DgMU1lCcbcbuqOxMOrHYXuGsGkpVtRrLFbkS/F9vCS2RJT0w kRkL2ecN8riAjh1lUUgY1CEgVyhkwh6Rw1ZALu3Ba2tISysMfXjAW1GiLHlgxP7g xD6zS0OTTokG/7+s1hGK2Nd4q/ZHnfOO1JgiBzrykGNq4enp7nRhiZKhnc/0ILJA 3WAsAMI14ZUxs95onjey7J3100tZBetYr14jzLRvf+w1klBNSvcen9dr+VhdyXYk MPMOwuUtq4OI1vt3HDoMjNFT6olg0gTxzWe8Grn96S4= =pP3Q -----END PGP SIGNATURE-----