On Thursday, October 02, 2014 12:05:15 AM Peter Todd wrote: > On 1 October 2014 11:23:55 GMT-07:00, Luke Dashjr <l...@dashjr.org> wrote: > >Thoughts on some way to have the stack item be incremented by the > >height at > >which the scriptPubKey was in a block? > > Better to create a GET-TXIN-BLOCK-(TIME/HEIGHT)-EQUALVERIFY operator. > scriptPubKey would be: > GET-TXIN-BLOCKHEIGHT-EQUALVERIFY > (fails unless top stack item is equal to the txin block height) > <delta height> ADD > (top stack item is now txin height + delta height) > CHECKLOCKTIMEVERIFY
This sounds do-able, although it doesn't address using timestamps. > > A limitation of encoding the target > >height/time directly, is that miners may choose not to mine the first > >transaction until they can also take the "burn to fee". So, one may > >prefer to > >say "cannot be spent until 100 blocks after the first transaction is > >mined", > >in effect reproducing the generation maturity rule. > > You'd want these sacrifices to unlock years into the future to thoroughly > exceed any reasonable business cycle; that's so far into the future that > miners are almost certain to just mine them and collect the fees. For many use cases, short maturity periods are just as appropriate IMO. 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
