On Friday, October 03, 2014 2:28:17 PM Matt Whitlock wrote: > Is there a reason why we can't have the new opcode simply replace the top > stack item with the block height of the txout being redeemed? Then > arbitrary logic could be implemented, including "output cannot be spent > until a certain time" and also "output can ONLY be spent until a certain > time," as well as complex logic with alternative key groups with differing > time constraints.
This cannot be done in a softfork. Furthermore, "output can ONLY be spent until a certain time" contradict's Bitcoin's present security assumptions: that assuming a honest sender, the transaction will remain valid and simply re-confirm if a reorg kicks it out. Luke ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
