While I think this is an important use case, the current BIP doesn't reasonably support it. Unfortunately, I have to agree that addressing this use case may be more trouble than it's worth right now.
BIP0065: Provide warning about miner incentives for proof-of-sacrifice #121
pull luke-jr wants to merge 1 commits into bitcoin:master from luke-jr:bip0065 changing 1 files +8 −0-
luke-jr commented at 3:38 PM on November 13, 2014: member
-
BIP0065: Provide warning about miner incentives for proof-of-sacrifice 829cb840f8
-
petertodd commented at 7:04 AM on December 17, 2014: contributor
Given that real-world proof-of-sacrifice applications will be using unlocking far off into the future to get past business cycles I'm pretty skeptical that this will actually be an issue.
In any case a better pull-req would be to describe how a future OP_CHECKBLOCKHEIGHTVERIFY opcode could be used in conjunction with CLTV to solve this problem, e.g:
scriptPubKey: CHECKBLOCKHEIGHTVERIFY 52560 ADD CHECKLOCKTIMEVERIFYspent with:
scriptSig: <blockheight of transaction containing scriptPubKey> -
laanwj commented at 8:23 AM on May 26, 2015: member
@luke-jr are you planning on reworking this change according to @petertodd's comment, or should this be closed?
- laanwj closed this on Jun 22, 2015
- jonatack referenced this in commit 3f62751809 on Nov 12, 2019
