On Saturday 13 May 2017 4:23:41 AM Russell O'Connor wrote: > I recall chatting about this idea recently and my conclusion was the same > as Peter Todd's conclusion: this will just encourage miners to false signal > readiness with undermines both BIP 9 and BIP 8.
I already explained why this isn't the case: If we're comparing MASF to MASF+CBV, then I agree. But MASF is not necessarily always on the table, so the comparison where this becomes relevant is MASF+CBV vs UASF. > I felt that rather than using script system for this construction, it would > be better to use the transaction version number instead by soft-forking in > a rule that says when the most significant bits of a transaction version > are 001 then the transaction can only be included in blocks whose lower 29 > version bits are set at the same position as the lower 29 version bits set > in the transaction version. Versionbits change/lose their meaning after the deployment timeout. For this reason, the timeout must be specified so the check is skipped when that occurs. Also, doing it the way you describe would fail to enforce that BIP9 is actually in use for the block version; you could simply add that as an additional condition, but it seems pretty hacky since you wouldn't be able to upgrade versionbits anymore... > While I think that making use of the transaction version number is superior > to adding an opcode, because it doesn't interfere with caching of script > validity Script validity can still be cached with this: you would always allow the opcode to succeed at evaluation-time, and simply store the criteria checked separately. Then it would behave effectively the same as using the transaction version number. Luke _______________________________________________ bitcoin-dev mailing list bitcoin-dev@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
