Skip to content

Releases

Bitflash 1.2.35

Choose a tag to compare

@github-actions github-actions released this 17 Nov 16:39

Bitflash 1.2.35: private pools with friends, LAN miners on one node, and a node that cannot check proof of work no longer accepts blocks. Recommended for every node. Not a consensus change: 1.2.33 or newer is still what rules v3 (2026-11-21 12:00 UTC) and rules v4 (2026-12-25 12:00 UTC) require.

A node that cannot set up RandomX no longer accepts blocks (#90)

If a node could not allocate the memory RandomX needs to check proof of work (about 256 MB), the check returned a hash of zero, and zero is below every target: such a node would have accepted any block's proof of work, and P2Pool shares and pool submits the same way. Nobody can cause this from outside; it needs a machine short of memory.

1.2.35 never treats a failed check as a pass. The node will not start if it cannot set up RandomX, and says how much memory it needs (about 256 MB, about 512 MB while a new node is still syncing blocks from before the PoW v2 switch). A block that cannot be checked is refused without blaming the peer and can be fetched again later; nothing is marked invalid. When RandomX works, nothing changes: same hashes, same decisions. A self-test, pow-unavailable, pins it.

Mine with friends in a private pool (P2Pool local, #83)

Create a pool, share its code and a password, and each friend mines from their own node over Tor. Payouts go straight to each member's wallet in every block the pool finds, split by the work each one did. There is no server, no operator and no account, and nobody outside the pool can see who is in it.

poolcreate local {"name":"friends"} <password>     returns the pool code
pooljoin "<pool code>" <password>                  on each friend's node
poolpeers local:friends ["ADDR@HOST.onion", ...]   each member lists the others
bitflash-node -p2pool=local:friends

These are JSON-RPC calls. Keep the password out of the command line and the shell history: docs/rpc.md shows how to send it from a prompt.

A local pool finds blocks in proportion to your machines' hashrate: rarer but larger payouts; the average is the same as any pool.

Proved on the Bitflash testnet with real coins: blocks paid each member by their share of the work, and every member spent their payout, the last run with members on two machines and one of them reaching the network only through Snowflake bridges. The default pool (pool zero) is byte for byte what it was. Details in docs/pool-registry.md, section 18.

Miners on your local network, one node (#81)

-p2poolbind=IP also serves the P2Pool stratum on a private address of your network, so every machine in the house mines through one node:

bitflash-node -p2pool -p2poolbind=192.168.1.10

Point XMRig or the Bitflash Miner on the other machines at that address (P2POOL_HOST=192.168.1.10 ./mine.sh p2pool). Only private addresses are accepted. Thanks to Marius, who asked for it.

Everpool, first part: the pool registry index

Everpool is a pool registry on the chain itself: anyone creates a pool with one burn, and nobody can edit or delete it afterwards. This release reads the registry (poollist, poolinfo; on mainnet today it holds pool zero only). poolcreate everpool shows exactly what would be recorded; burning a pool on mainnet opens in a later release, when registered pools can be carried and mined. On testnet it works now. Pools with the same name are flagged, and every pool is shown by its full id, fee and age, never by its name alone.

Also

  • The GUI's pool settings are saved under a lock, so pressing save while mining no longer races the miner threads.
  • The address row's Copy and Request buttons fit the window.

Who should upgrade

Everyone is encouraged to, for the RandomX fix. Nothing in the data directory changes shape, and 1.2.35 talks to 1.2.33 and 1.2.34 nodes as they talk to each other.

Downloads

  • Bitflash-1.2.35-windows-with-tor.zip: the wallet (Bitflash.exe) and btfchat (BtfChat.exe), with Tor.
  • Bitflash-1.2.35-x86_64.AppImage and BtfChat-1.2.35-x86_64.AppImage: the wallet and btfchat for Linux, with Tor.
  • bitflash-node-1.2.35-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.35-macos-arm64.tar.gz: macOS 15 or newer on Apple silicon, from Terminal: the node, btfchat and Tor.
  • Bitflash-Miner-1.2.35-{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.

Verify what you download

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

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

Bitflash 1.2.34

Choose a tag to compare

@github-actions github-actions released this 14 Nov 21:26

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.

Bitflash 1.2.33

Choose a tag to compare

@github-actions github-actions released this 13 Nov 12:28

Every node: upgrade before 2026-11-21 12:00 UTC. Two fixes in this release need to be running before rules v3 switch on at that moment:

  • Pay-to-script-hash waits until rules v3 are locked in (#60). For the first few blocks after the switch a miner may still date a block just before it, and such a block runs the old rules, where a pay-to-script-hash output is spent by its redeem script alone. Up to 1.2.32 the wallet and relay went by the local clock and allowed C... payments from 12:00, so a payment made in those minutes could be taken by anyone who knows the redeem script. Now they wait until the tip's median time has passed the switch, after which every valid block runs rules v3.
  • Script numbers read the same on Windows and Linux (#71, consensus). A script number of 2^32 or more read as 0 on Windows and as the largest integer on Linux. In OP_PICK, OP_ROLL and OP_CHECKMULTISIG that made a script valid on one system and invalid on the other, which would split the network. Windows nodes now read these numbers as Linux nodes always have. No block on either chain has ever used such a value (every mainnet and testnet script was scanned), so nothing about the existing chain changes. All Windows users should upgrade; after upgrading, a Windows node operator can compare the tip hash with the seeds.

1.2.33 or newer is required before 2026-12-25 12:00 UTC, when rules v4 switch on on mainnet and atomic swaps open. Not only miners and pools: wallets, explorers, exchanges, every node. The dates are the ones 1.2.32 announced and do not change.

The audit

This release is the result of a full audit of the node: manual reviews of consensus, denial of service, the wallet and its cryptography, the swaps and the light clients; fuzz harnesses for every parser that reads what a stranger sends; every self-test under AddressSanitizer, UndefinedBehaviorSanitizer, LeakSanitizer, ThreadSanitizer and Valgrind; static analysis; and a bit-for-bit reproducible build check. Every finding, the pull request that fixed it, the self-test that pins it, and what is deferred with its reason are in docs/AUDIT.md. Self-test coverage of the node went from 55% to 67% of lines.

Chain selection

  • The best chain is the one with the most work (#55). The node used to pick the tallest chain, so a shorter chain with more proof of work behind it lost to a taller one with less. It now sums each block's work from genesis. This is chain selection only: upgraded and older nodes accept the same blocks.
  • A checkpoint on mainnet at height 68000. A block that contradicts it, or forks off below it, is refused. A node that loads a best chain contradicting it walks back to the last block that does not.

What changes in the wallet

  • -restorephrase=WORDS is refused, so the words no longer end up in the shell history or the process list. Give them on stdin (-restorephrase, typed with echo off) or from a file (-restorephrase=@FILE).
  • getbalance at the default minconf=1 no longer counts other people's unconfirmed payments. The wallet's own change still counts at once. minconf=0 counts everything unspent.
  • Send in the GUI takes two steps. The first press shows amount, fee and total and sends nothing. Confirm sends, and refuses if the fee came out more than a tenth above what was shown.
  • A fee ceiling: /maxtxfee=AMOUNT, default 1 BTF. A send whose fee is above it is refused. The flat fee setting is limited to 0 to 1 BTF; a larger stored value is not used, and the node says so at start.
  • Locking: a new RPC walletlock; /walletunlocktimeout=SECS (with /walletpassphrase) locks the wallet that long after start, except on a node that mines, runs a pool or renews an inheritance by itself; getinfo reports unlocked_until.
  • Encrypted wallets: installing or restoring a phrase is refused while the wallet is locked. A plaintext seed left by an older version is encrypted or removed at the next unlock, and a key pool damaged by an older version is rebuilt then.
  • New wallets take as many key-derivation rounds as cost about 100 ms on the machine, never fewer than the old 25000. Existing wallets keep theirs.
  • Vault and batch: vaultcreate and ctvbatch refuse, before any coin moves, a template whose fee is below what miners ask for its size or whose expansion is larger than nodes relay. The error names the fee needed. Their answers carry a depositWarning: those addresses take one deposit only.
  • Time-locked coins: a payment locked to a unix time is now counted as final once its time has passed. The 0.1.0 check only understood heights, so such coins never showed in the balance or in listunspent.
  • The RPC cookie, the key dump, swaps.log and btfchat.dat are created owner-only on Linux and macOS.

Swaps

Swaps open on mainnet on 2026-12-25 12:00 UTC, as announced. Both sides need 1.2.33: offers and takes now carry "v":2, and older ones are refused before anything is locked.

  • BTF is locked by time, like the other chains, counted on median time past: 48 hours for the initiator, 18 hours for a BTF participant. A taker giving BTF waits while the Bitflash median time is more than an hour behind the clock. Rules v3 already enforce this, so it is not a consensus change.
  • Every lock is written to swaps.log before it is paid, with its secret, contract and lock time. If that write fails, nothing is sent. Asked again under the same swap, the wallet returns the same lock instead of paying twice. New RPC swaplookup.
  • A counterparty's lock is checked from its contract before any audit. Refunds are confirmed and their fee raised if needed. A maker whose redeem lost the race goes on to refund its own contract. A taker's refund counts as final only when it is deep enough and the maker's contract is spent or past its lock.
  • Swap offers are taken one at a time per peer, and finished swaps are pruned.

Limits on what one peer can make a node do

Wire compatible with 1.2.x: no new message, and every limit allows what current nodes send.

  • P2P (#59): sync serves at most 500 blocks per request and ends each batch with a hint of the tip; requests and announcements have ceilings; a peer's buffers have limits; at most 117 inbound peers, and when full a new peer replaces the least useful one; a misbehaving peer is dropped at once; debug.log rotates at 50 MB.
  • Blocks and the memory pool (#61): a block that fails is marked and kept instead of freed, which closed a use-after-free; orphan blocks are bounded by size; the memory pool refuses transactions that are not final; a branch from genesis can no longer stop a node that lacks the newest checkpoint.
  • Signature hashing (#54) no longer copies the transaction for each check. A spend running 4000 multisig checks went from about 2 s to 32 ms on one machine, which lowers what a block can cost to validate. The hash is the same, byte for byte.
  • P2Pool (#66): shares and history requests from peers that have not yet sent an accepted share draw on shared budgets and wait their turn; the share chain is capped at 128 MB, and lines close to the tip are never evicted.
  • Chat (#70): a node asks more work for a chat record once its store is half full, and the chat app of this release mines to what it asks. Chat apps of 1.2.32 and older cannot store a record on a store at or above half full, which only happens while someone is filling it. The chat listener has connection limits and timeouts.
  • Nostr discovery checks event signatures and dates and has ceilings.
  • RPC (#72): a connection that sends nothing, or stops reading, is closed after 30 s; Content-Length must be a plain number; JSON nested deeper than 64 levels is refused.

Relay and parsing

  • Spends that run a rules-v4 upgrade hook (a CSFS key or CTV argument that is not 32 bytes, CSV with bit 31 set) are not relayed or mined by default.
  • A transaction whose script runs OP_CHECKMULTISIG on a computed key count is not relayed or mined. Wallets in this repository never build one. A refused transaction is no longer kept as an orphan.
  • Raw transaction hex whose lengths are not written in the shortest form is refused by decoderawtransaction, sendrawtransaction and signing. Every Bitflash release writes the shortest form; an external tool that does not needs fixing. Block and transaction validity do not change.
  • A .btf name is accepted only in the spelling the encoder writes (no stray padding bits), onion ports are normalised (:080 becomes :80), and address strings with an embedded NUL are refused.
  • The light client drops a saved block or pending transaction that no longer reads, instead of refusing to start for that coin.
  • In bridges.txt, a line Bridge #... is ignored.

Rules v5, not scheduled

A soft fork closing four gaps left from 0.1.0 (retarget time, spending a coinbase in its own block, lock times past 2038, CSFS sigops before v4) and capping multisig at 20 keys is in the code with no date on either network. Nothing changes until a release sets one. See docs/rules-v5.md.

Packages

  • Tor Expert Bundle 16.0 (tor 0.4.9.15) in the release packages, instead of tor 0.4.9.11.

Downloads

  • Bitflash-1.2.33-windows-with-tor.zip: the wallet (Bitflash.exe) and btfchat (BtfChat.exe), with Tor.
  • Bitflash-1.2.33-x86_64.AppImage and BtfChat-1.2.33-x86_64.AppImage: the wallet and btfchat for Linux, with Tor.
  • bitflash-node-1.2.33-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.33-macos-arm64.tar.gz: macOS 15 or newer on Apple silicon, from Terminal: the node, btfchat and Tor.
  • Bitflash-Miner-1.2.33-{windows.zip,linux.tar.gz,macos-arm64.tar.gz}: XMRig and Tor, ...
Read more

Bitflash 1.2.32

Choose a tag to compare

@github-actions github-actions released this 09 Nov 13:38

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.

Bitflash 1.2.31

Choose a tag to compare

@github-actions github-actions released this 26 Oct 01:54

Every miner and pool: upgrade before 2026-11-21 12:00 UTC. From that moment, when rules v3 switch on, one transaction could stop 1.2.29 and 1.2.30 from building a valid block. 1.2.31 closes that.

Fixed

  • Blocks stay under the signature-operation cap. Neither the solo miner nor the pool counted signature operations when building a block, and the memory pool had no cap per transaction. Under rules v3 a node also counts the operations inside pay-to-script-hash redeem scripts, so one standard transaction of about 1.5 kB could sit in every pool and make every block these builders made invalid. The pool now refuses any transaction over 4,000 (a fifth of a block, as in Bitcoin), and both builders count the way block validation does.
  • Coinbase maturity during a reorganization. The check that a mined coin is 100 blocks deep was made against the old tip while a node switched branches. A node that reorganized could accept a block every other node refused. This was inherited from Bitcoin 0.1.0 and is now checked on the chain being connected.
  • Both block builders fix the block's time before choosing its transactions, so those transactions are checked under the rules of that block.

Rules v4 on testnet, 2026-12-25 12:00 UTC

New script rules switch on on testnet on Christmas Day. Mainnet has no date: nothing changes there until one is announced.

  • Relative lock time (BIP68) and OP_CHECKSEQUENCEVERIFY (BIP112): "not until N blocks after this coin was mined". This is for vaults, payment channels and swaps without a fixed deadline.
  • OP_CHECKTEMPLATEVERIFY (BIP119): "only by a transaction shaped exactly like this". This is for batched payments and covenants. The hash leaves out the scriptSigs field so that it works inside pay-to-script-hash; see docs/rules-v4.md.
  • OP_CHECKSIGFROMSTACK (BIP348): "this key signed this message". It uses BIP340 Schnorr, for oracle-signed contracts.

All three were proven with coins on an isolated testnet bench before release. Every valid path was spent and every invalid one tried; the results are in docs/rules-v4.md.

New RPCs to build and spend these by hand: templatehash and spendscript (docs/rpc.md). For testnet benches only: -isolate, -connectbtf=ADDRESS@HOST.onion:PORT and -benchrulesv4. All three are refused on mainnet.

Reproducible builds

Packages now come out the same from the same commit. Two separate builds of every package matched byte for byte. To check a release against a build of your own instead of trusting this one, follow docs/release-verification.md.

Downloads

  • Bitflash-1.2.31-windows-with-tor.zip: the wallet (Bitflash.exe) and btfchat (BtfChat.exe), with Tor.
  • Bitflash-1.2.31-x86_64.AppImage and BtfChat-1.2.31-x86_64.AppImage: the wallet and btfchat for Linux, with Tor.
  • bitflash-node-1.2.31-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.31-macos-arm64.tar.gz: macOS on Apple silicon, from Terminal: the node, btfchat and Tor.
  • Bitflash-Miner-1.2.31-{windows.zip,linux.tar.gz,macos-arm64.tar.gz}: XMRig and Tor, wired to the pool's onion.

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.

Bitflash 1.2.30

Choose a tag to compare

@github-actions github-actions released this 22 Oct 22:54

Atomic swaps open on mainnet on 2026-12-25 12:00 UTC. That is the only change from 1.2.29.

What moves and what does not

  • Swaps open on Christmas Day. On mainnet, swapinitiate, swapparticipate, btcinitiate and btcparticipate refuse until 2026-12-25 12:00 UTC, and btfchat neither posts nor takes a swap offer before then.
  • Rules v3 keep their date: 2026-11-21 12:00 UTC. 1.2.29 already carries that date, and the rules must switch on everywhere at the same moment. Miners and pools: be on 1.2.29 or 1.2.30 before 2026-11-21.
  • Testnet does not change. Swaps there are open since 2026-10-20, as before.

Everything else is as in 1.2.29, including the OP_2DROP fix every node should have.

Downloads

  • Bitflash-1.2.30-windows-with-tor.zip: the wallet (Bitflash.exe) and btfchat (BtfChat.exe), with Tor.
  • Bitflash-1.2.30-x86_64.AppImage and BtfChat-1.2.30-x86_64.AppImage: the wallet and btfchat for Linux, with Tor.
  • bitflash-node-1.2.30-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.30-macos-arm64.tar.gz: macOS on Apple silicon, from Terminal: the node, btfchat and Tor.
  • Bitflash-Miner-1.2.30-{windows.zip,linux.tar.gz,macos-arm64.tar.gz}: XMRig and Tor, wired to the pool's onion.

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.

Bitflash 1.2.29

Choose a tag to compare

@github-actions github-actions released this 22 Oct 21:02

Trade BTF for BTC with nobody in the middle. Atomic swaps are built into the wallet and into the chat: either both sides get paid, or both get their coins back. No exchange, no escrow, no server. They switch on with rules v3, a soft fork scheduled for mainnet on 2026-11-21 12:00 UTC (testnet switched on 2026-10-20). Miners and pools: upgrade before that date.

Every node should upgrade, not only miners. Since 0.1.0, OP_2DROP removed two items from the script stack without checking that there were two. A script that reached it with fewer crashed every node that evaluated it. It is now checked, as Bitcoin has done since 0.3. Fuzzing found it. No block in the chain changes validity: a block like that would have crashed every node that validated it.

Atomic swaps, BTF for BTC

  • The contract is Decred's atomicswap contract, byte for byte, so a btcatomicswap user can trade with a Bitflash user. The secret is shown by whoever takes the coins first; the other side reads it off the chain. Whoever stops answering, the other gets their coins back after their lock (48 hours for the side that locks first, 24 for the other).
  • Bitcoin built in, with no Bitcoin Core and no server. Without Core, the wallet runs its own Bitcoin light client, the way it runs Tor: block headers checked from genesis (proof of work, difficulty, median time), compact block filters (BIP157/158) compared between two Bitcoin nodes, and only the blocks that touch your contract, checked against their merkle root. Every connection goes through the wallet's Tor. You pay your side from any Bitcoin wallet, to the address and exact amount the wallet shows, and receive to your own Bitcoin address. The first sync takes a while.
  • Or with your Bitcoin Core (30 and later) when it is configured: the Bitflash wallet signs, Core only pays and receives. -btcdatadir, -btcrpcport, -btcwallet.
  • Swaps inside btfchat. Post an offer in a public community ("100 BTF for 0.001 BTC"); whoever takes it and whoever made it carry the swap through in their conversation. Two presses to lock your side. Everything else happens on its own: checking the other side's contract on your own node, taking theirs, reading the secret, refunding if it does not finish.
  • RPC: swapinitiate, swapparticipate, swapauditcontract, swapredeem, swaprefund, swapfindsecret and their btc* counterparts. docs/atomic-swaps.md.

Rules v3 (soft fork, 2026-11-21 12:00 UTC on mainnet)

  • Pay-to-script-hash (BIP16) enforced, with the signature operations inside redeem scripts counted.
  • OP_CHECKLOCKTIMEVERIFY (BIP65).
  • Lock-time finality against median time past (BIP113).
  • OP_VER, OP_VERIF and OP_VERNOTIF are invalid, even in a branch not taken, as in Bitcoin. They made a script's result depend on the version of the node running it.

The rules only tighten what a block may contain: a 1.2.28 node keeps following the chain. What has to upgrade before the date is the hashrate.

macOS, from Terminal

Bitflash runs on Macs with Apple silicon (M1 and later), from Terminal, with no app to install: the node (wallet, solo mining, and the chat's wallet), btfchat as a terminal chat, Tor, and the libraries they use, all in one folder. The Bitflash Miner has a macOS package too (official XMRig and Tor). The download is not signed by Apple; README-macOS.txt has the one command that lets macOS run it. On Windows and Linux, btfchat keeps its window and takes -terminal for the same terminal chat.

btfchat without servers

  • Offline messages wait in the Bitflash nodes themselves (1.2.29 and later), sealed so only the recipient can read them. Finding someone needs no relay: the chat reaches the nodes the way a node does. No Nostr, no VPS, nothing anybody has to keep up.
  • Money in the conversation. "Ask to be paid" and "pay", from your own wallet; a payment can only go to an address the other person signed.
  • Public communities, with the chain as the directory. Creating one burns 0.01 BTF into a listing nobody can take down.
  • On a network that blocks Tor, the chat moves to bridges (snowflake, then obfs4, and on), as the wallet does. It used to take its own onion address for proof that Tor worked, and stayed stuck at a few percent.
  • Delivered means delivered. The receiving chat answers every message with a receipt, and a message counts as delivered only on it; with no receipt it goes to the other person's mailbox. Before this, a message sent to a chat that had just closed could be shown as sent and be lost.

Wallet

  • Fees that work like a market. A rate per 1000 bytes, with a suggestion from what is waiting. Miners now fill blocks best fee per byte first; in 0.1.0 they went in hash order, so paying more bought nothing.
  • Speed up a stuck payment. Transactions are replaceable (BIP125), and a payment still waiting gets a "speed up" button (bumpfee). The free "newer version" replacement inherited from 0.1.0 is gone.
  • Encrypting an old (Berkeley DB) wallet leaves no plaintext behind. Berkeley DB could carry pieces of the unencrypted HD master key into unused space of the rewritten file; they are now found and zeroed before the file is used. The SQLite wallet, the default for new wallets, was not affected.
  • A bad -poolfeeto or -treasuryshare stops the start instead of being ignored.
  • A node whose Tor finished connecting stays off bridges. If no peer answered in its first minutes, it used to decide Tor was blocked, move onto bridges and stay there. Over a bridge its onion address is all but unreachable to others. Servers can pin direct Tor with -notorfallback.
  • Payment links and QR codes. bitflash:ADDRESS?amount=1.5 (BIP21). "Request" shows the link and its QR code; pasting a link into Send fills in the address and amount.

A payment gateway that is only your own node

createinvoice gives a shop a fresh address of its own wallet, the payment link and its QR code (SVG) for the checkout. The node watches for the payment and tells the shop's system, through a signed webhook (HMAC-SHA256) and/or a local command, as the invoice goes waiting, seen, paid (or partial, expired). No gateway company, no account, nothing of ours in between. docs/invoices.md.

For exchanges and integrators

  • Unconfirmed payments can now be replaced by their sender (BIP125): credit deposits on confirmations, and match them by address and amount, not by the first txid seen. gettransaction reports bip125-replaceable.
  • New RPCs: estimatefee, settxfee, bumpfee, createinvoice, getinvoice, listinvoices, cancelinvoice.

Known limits

  • The built-in Bitcoin light client trusts that at least one of the Bitcoin nodes it reaches is honest about the filters; no light client can do better. It sees no memory pool, so a Bitcoin redeem counts only once it is in a block, and one still waiting after an hour is sent again at twice the fee. It has no fee estimate: set -btcfeerate when Bitcoin's fees are high (10 sat/vB by default). For large amounts, Bitcoin Core is the stronger choice, and it is used whenever it is configured.
  • A swap needs the app open at some point during its locks; a refund happens when the app is next open after a lock runs out.
  • A replacement (speed up) takes effect where miners run 1.2.29.

What was tested

Full test suites on Windows and Linux. On testnet with coins: swaps BTF for BTF after rules v3 switched on (swap, refund, every refusal); BTF for BTC against Bitcoin Core 29.4 with Decred's tool and 31.1 with the wallet's own Bitcoin half, both directions; the chat's swap engine end to end with Bitcoin Core and with the built-in light client alone, both directions and both refunds when the maker vanishes; a payment sped up twice, the replacement being the one mined; invoices paid, partial and expired with signed webhooks; two chats behind a network that blocks Tor (invite, messages, payment), and two terminal chats on a server (mailbox, communities, a swap offer taken); the script interpreter under the fuzzer.

Downloads

  • Bitflash-1.2.29-windows-with-tor.zip: the wallet (Bitflash.exe) and btfchat (BtfChat.exe), with Tor.
  • Bitflash-1.2.29-x86_64.AppImage and BtfChat-1.2.29-x86_64.AppImage: the wallet and btfchat for Linux, with Tor.
  • bitflash-node-1.2.29-x86_64: the headless node for servers, for Debian 13 / Ubuntu 24.04 and later. It uses the system's libraries: sudo apt install libsodium23 libdb5.3++ libsqlite3-0 libssl3t64 (libssl3 on older releases). On other distributions, use the AppImage, which carries its own.
  • Bitflash-1.2.29-macos-arm64.tar.gz: macOS on Apple silicon, from Terminal: the node, btfchat and Tor.
  • Bitflash-Miner-1.2.29-{windows.zip,linux.tar.gz,macos-arm64.tar.gz}: XMRig and Tor, wired to the pool's onion.

Upgrading

Stop the node, replace the binary, start. Nothing in the data directory changes shape. Miners and pools must be on 1.2.29 before 2026-11-21 12:00 UTC.

Verify what you download

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

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

Bitflash 1.2.28

Choose a tag to compare

@NSable-sh NSable-sh released this 23 Sep 14:10

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.