BIP Draft: Flag day activation based on nLockTime signaling

[1440000bytes]

@sjors

I’m not sure who you’re referring to with “readiness”.

If you mean that miners are signalling readiness, then I don’t think we should encourage the idea that including a transaction is an endorsement of it.

Miners do not endorse any soft forks with signaling. Neither this BIP nor BIP 8/9 signaling is meant for endorsements.

@sjors

If on the other hand users are signalling readiness, then inclusion in a block is an unreliable metric since miners could be manipulating that in either direction.

Users are signaling support as mentioned in the BIP draft. All transactions will be mined sooner or later if there is at least one pool which can include it in the block.

@sjors

We should not creative incentives for better censorship tooling.

Ocean pool (default template) already excludes transactions with nLockTime 21. This BIP does not create incentives for censorship. All transactions will eventually get mined except if all miners decide to exclude it. In case, all miners ignore a transaction, users can use a normal nLockTime to replace the original transaction or increase fees.