Skip to content

Bitflash 1.2.32

Choose a tag to compare

@github-actions github-actions released this 09 Nov 13:38
· 126 commits to main since this release

Testnet nodes and miners: upgrade before 2026-11-20 12:00 UTC. Rules v4 switch on there that day, five weeks earlier than 1.2.31 said.

Every mainnet node: upgrade before 2026-12-25 12:00 UTC. Rules v4 switch on on mainnet at that moment, the same moment atomic swaps open, and a node that has not upgraded leaves the chain at the first block that uses them (below). Not only miners and pools: wallets, explorers, exchanges, every node. Rules v3 still switch on on 2026-11-21 12:00 UTC, as announced; 1.2.31 already covers that.

Rules v4: the dates

Relative lock time (BIP68 and OP_CHECKSEQUENCEVERIFY), OP_CHECKTEMPLATEVERIFY and OP_CHECKSIGFROMSTACK, described in the 1.2.31 notes and in docs/rules-v4.md:

  • testnet: 2026-11-20 12:00 UTC (1795176000);
  • mainnet: 2026-12-25 12:00 UTC (1798200000).

Up to and including 1.2.31, mainnet had no date. On a node without these dates the three new opcodes fail any script that uses them, as they always have, and since rules v3 every node runs the script inside a pay-to-script-hash spend. So the first block after the switch that spends a vault, a batch or an inheritance is valid to 1.2.32 and invalid to 1.2.31, and a 1.2.31 node stops following the chain there. On testnet the same holds for every node older than this release, since the date moved forward. The dates take effect only in this release.

In the wallet: a vault, a batch and inheritance

What rules v4 were written for, usable from the dates above.

  • Vault (vaultcreate, vaultunvault, vaultwithdraw, vaultrecover): coins leave only through a transaction fixed in advance, to an unvault output in the open. From there the hot key spends after a delay you choose, and the recovery key at once. A stolen hot key shows itself by the unvault, and you have the whole delay to take everything back.
  • Batch (ctvbatch, ctvexpand): one output now, unfolding later into fixed payments, by a transaction anybody can broadcast.
  • Inheritance (inheritcreate, inheritinfo, inheritrenew, inheritcancel, inheritpackage, inheritimport, inheritclaim): coins pass to an heir once the owner has gone quiet for a set period. The owner's wallet renews by itself at half the period. The heir's package holds no key. See docs/inheritance.md.

Contracts are kept in v4contracts.json beside the wallet. Back it up with the wallet.

All three were proven with coins on an isolated testnet bench, every valid path spent and every invalid one tried.

P2Pool, inside the node

Pooled mining with no pool: every node with -p2pool holds and relays a share chain, and every block's coinbase pays the miners of the last 2160 shares in proportion to their work. No operator, no custody, no fee, nobody to switch off. Main-chain consensus does not change.

  • -p2pool serves stratum on 127.0.0.1:3333; point XMRig at it, or run mine.sh p2pool / mine.cmd p2pool.
  • -p2poolpayto=ADDRESS picks where payouts go. By default it is a fresh address of the node's own wallet, changed every 24 hours.
  • Proven on testnet: blocks paid both miners, the payouts matured and were spent.

The central pool stays up until P2Pool has paid real mainnet blocks to several miners. See docs/p2pool.md.

Atomic swaps: more chains, from 2026-12-25 12:00 UTC

Swaps open on mainnet on 2026-12-25 12:00 UTC, as announced. Besides Bitcoin, the wallet and btfchat now swap with Litecoin, Bitcoin Cash, eCash, Dogecoin, DigiByte and Ravencoin: the same contract, no server of anyone's.

  • RPC: coinswapinfo, coininitiate, coinparticipate, coinauditcontract, coinredeem, coinrefund, coinfindsecret and the rest take the chain first, e.g. coininitiate ltc <address> <amount>. The btc* calls are unchanged.
  • btfchat: an offer names its chain, in the window's form or as offer 100 BTF for 2 LTC.
  • Each chain works through its own node or an embedded light client over Tor, which checks every header's proof of work. Ravencoin's test network is node only.
  • On chains whose difficulty eases quickly (Dogecoin, Bitcoin Cash, eCash, DigiByte, Ravencoin), mainnet confirmations count by work, not by blocks, so a private chain of easy blocks does not pass for a deep payment.

Public swaps on the test networks of Litecoin, Bitcoin Cash, Dogecoin and DigiByte are recorded in docs/atomic-swaps.md. Before mainnet opens, each chain gets a swap on its main network (docs/swaps-multicoin.md, "Proof before opening"). Ravencoin's test network did not answer and no eCash test coins came, so the first public swap of those two will be that one; both are proven on a private test chain.

An explorer in the wallet

Explorer in the menu, and view beside each transaction. It finds a block by height or hash and a transaction by id, one still waiting included, and shows the fee and which transaction spent each output. It reads only your own node's files, so a lookup tells no website what you looked at, and it keeps working with every site down.

Fixed

  • Blocks over 1 MB. The solo miner and the pool still capped their templates at the 16 MB message limit from 0.1.0. With more than a megabyte of transactions waiting, every block they built failed its own size check, and no block was found until the memory pool drained.
  • Lock room for a full block. Connecting a block is one database transaction, holding a lock on every page it touches. The limit was 10000, inherited. The same full block of small transactions took 7921 locks on one machine and 13976 on another, because the page size comes from the filesystem, so it could pass on one node and stop another. The limit is now 537000, Bitcoin's figure since March 2013, at a cost of about 38 MB at peak. The chain is far from that today.
  • A node left with one peer asked it for blocks only if it was the first peer of the run, and otherwise sat behind until a block was announced.
  • The Bitcoin light client's minimum-work anchors now come from Bitcoin Core v31.1.
  • An isolated testnet bench node (-isolate) now keeps every light client to its own peers (-btcpeer, -ltcpeer and the others) as well, and dials no Nostr relay.
  • Inheritance could freeze the node. The automatic renewal and an inheritance call made at the same moment took two locks in opposite orders, and the whole node stopped. They take them in the same order now.
  • vaultrecover when someone else broadcast the unvault. The unvault needs no key, so a thief with the hot key can send it. Recovery then refused with "not unvaulted yet". It now finds the unvault, whoever sent it, and vaultunvault says when someone else already did.
  • v4contracts.json is written safely. It is replaced in one step after it is on the disk, the version before is kept as v4contracts.json.bak, the file is checked before coins are locked, and if a save fails after, the answer carries the script so it is not lost.
  • Swaps. A contract is accepted only exactly as the wallet would write it (a contract with its data pushed the long way passed the check, and could never be redeemed on Bitcoin Cash or eCash). A contract spent where the node cannot yet read the spend no longer ends the swap as done. On mainnet a Bitflash contract counts after 30 blocks, an hour, since RandomX can be rented by the hour. The fee of a redeem sent again now rises on Dogecoin, DigiByte and Ravencoin too.
  • Light clients. Two lying peers can no longer make cheap blocks count as an hour of confirmations; one answer can no longer fill the table of peers; a weak fork can no longer fill memory with headers; and Bitcoin filters on mainnet come from two peers or not at all.
  • P2Pool. Shares far easier than the tip's are not kept or relayed, a forged copy can no longer get an honest peer banned, and share messages no longer hold up the rest of the node.
  • The RPC server is refused at start when its port, the default one included, is one the node publishes on its onion.

Windows

  • Bitflash.exe and BtfChat.exe carry version information.
  • The Miner package no longer ships WinRing0x64.sys, which Windows reports as a vulnerable driver. XMRig loads it only when run as administrator, which mine.cmd never does, so nothing changes in hash rate.
  • docs/windows-defender.md explains what Defender flags, why, and how to report a false positive to Microsoft.

Downloads

  • Bitflash-1.2.32-windows-with-tor.zip: the wallet (Bitflash.exe) and btfchat (BtfChat.exe), with Tor.

  • Bitflash-1.2.32-x86_64.AppImage and BtfChat-1.2.32-x86_64.AppImage: the wallet and btfchat for Linux, with Tor.

  • bitflash-node-1.2.32-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.32-macos-arm64.tar.gz: macOS on Apple silicon, from Terminal: the node, btfchat and Tor. Now needs macOS 15 (Sequoia) or newer: GitHub retired the macOS 14 build machines on 2026-11-02, and the libraries built on macOS 15 need it.

  • Bitflash-Miner-1.2.32-{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. Every package now holds a copy.

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. New files appear beside it only when used: v4contracts.json (vaults, batches, inheritance), p2pool.dat, and the light clients' header stores.

Verify what you download

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

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