Skip to content

Bitflash 1.2.34

Choose a tag to compare

@github-actions github-actions released this 14 Nov 21:26
· 93 commits to main since this release

Every node: run 1.2.34 before 2026-11-21 12:00 UTC. This release fixes a stall that keeps a new node from catching up, and it carries the two fixes from 1.2.33 that must be running when rules v3 switch on at that moment.

A new node no longer stalls while it syncs (#78)

A node installed fresh on 1.2.33 and syncing from genesis could stop partway and never resume. Most of the blocks it received arrived before their parents, were held aside as orphans, and were dropped again. Then the next block request was pushed so far into the future that it was effectively never sent.

Two things caused it. Nodes on 1.2.33 tell every peer about their newest block when they connect and at the end of each batch they serve. A syncing node took each of those messages as a reason to start a new download from that peer, so with several peers it fetched the same range in parallel, mostly out of order. And each mention of a block it was already waiting for pushed the shared retry time of that request two minutes further out.

1.2.34 downloads from one peer at a time while it catches up. It switches to another peer if that one disappears or the chain stops growing for two minutes. Retry times are kept per peer, and one announcement leads to at most one request. Nothing changes in what a node serves to others, and the change is not consensus.

While testing this release, a wallet that was 3,400 blocks behind slowed to a crawl because the one peer it picked was a new inbound connection. Blocks from such peers share a small budget that protects the node from floods, so they arrive slowly and out of order. 1.2.34 does not pick a new inbound peer while another peer can serve, and switches away from one as soon as another can (#80).

On the public networks, a node built from this release synced mainnet from genesis to the tip in about 40 minutes with 9 blocks arriving before their parents, and testnet in 19 minutes with 2. A self-test, sync-stall, pins the behaviour.

Thanks to spiff, who found the fresh-sync stall by replaying the chain from genesis on every version.

If you have a node stuck on 1.2.33: restart it. It carries on from where it stopped. Upgrading to 1.2.34 is the lasting fix.

Who must upgrade

Everyone: miners, pools, wallets, explorers, exchanges, every node. Every node needs 1.2.33 or newer before 2026-11-21 12:00 UTC, when rules v3 switch on, because of these two fixes from 1.2.33, which 1.2.34 also carries:

  • Pay-to-script-hash waits until rules v3 are locked in (#60). The wallet and relay go by the tip's median time instead of the local clock, so a C... payment made in the first minutes after the switch cannot be taken by someone who knows the redeem script.
  • Script numbers read the same on Windows and Linux (#71, consensus). A script number of 2^32 or more no longer reads differently on the two systems in OP_PICK, OP_ROLL and OP_CHECKMULTISIG.

A node installed new should be installed on 1.2.34, since 1.2.33 may not finish its first sync.

1.2.33 or newer is still required before 2026-12-25 12:00 UTC, when rules v4 switch on on mainnet and atomic swaps open. Both dates are the ones already announced and do not change.

A swap lock is refused while the node is catching up (#79)

swapinitiate and swapparticipate count a Bitflash lock from the tip's median time. On a wallet that is still syncing, that median can be days behind the clock, and a lock counted from it is already open when it is paid: the other side could refund at once. The public eCash testnet swap below found this, when a wallet that had been offline for five days made an 18 hour lock that had opened three days earlier. Nothing was lost: the swap was stopped and that lock refunded.

Both calls now refuse while the median time is more than an hour behind the clock, the same hour the chat already waited on for a taker giving BTF. A synced node makes the same lock as before. Not a consensus change. Swaps open on mainnet on 2026-12-25, so no mainnet coins were exposed.

Swap proof: BTF and XEC on the public testnets

This release build swapped 3 tBTF for 996.78 tXEC between the Bitflash testnet and the eCash testnet, both wallets on the built-in eCash light client. The participant's tXEC redeem used the secret that the initiator's tBTF redeem put on the Bitflash chain. The locks are tXEC and tBTF.

Also

  • SECURITY.md: how to report a vulnerability, and where the audit is.

Everything else is as in 1.2.33. Its notes, and the full audit with every finding, are at https://github.com/bitflash-network/bitflash/releases/tag/v1.2.33 and in docs/AUDIT.md.

Downloads

  • Bitflash-1.2.34-windows-with-tor.zip: the wallet (Bitflash.exe) and btfchat (BtfChat.exe), with Tor.
  • Bitflash-1.2.34-x86_64.AppImage and BtfChat-1.2.34-x86_64.AppImage: the wallet and btfchat for Linux, with Tor.
  • bitflash-node-1.2.34-x86_64: the headless node for servers, for Debian 13 / Ubuntu 24.04 and later (sudo apt install libsodium23 libdb5.3++ libsqlite3-0 libssl3t64). On other distributions, use the AppImage.
  • Bitflash-1.2.34-macos-arm64.tar.gz: macOS 15 or newer on Apple silicon, from Terminal: the node, btfchat and Tor.
  • Bitflash-Miner-1.2.34-{windows.zip,linux.tar.gz,macos-arm64.tar.gz}: XMRig and Tor, wired to the pool's onion.
  • THIRD-PARTY-NOTICES.txt: the licenses of everything the packages carry.

Packages come out the same from the same commit; to check one against a build of your own, follow docs/release-verification.md.

Upgrading

Stop the node, replace the binary, start. Nothing in the data directory changes shape.

Verify what you download

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

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