Luke Dashjr is against the 180-day lock, but says he'll accept it
Bitcoin Knots maintainer Luke Dashjr says he is against extending XBT's coinbase lock, and would rather let it expire at block 979,920 next week. But he says the decision isn't his, the community "seems to clearly support it," and he will accept it. That points toward the 180-day rolling lock shipping in the next Knots release.

What he said
Posting on X on Oct 22 (@LukeDashjr), quoting his own poll from two days earlier on what the community agrees on:
"Just to be perfectly clear: I am against this. I think we should let the long CBM expire in a week and move on, focus on building back what we lost.
But it's not my decision, and the Bitcoin community seems to clearly support it, so I will accept it."
He followed up with two more posts:
"Currently, all pools require DATUM in one way or form. As long as that continues, I don't think we need further consensus-level enforcement. If someone walks back later, we can always do a longer maturity + canceling payments at that time."
"Longer maturity doesn't have much purpose beyond making it possible to cancel payments. And much shorter than 1 year doesn't give enough time to coordinate the cancellations.
Ordinarily, all softforks should really be _released_ with a year lead time before activation..."
What it means
- The 180-day lock is on track. PR #468 has three tested approvals, broad community support, and is already in the 29.4.3rc2 community test build. The maintainer saying he'll accept it removes the biggest open question. It still needs to be merged and released. What's in rc2
- His case against it: pools already require DATUM, so the original goal is met; the real use of a long lock is to cancel bad actors' payments, and 180 days is too short to coordinate that; and soft forks normally deserve a year's notice, not ten days.
- Voiding stays on the table, later. He describes "longer maturity + canceling payments" as a tool to use if pools walk back DATUM, not something needed now. The same debate ran through the #468 review thread, where several reviewers said they oppose voiding any mined reward.
- Nothing changes for coins locked now. Under #468 or no change at all, the roughly 20,000 XBT locked since block 973,440 unlock at block 979,920, around Oct 31 to Nov 1. Live countdown
Our take
This is how it should work. The maintainer disagreed in public, gave his reasons, and deferred to what node runners and reviewers asked for. Whatever you think of 180 days, that's a healthier process than the one XBT left behind on the SHA-256 chain, where a few pools and companies decided BIP-110's fate.
All the lock optionsUnlock countdown
Sources: Luke Dashjr's posts on X, Oct 22, 2026; Bitcoin Knots PR #468 and the knots-dev 29.4.3rc2 release notes. "Our take" is xbt.live's opinion. Not financial advice.
Have an XBT story? Write for xbt.live.