1 2017-10-21 00:03:21 <prestwich> has anyone considered transaction expiries? Kindof the opposite of timelocks. They'd render transactions invalid after specific time
 2 2017-10-21 00:04:09 <prestwich> I'm looking into HTLCs and atomic trades, and being able to expire specific transactions, or having expiry ops in scripts seems very useful
 3 2017-10-21 04:48:04 <meshcollider> in what script would you put such an op code
 4 2017-10-21 07:13:18 <\x> hello
 5 2017-10-21 07:13:28 <\x> why cant I brodcast 0-fee on 0.15 now?
 6 2017-10-21 07:13:51 <\x> it works on 0.14 and 0.14 s2x
 7 2017-10-21 07:13:54 <\x> aka btc1
 8 2017-10-21 07:14:10 <\x> is there a way for me to brodcast 0-fee?
 9 2017-10-21 07:16:05 <\x> back then I can brodcast 0-fee on coins with high coin days destroyed
10 2017-10-21 15:50:57 <LowKey> Hi, I have  questions, what meaning of ProcessBlock() : CheckBlock FAILED & CheckBlock() : first tx is not coinbase , is it wallet issue?
11 2017-10-21 16:33:50 <prestwich> meshcollider: you'd have to do a protocol layer expiry, and an opcode expiry for script. You'd use the opcode to change spending conditions over time. Right now execution paths can become valid after time, but not invalid after time.
12 2017-10-21 16:35:06 <prestwich> Example: a p2sh multisig that rotates owner pubkeys over time.