On 10 October at 07:22 UTC, BTX block 244,000 switched on three new checks that every up to date node now enforces. They were scheduled in advance by BTX 0.34.14, and 0.34.15 keeps them and fixes a stall 0.34.14 could hit while catching up.
What changed, in plain words
- Timed payments (HTLCs) must use a 32 byte secret. - Shielded recovery proofs now count toward a block's verification budget. - A block header that only passed a quick first check can no longer be treated as the newest block. A block has to be fully checked to lead.
Who needs to do what
- You run your own BTX node: upgrade to 0.34.15. Nothing older than 0.34.14 follows the chain. If you come from 0.34.13 or older, note that an unset -reorgpolicy now means legacy; set -reorgpolicy=bounded to keep the behaviour you had. - You run easyNode: 0.7.8 and later carry 0.34.15. The app fetches the update itself and installs it on the next relaunch. If yours shows an older version, download it again on the nodes page. - You mine on a pool: nothing to do. The pool runs the node. - You hold BTX in a wallet: nothing to do. Your coins were never at risk.
What it looked like
A node on an older build does not stop with an error. It keeps running and can follow a branch the rest of the network has refused, while looking perfectly healthy. Our own explorer's two nodes were on 0.34.12 and did exactly that after block 244,089, until they were moved to 0.34.15 on the evening of 10 October. Mining carried on normally throughout.
You can check which build to run, and every earlier rule change, on the btxscan status page.