|
Title: CHECKLOCKTIMEVERIFY with "relative" block numbers? Post by: bmking on March 07, 2015, 11:29:06 PM I was reading about the proposal for CHECKLOCKTIMEVERIFY as an OP Code. The way I understand it, you can specify in your transaction, that it can only be used as an input to a new transaction (meaning it can only be spend), if the new transaction uses an nLockTime at least as great as the CHECKLOCKTIMEVERIFY specified for the input. So in general it is possible to include a specific date or block for the CHECKLOCKTIMEVERIFY, for which you know that before this date/block is reached the transaction cannot be spent. But what about if you want to make a raw transaction containing CHECKLOCKTIMEVERIFY in such a way, that it will first be spendable after e.g. 144 blocks from the moment the transaction has been included in a block (e.g. "mined")? Is such a functionality planned with CHECKLOCKTIMEVERIFY? Because I think it could be very useful in regard of Never-Closing Payment Channels. Title: Re: CHECKLOCKTIMEVERIFY with "relative" block numbers? Post by: btcdrak on October 03, 2015, 04:12:29 PM This feature is planned now according to BIP68 and BIP112 which will introduce a new opcode called OP_CHECKSEQUENCEVERIFY.
|