Repository navigation
Bitflash 1.2.33
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_ROLLandOP_CHECKMULTISIGthat 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=WORDSis 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).getbalanceat the defaultminconf=1no longer counts other people's unconfirmed payments. The wallet's own change still counts at once.minconf=0counts 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;getinforeportsunlocked_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:
vaultcreateandctvbatchrefuse, 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 adepositWarning: 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.logandbtfchat.datare 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.logbefore 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 RPCswaplookup. - 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.logrotates 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-Lengthmust 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_CHECKMULTISIGon 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,sendrawtransactionand signing. Every Bitflash release writes the shortest form; an external tool that does not needs fixing. Block and transaction validity do not change. - A
.btfname is accepted only in the spelling the encoder writes (no stray padding bits), onion ports are normalised (:080becomes: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 lineBridge #...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.AppImageandBtfChat-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, 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.