Sunday, October 25, 2026
Archived at the end of the day (US Eastern). Price, the lock, the Knots fight and what people are saying.
🔒 17,476 XBT locked, unlock in 893 blocks (about 6 days). Live unlock tracker
What changed
- LockKnots #469 was reopened: Softfork: Continue RDTS, with a rolling 40320-block (~280-day) coinbase maturity (builds on #467)
- BuildKilowallet released Kilowallet 1.3.4
- BuildKilowallet released Kilowallet 1.3.3
- BuildKilowallet released Kilowallet 1.3.3-beta4 (pre-release)
- BuildKilowallet released Kilowallet 1.3.3-beta3 (pre-release)
- BuildKilowallet released Kilowallet 1.3.3-beta2 (pre-release)
- BuildKilowallet released Kilowallet 1.3.3-beta1 (pre-release)
- BuildKilowallet released Kilowallet 1.3.2
- BuildKilowallet released Kilowallet 1.3.1
- BuildKilowallet released Kilowallet 1.3.1-beta3 (pre-release)
- BuildKilowallet released Kilowallet 1.3.1-beta2 (pre-release)
- BuildKilowallet released Kilowallet 1.3.1-beta1 (pre-release)
Said today on the Knots PRs
“After staying further away from the community discussion for the past 24 hours and taking more time to reflect on the situation; I am joining Greg in this position. Not because I don't think the 45 day CBM has been ineffective rather, because I believe it has. We are not allowing that change to fully sunset before assessing threats anew. This effectively disallows the ability to conduct proper evidence based …”
SeventyEi8ht on #468 · 18h ago
“Concept ACK of rCBM of 180 days. This PR is strictly worse than 478. It is however better than going back to 100 days.”
ghastlyxbt on #468 · 10h ago
“Concept ACK. I do like this approach better than 468. (Thanks @MarcanoFilms) Keeping the maturity policy separate from RDTS gives us more flexibility, and allows us to address RDTS on its own without worrying about other things that we've layered onto its expiration.”
stackitdeep on #476 · 10h ago
“Concept NACK. Too small CBM to be effective.”
ghastlyxbt on #480 · 11h ago
“Concept ACK. This is the best solution we currently have. 180 days is plenty to deter blind hashing for profit. I don’t buy the nonsense around not wanting to touch the maturity of already mined coins. We have been very clear on what our goals are. If 180 days turns out to be insufficient for blind hashing deterrence I’m more than happy to extend it to a year. Also I’m more comfortable with a trial of this until …”
ghastlyxbt on #478 · 11h ago
Lock proposals still open
- #468 T.Softfork: consensus: 180-day rolling coinbase maturity from height 979919 until RDTS expiry 4 approvals
- #404 Consensus: Batched extended coinbase maturity temporary softfork 1 approval
- #409 Consensus: Batched extended coinbase maturity temporary softfork /w hash based random maturity instead of deterministic height based 1 approval
- #429 T.Softfork: Long coinbase maturity (part 2 of 3): extend from 45 days to 1 year 1 approval
- #476 Softfork: 1-year rolling coinbase maturity, no release cliff, independent of RDTS 1 approval
- #478 Softfork: 180-day rolling maturity from 973440 built on #468 1 approval
- #397 [WIP] consensus: Relock outputs of early coinbase spends 0 approvals
- #434 T.Softfork: Release long coinbase maturity in four periods 0 approvals
- #469 Softfork: Continue RDTS, with a rolling 40320-block (~280-day) coinbase maturity (builds on #467) 0 approvals
- #480 45 Day Maturity Softfork - Permanent 0 approvals
- #482 Cover the historical coinbase maturity window on regtest 0 approvals
Stories and takes
- TideHash opens a BLAKE2b hashrate market: rent XBT mining power from $2.56 per TH a day xbt.live
- #468 fixes the future. The Nov 1 cliff is still on, and Knots policy is the only brake xbt.live
- Spending USD, Or Bitcoin Instead? Bitcoin University