Repository navigation
Bitflash 1.2.29
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
btcatomicswapuser 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,swapfindsecretand theirbtc*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_VERIFandOP_VERNOTIFare 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
-poolfeetoor-treasurysharestops 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.
gettransactionreportsbip125-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
-btcfeeratewhen 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.AppImageandBtfChat-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(libssl3on 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.