Skip to content

Bitflash 1.2.28

Choose a tag to compare

@NSable-sh NSable-sh released this 23 Sep 14:10
· 326 commits to main since this release

The switch happened. Mainnet block 38841, 2026-09-21 12:00:58 UTC, was the first mined under PoW v2 and the consensus rules v2 announced in 1.2.26. This release changes nothing in consensus: a 1.2.26 or 1.2.27 node follows the same chain. What 1.2.28 brings is everything around it — the network layer, the wallet, Tor where Tor is blocked — built and tested on the side while the switch was waited for.

Network: what Bitcoin 0.2–0.3 taught the P2P layer

Protocol 102, negotiated per peer; a 101 peer is spoken to exactly as before.

  • A checksum on every message. Four bytes of the payload's double-SHA256 in the header, as Bitcoin added in 0.2.9. A corrupted or truncated message is dropped where it arrives instead of being parsed.
  • Misbehaving peers are scored and banned. Malformed blocks, invalid proof of work, nonsense messages: each carries a score, and a .btf address that reaches 100 is refused for 24 hours. Diagnostics shows the count.
  • Initial block download is a state. A node more than three blocks behind what its peers report neither mines nor announces blocks until it is level, so a freshly started miner does not extend a stale tip.
  • Block data is synced to disk before the index points at it. Three nodes on one machine lost their index to a hard reset on 2026-09-17 and failed to start with "Cannot read the block index"; the bytes the index named had never reached the platter. Flush and fsync now, every block (every 500th while catching up).
  • A deadlock that could stall RPC and relay, present since 0.1.0: the message thread held a peer's send lock while waiting for the main lock, and an RPC call held the main lock while pushing a message to that peer. Found while testing, fixed as Bitcoin 0.3 did. This one matters to an exchange: sendtoaddress could hang.
  • The wallet marks what it spends as spent the moment a transaction enters it, not only when the block arrives; a coin could be picked twice for two transactions built in quick succession.

docs/net-hardening.md.

Tor where Tor is blocked

  • A ladder of transports, climbed on its own. Managed Tor reaches no peer within four minutes — or cannot even fetch a directory within 90 seconds — and the node restarts it with the bundled Snowflake bridges; then obfs4, webtunnel and meek, six minutes each, the bridge lines taken from Tor Browser's list shipped beside the transports. The onion address is kept across every restart. What worked is remembered, so the next start begins there. Tor's own bootstrap is read over the control port the whole time and shown in Diagnostics, in Options → Tor & Censorship and in the gettorinfo RPC, so "no peer" comes with why.
  • Bridges of your own. bridges.txt in the data directory, the paste box in Options, -torbridge=LINE, or settorbridges over RPC: lines from bridges.torproject.org, bridges@torproject.org or the Telegram bot @GetBridgesBot. Preferred over the bundled ones, never abandoned for direct Tor. -notorfallback turns the ladder off.
  • A Tor left behind is cleared. A node killed without a clean shutdown left its Tor running; every later start's own Tor then exited, and the node had inbound peers and no outbound. The pid is recorded and a stale Tor on our configuration is stopped before ours starts.
  • The releases are served over Tor at http://rqzruhh4sm2s3fl6b4mpselkqsaaxebnyptpqhdpt236g57lof7j7sid.onion/ with the signing key, for networks where the sites are blocked too.

docs/censored-networks.md has the whole picture, including what none of this can do and the legal caveat.

Wallet: multisig and raw transactions, ahead of rules v3

Bare m-of-n multisig (valid since genesis, relayed from this release) and the pay-to-script-hash shapes, with the RPC an exchange or a custodian expects: createmultisig, addmultisigaddress, decodescript, listunspent, createrawtransaction (with data: outputs), decoderawtransaction, getrawtransaction, signrawtransaction (partial signatures combine), sendrawtransaction; validateaddress reports the public key of an address this wallet holds. Pay-to-script-hash addresses (C…) are understood but refused as a destination until the rules v3 switch is scheduled: until then such an output belongs to whoever spends it first. docs/multisig.md.

One OP_RETURN output of up to 80 bytes per transaction is relayed: the burn, unspendable since 0.1.0, which a coming feature is built on (docs/btfchat.md describes the design; nothing of it ships here).

Also

  • TRADEMARK.md: what the MIT license never covered.
  • Options gained the Tor section; the diagnostics dump gained the peer protocol column, the ban count and Tor's bootstrap.

Upgrading

Stop the node, replace the binary, start. Nothing in the data directory changes shape. A 1.2.26 or 1.2.27 node is not obliged to upgrade for consensus; a node on 1.2.23 or earlier is off the chain since the switch and must.

Verify what you download

sha256sum -c SHA256SUMS
gpg --verify SHA256SUMS.asc SHA256SUMS

Signed with 910A 2B4C CA87 9E81 FB4B 2AEA 1D4A 53D3 B78A A4B8.