BIP 113 makes things valid which currently are not (any transaction with a locktime between the median time past, and the block nTime). Therefore it is a hardfork. Yet the current BIP describes and deploys it as a softfork.
Furthermore, Bitcoin Core one week ago merged #6566 adding BIP 113 logic to the mempool and block creation. This will probably produce invalid blocks (which CNB's safety TestBlockValidity call should catch), and should be reverted until an appropriate solution is determined. Rusty suggested something like adding N hours to the median time past for comparison, and to be a proper hardfork, this must be max()'d with the block nTime. On the other hand, if we will have a hardfork in the next year or so, it may be best to just hold off and deploy as part of that. Further thoughts/input? Luke _______________________________________________ bitcoin-dev mailing list bitcoin-dev@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
