On Fri, Sep 18, 2015 at 12:44 AM, Peter Todd <p...@petertodd.org> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > > > On 17 September 2015 12:14:38 GMT-07:00, "Jorge Timón via bitcoin-dev" > <bitcoin-dev@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.
That would work. I was thinking about requiring OP_MATURITY 100 (or greater than 100) in all the scriptPubKey's of the expiry transaction. _______________________________________________ bitcoin-dev mailing list bitcoin-dev@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
