Good morning list,
I would like to speculate on the addition of an opcode which would provide
replay protection and allow chain-backed trustless creation of hardfork futures
payment channels.
Note however that in order to work, the hardfork must "cooperate" by changing
the operation of OP_CHEC
I guess I wasn't clear on the wildcard, `nForkId=0`
This proposal puts Bitcoin at `nForkId=1`, with the purpose of having
`nForkId=0` valid on *all* future forks. This means you can create a
`nLockTime` transaction, delete the private key and still be assured to not
lose potential future tokens
