upleb.uk

Public git repos — served from a NIP-34 GRASP relay at git.upleb.uk

summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2026-08-14wallet: add read-only record scan boundaryNsable-sh
2026-08-14Merge pull request 'wallet: fail closed on unsafe wallet storage state' ↵Bitflash
(#39) from wallet-storage-sanity-checks into main
2026-08-14Merge pull request 'wallet: audit Berkeley DB wallet storage' (#38) from ↵Bitflash
wallet-storage-audit-bdb into main
2026-08-14wallet: drop bdb log check from storage sanityNsable-sh
2026-08-14wallet: initialize storage audit counts explicitlyNsable-sh
2026-08-13wallet: add storage sanity checkNsable-sh
2026-08-13wallet: export storage audit jsonNsable-sh
2026-08-13wallet: add storage audit commandNsable-sh
2026-08-13tests: assert encryptwallet purges BDB logsNsable-sh
2026-08-13docs: inventory Berkeley DB storageNsable-sh
2026-08-13tests: cover portable wallet copiesNsable-sh
2026-08-13wallet: report locked encrypted recovery seedNsable-sh
2026-08-13release: v1.2.19 (nHDNext restore fix, Tor onion transport: managed Tor, ↵bitflash
direct onion peers, onion-only mode)
2026-08-13Merge pull request 'net: auto-start bundled managed Tor' (#37) from ↵Bitflash
auto-managed-tor into main
2026-08-13Merge pull request 'net: show Tor transport in diagnostics' (#36) from ↵Bitflash
tor-diagnostics into main
2026-08-13net: auto-start bundled managed TorNsable-sh
2026-08-13net: count direct onion peers by endpointNsable-sh
2026-08-13net: show Tor transport in diagnosticsNsable-sh
2026-08-13Merge pull request 'net: add onion-only btf dial mode' (#35) from ↵Bitflash
managed-tor-two-node-smoke into main
2026-08-13net: add onion-only btf dial modeNsable-sh
2026-08-13Merge pull request 'release: package Windows builds with managed Tor' (#34) ↵Bitflash
from windows-managed-tor-package into main
2026-08-13release: verify bundled Tor signaturesNsable-sh
2026-08-13release: package Windows builds with managed TorNsable-sh
2026-08-13Merge pull request 'net: add managed Tor hidden service bootstrap' (#33) ↵Bitflash
from embedded-tor-manager into main
2026-08-13net: stop managed Tor through control portNsable-sh
2026-08-13net: fix managed Tor Windows startupNsable-sh
2026-08-13net: harden managed Tor lifecycleNsable-sh
2026-08-13net: add managed Tor hidden service bootstrapNsable-sh
2026-08-13Merge pull request 'net: add signed direct onion peer endpoints' (#32) from ↵Bitflash
onion-direct-peers into main
2026-08-13net: add signed direct onion peer endpointsNsable-sh
2026-08-12Merge pull request 'site: align public docs and static explorer output' ↵Bitflash
(#30) from site-docs-polish-v1218 into main
2026-08-12Merge pull request 'wallet: collapse restored legacy hdnext' (#31) from ↵Bitflash
restore-collapse-hdnext into main
2026-08-12wallet: collapse restored legacy hdnextNsable-sh
2026-08-12site: document public deployment contractNsable-sh
2026-08-12release: v1.2.18 (Tor/SOCKS5 outbound privacy, poll() socket handler, new ↵bitflash
app icon)
2026-08-12build: fix leftover merge markers in makefile.mingw (drop FD_SETSIZE, keep ↵bitflash
BITFLASH_NODE_BUILD)
2026-08-12Merge pull request 'net: replace peer select loop with poll' (#29) from ↵Bitflash
poll-socket-handler into main
2026-08-12test mergebitflash
# Conflicts: # src/makefile.mingw
2026-08-12Merge pull request 'net: add Tor mode for outbound discovery' (#28) from ↵Bitflash
tor-mode into main
2026-08-12Merge pull request 'net: add optional SOCKS5 outbound proxy' (#27) from ↵Bitflash
socks5-proxy into main
2026-08-12Merge pull request 'tests: add deterministic chain tool fixtures' (#26) from ↵Bitflash
tool-fixtures into main
2026-08-12docs: update social banner to the new coin logobitflash
2026-08-12release: bump version to 1.2.17 (hardened audit tooling)bitflash
2026-08-12Merge pull request 'tools: harden chain audit scripts' (#25) from ↵Bitflash
tooling-hardening into main
2026-08-11net: replace peer select loop with pollNsable-sh
2026-08-11net: warn when Tor mode overrides SOCKSNsable-sh
2026-08-11net: add Tor mode for outbound discoveryNsable-sh
2026-08-11net: harden SOCKS5 proxy parsing and testsNsable-sh
2026-08-11net: add optional SOCKS5 outbound proxyNsable-sh
2026-08-11tests: add deterministic chain tool fixturesNsable-sh
2026-08-11tools: address audit follow-upsNsable-sh
2026-08-11tools: harden chain audit scriptsNsable-sh
2026-08-11Merge pull request 'money: ParseMoney accepts full 8 decimals' (#23) from ↵Bitflash
parsemoney-full-decimals into main
2026-08-11money: ParseMoney accepts full 8 decimals (0.5, 0.00000001)Bitflash
The legacy parser only accepted two decimal places (cents) and rejected 0.5, leaving six of the eight coin decimals unreachable by -sendto and the send window. Parse up to 8 fractional digits Bitcoin-style, reject >8 to avoid silent truncation. Adds the parse-money selftest (12 cases).
2026-08-11Merge pull request 'wallet: SLIP-0044 4346950 is official, drop provisional ↵Bitflash
naming' (#22) from slip44-official-naming into main
2026-08-11wallet: SLIP-0044 4346950 is official, drop 'provisional' namingBitflash
The coin type 4346950 (0x425446 = BTF) was merged into the SLIP-0044 registry on 2026-08-07. Rename HD_BIP44_COIN_TYPE_BITFLASH_PROVISIONAL to HD_BIP44_COIN_TYPE_BITFLASH and update comments, logs and UI strings. Value is unchanged, so derivation paths and addresses are identical.
2026-08-11Merge pull request 'tools: add UTXO inclusion proofs' (#21) from ↵Bitflash
utxo-inclusion-proofs into main
2026-08-11tools: add UTXO inclusion proofsNsable-sh
2026-08-11Merge pull request 'tools: add deterministic UTXO commitment verifier' (#19) ↵Bitflash
from utxo-set-commitment into main
2026-08-11Merge pull request 'tools: add Bitflash mining calculator' (#20) from ↵Bitflash
mining-calculator into main
2026-08-11Merge main into utxo-set-commitment (union README)bitflash
2026-08-11Merge main into mining-calculator (union README)bitflash
2026-08-11Merge pull request 'tools: add fair launch verifier' (#18) from ↵Bitflash
fair-launch-verifier into main
2026-08-10tools: add Bitflash mining calculatorNsable-sh
2026-08-10tools: add deterministic UTXO commitment verifierNsable-sh
2026-08-10tools: add fair launch verifierNsable-sh
2026-08-10tools: static block explorer generator (v0)Bitflash
2026-08-10docs: specify the .btf rendezvous protocolBitflash
2026-08-10release: bump version to 1.2.16Bitflash
2026-08-07shutdown: flush wallet.dat on Windows headless stopBitflash
The headless loop installed SIGINT/SIGTERM handlers only under #ifndef _WIN32, so a headless node on Windows never reached the clean StopNode()+DBFlush() path: Ctrl-C, closing the console window, a service stop and OS shutdown all killed it mid-write, and a Berkeley DB wallet.dat left unflushed will not reopen. Install a SetConsoleCtrlHandler that mirrors the POSIX path: set fShutdown and, because the OS terminates us shortly after the handler returns on CLOSE/LOGOFF/SHUTDOWN, block until the main loop signals the flush is done. A 'taskkill /F' is still an uncatchable hard kill by design. Closes #16.
2026-08-07pool: publish round proof ledgerNsable-sh
2026-08-07bignum: shift setint64 in unsigned space to avoid signed overflow UBBitflash
setint64() extracted big-endian bytes with a signed left shift (n <<= 8). When the top byte is set that overflows int64 -- undefined behaviour, which the script fuzzer flagged under UBSan (bignum.h:158). The result was correct on two's-complement hardware, so this is a latent UB inherited from the original 0.1 code, not a behaviour change. Do the shift on a uint64.
2026-08-07tools: reject non-http(s) dashboard URLs in the pool directoryBitflash
A pool's dashboard URL comes from its self-published status file. Escaping it for HTML is not enough: a javascript: or data: scheme would still render as a clickable script-injection on the public directory page. Only emit a link for http(s) schemes; anything else shows as no link.
2026-08-07tools: build a static pool directoryNsable-sh
2026-08-07pool: add local Stratum bridgeNsable-sh
2026-08-07pool: write dashboard status JSONNsable-sh
2026-08-07test: cover pool Stratum share accountingNsable-sh
2026-08-07pool: make payout ledger crash-safeNsable-sh
2026-08-07randomx: serialize cache initialization (#4)Nsable-sh
2026-08-07fuzz: add script parser harness (#5)Nsable-sh
2026-08-07net: disable legacy order messages (#3)Nsable-sh
2026-08-07wallet: cleanse unlocked secrets before clearing them (#2)Nsable-sh
2026-08-07nostr: verify relay TLS and lock peer counts (#1)Nsable-sh
2026-08-06release: sign SHA256SUMS with a pinned key, verify against itBitflash
verify-release.sh embeds the Bitflash release signing key and now requires that the checksum signature validate against that exact key, not merely against some key in the caller's keyring (#138). It also fetches releases from releases.bitflash.network instead of the retired GitHub host, resolving 'latest' from latest.txt. Release signing key fingerprint: 910A 2B4C CA87 9E81 FB4B 2AEA 1D4A 53D3 B78A A4B8
2026-08-04fuzz: add P2P message parser harness (#142)mtg0001
* fuzz: add P2P message parser harness * fuzz: avoid duplicate legacy header includes * fuzz: seed the corpus with our network magic, not Bitcoin's The two seed inputs began f5 be b6 d9, which is Bitcoin's message start. Ours is bf 20 5c fd. CMessageHeader::IsValid rejects on that field first, so both seeds died at the first check and the smoke run exercised the reject path and nothing else. libFuzzer would have to mutate its way onto four exact bytes before reaching any parser, which does not happen in 128 runs. The job would have gone green while covering none of what it was added to cover. --------- Co-authored-by: Gilcimar Duarte <ti@gpm.infra> Co-authored-by: Bitflash-sh <btf01@proton.me>
2026-08-04ci: add GitHub Actions build and selftests (#140)mtg0001
Co-authored-by: Gilcimar Duarte <ti@gpm.infra>
2026-08-04build: pin external source dependencies (#139)mtg0001
Co-authored-by: Gilcimar Duarte <ti@gpm.infra>
2026-08-04rpc: build the pool block template the way the solo miner does (#141)Bitflash
Two bugs in RebuildJob(), the operator's Stratum template builder. It is a separate path from BitcoinMiner() and had drifted from it. A single pass over mapTransactions is not enough. That map is keyed by hash and carries no dependency order, so a transaction spending another still-unconfirmed transaction's output -- change from a recent send, usually -- fails ConnectInputs whenever its parent sits later in map order. One pass drops it, and map order does not change between rebuilds, so every later rebuild drops it at the same point. That is deterministic exclusion rather than bad luck: where pool operators mine most blocks, a transaction of that shape can stay unconfirmed for as long as its parent is. Now it retries until a pass adds nothing, which is what the solo builder has always done. And the fees reached nobody. nFees was declared inside the scan loop, so each transaction reset it and the running total was discarded, while the coinbase line passed a hardcoded 0. An operator collected fees into a block and paid none of them out. The block stayed valid, since paying less than allowed always is, so nothing ever complained. Both the diagnosis and the fix are Vic-Nas's, from his fork of this code. He deleted the fork, so this brings the work back rather than letting it go with it. His description of the failure was precise enough that finding the same two defects here took one read of our RebuildJob.
2026-08-04docs: one documentation directory, not two (#137)Bitflash
docs/ has held the README's images since the fair-launch release. I added doc/ yesterday for the derivation spec without looking, and #108 then correctly used docs/ -- leaving the repository with both, one letter apart, which is the kind of thing that quietly costs someone ten minutes a year forever. The mistake was mine, so the move is mine: derivation.md and verify-derivation.py go to docs/, and the two README links follow. No content changes. The verifier still reproduces the wallet from its new path, which is the only thing here that can actually break.
2026-08-04Add release verification tooling (#108)mtg0001
Co-authored-by: Gilcimar Duarte <ti@gpm.infra>
2026-08-04gui: say why the wallet would not open, where the user can see it (#136)Bitflash
Every fatal startup path wrote to stderr and to printf, and on Windows neither reaches anybody. printf is remapped to OutputDebugStringF, so it lands in debug.log inside the data directory. A -mwindows binary started by double-clicking has no stderr at all, and AttachTerminal() cannot help: it attaches to a parent console, which a double-clicked exe does not have. So Bitflash exited silently. Someone whose wallet.dat needs a newer build -- exactly what the wallet format guard was added to tell them -- double-clicked and watched nothing happen. The guard was correct and mute, which is the failure it was written to prevent. Fatal startup errors now go through one reporter: debug.log as before, stderr as before, and a message box when there is a person in front of the screen. Applied to the three that mean "your data will not open": the block index failing to load, the block index throwing, and wallet.dat failing or throwing. The box is deliberately not shown for a headless node. Those run under scheduled tasks and services, where a modal dialog waits forever for a click nobody is there to make -- a hung process instead of an exit code. Headless keeps stderr and the log. LoadWallet() now also reports why it refused, in a sentence, instead of only logging it. The unsupported-format case is the one that has to be understood by whoever reads it, and "LoadWallet failed" is not that. Verified by breaking a throwaway wallet on purpose and starting both ways. Headless: exit code 1, no dialog, no process left behind. Windowed with no console: a box naming the file, the Berkeley DB error, the usual cause, and where to look for more.
2026-08-04wallet encryption: the stack from #130–#133, with the two blockers fixed ↵Bitflash
(#134) * wallet: refuse future encrypted wallet formats * wallet: add encrypted key unlock core * wallet: add encryptwallet rewrite command * wallet: read passphrases from stdin or files * wallet: keep the derivation across encryption, and take the logs with it Two things stopped the encryption stack from being safe to merge. Both were found against a wallet holding real coin, not in the self-tests. 1. Encrypting turned a BIP44 wallet into a legacy one. LoadWallet() ends by resetting the schema and the derivation counters when no seed is in memory. That was written when "no seed after loading" could only mean the wallet had none. An encrypted wallet has a seed -- it just has not been decrypted yet -- so the reset threw away metadata that had been read correctly a moment earlier. Unlocking later restores the seed and nothing restores the rest. Measured on the wallet from the #124 proof: after encrypting, index 1 moved off BAtgSgra2X8Dqo5PJzPCLJhPwrrC2thYVJ, the address actually holding 1.00 BTF, and the audit went from "1.00 covered by the phrase" to "0.00 covered, 1.00 wallet.dat-only". Encrypt your wallet and the program told you your recovery phrase no longer covered your money. Now the condition also accepts a wallet whose seed is present but encrypted. Same wallet, before and after: schema bip44, same four derived addresses, 1.00 BTF still reported as covered. 2. The plaintext keys stayed behind in the Berkeley DB logs. wallet.dat comes out clean -- verified by scanning the raw file for the 118 bytes of a known private key. database/log.0000000002 did not: it held the whole key, and still did after a full node restart, because every record this wallet ever wrote passed through the log. That defeats the feature for the case it exists for, since our own backup advice is to copy the whole directory rather than wallet.dat alone. log_archive() cannot fix it: it only drops logs Berkeley DB considers obsolete and never the one it is writing to, and with one 10 MB log per directory that is precisely where the keys are. They also did not get there at encryption time -- they accumulated over the wallet's whole life -- so nothing done during the rewrite can archive them out. So the encrypt command now closes the environment and deletes the logs on its way out, after the flush that makes every .dat self-contained. This is not secure erasure; the blocks are unlinked, not overwritten. It closes the case of someone reading a copied data directory. Getting there uncovered a third bug, older than both. DBFlush(true) is not safe to call twice. The first call closes the environment, and txn_checkpoint() on a closed environment segfaults instead of returning an error, so the try/catch around it never sees anything. EncryptWallet() already flushes before renaming the wallet, and the command flushes again on the way out -- that pair crashed every single time. Guarded now. The same function has been calling log_archive() with the address of an uninitialised pointer since 0.1.0, on every clean shutdown, in a path whose catch(...) cannot catch a structured fault on Windows. DB_ARCH_REMOVE requires that argument to be NULL. Fixed while here, because the encryption cleanup depends on that call not being a coin flip. --------- Co-authored-by: Gilcimar Duarte <ti@gpm.infra>
2026-08-03doc: write down the derivation, so the words work without us (#128)Bitflash
The twelve words were only as good as this binary staying alive. The derivation path, the address version byte and the public-key encoding existed nowhere outside src/, so anyone holding a phrase and no working Bitflash had the keys and no way to find them. doc/derivation.md states all of it: BIP-39 to seed, BIP-32 to children, both layouts this wallet has used (legacy m/i' and BIP-44 m/44'/4346950'/0'/{0,1}/i), secp256k1 with UNCOMPRESSED public keys, and Base58Check with version byte 25. The uncompressed part is the trap worth naming. Hashing the same key in compressed form yields a different, perfectly valid-looking address that holds nothing, and nothing in the source says out loud which one is used -- it falls out of OpenSSL's default in code inherited from 0.1.0. doc/verify-derivation.py implements the document from scratch, sharing no code with this project and importing nothing outside the standard library, then checks it against addresses the wallet actually produced. Both tables were generated by a binary first: the legacy one by the published v1.2.15, which knows only that layout, and the BIP-44 one by the current tree. The script reproduces all eight. That is the point of shipping the checker rather than only the prose: if the two ever drift, the script fails and says which side is wrong.
2026-08-03gui: name the icon resource GLFW_ICON so the window actually wears it (#126)Bitflash
The right icon has been in the exe the whole time. GLFW never found it. GLFW registers its own window class and fills hIcon with LoadImageW(module, L"GLFW_ICON", ...), falling back to IDI_APPLICATION when that exact resource name is missing. Ours was named "bitflash", so the lookup failed and every window this program has opened wore the generic Windows icon -- in the title bar and in the taskbar -- while the correct artwork sat unused a few kilobytes away. One line, verified by looking at it: rebuilt, ran the window, and zoomed in on both places the user pointed at. The title bar and the taskbar button now show the green BF coin. Checked the shell path too, since it resolves icons differently: ExtractAssociatedIcon on the new exe still returns the coin, so renaming the resource did not cost the file icon in Explorer.
2026-08-03Activate BIP44 wallet derivation (#124)mtg0001
* Add BIP32 path derivation foundation * Add HD wallet schema metadata * Add provisional BIP44 coin type metadata * Activate BIP44 wallet derivation * wallet: scan BIP44 restore depth per branch * wallet: widen default BIP44 restore lookahead --------- Co-authored-by: Gilcimar Duarte <ti@gpm.infra>
2026-08-03Bump to 1.2.15 (#120)Bitflash
2026-08-03wallet: wire -sendto into main(), where it never was (#119)Bitflash
CmdSendTo() has been in walletcmd.cpp since #115 and nothing declared it or called it. The flag was dead: `bitflash -sendto=ADDRESS,AMOUNT` started a node and said nothing, because an unrecognised argument is not an error here. The v1.2.14 notes announce it under "A headless node can finally spend", and the headless Linux binary is exactly the one that does not have it -- `-help` there lists /newaddress and stops. The published Windows binary does have it, because it was built from a working tree that carried these two files uncommitted. So the artifacts disagree with each other and neither matches the tag. This adds only what was missing: the declaration in walletcmd.h, the dispatch in main(), and the -help line. No behaviour change to CmdSendTo itself. Checked on a build of this branch, against a throwaway data directory: -help lists /sendto=ADDRESS,AMOUNT -sendto=NOTANADDRESS,1 "Not a valid address", exit 1 -sendto=<valid>,-5 "Not a valid amount", exit 1 -sendto=<valid>,999 refused on an empty wallet, exit 1 All five self-tests still pass.
2026-08-03Add wallet recovery balance audit (#117)mtg0001
Co-authored-by: Gilcimar Duarte <ti@gpm.infra>
2026-08-03gui: read the Finish condition once, before the button that clears it (#118)Bitflash
Creating a recovery phrase from the window aborted with an ImGui assertion on the success path: Expression: (g.DisabledStackSize > 0) && "Calling EndDisabled() too many times!" File: imgui/imgui.cpp Line: 8435 The Finish button is wrapped in BeginDisabled/EndDisabled guarded by !g_phraseWrittenDown, and its own click handler sets g_phraseWrittenDown to false. So the pair was opened while the checkbox was ticked and closed after the handler had unticked it: BeginDisabled was never called, EndDisabled was, and ImGui asserted on the unmatched close. It fires on the only path that installs a seed -- tick the box, press Finish -- so every phrase created from the window has hit it since the feature shipped in 1.2.12. Three releases carried it because nothing tests the window. Reproduced on the published 1.2.14 binary and confirmed fixed on this build, driving the real window: Wallet Safety -> Create recovery phrase -> tick -> Finish. The old build raises the assertion; the fixed build closes the dialog, reports "This wallet has a recovery phrase", and the address changes to a derived one. The seed itself was already written before the assertion, so the wallet was never left half-installed -- and ImGui's IM_ASSERT_USER_ERROR_RET returns before touching its state, so answering Ignore was safe. Abort was not: it kills the process with no DBFlush. The restore dialog next door already does this correctly, copying the condition into a local first. This makes the create dialog match.
2026-08-02Bump to 1.2.14 (#116)Bitflash
A block had no size limit, spending could move coins onto a key your recovery phrase cannot reproduce, and one peer could hold up the whole node with a message it never finished sending. All three are fixed here, and all three were found by auditing the tree rather than by anyone hitting them. ## Blocks now have a size limit — and this one is consensus `CheckBlock()` measured a block against `MAX_SIZE`, the serializer's generic 32 MB guard. There was no `MAX_BLOCK_SIZE` anywhere in the tree: Bitcoin's 1 MB cap arrived in 0.3.x, after the 0.1.0 this project came from, so the inheritance was simply missing. A miner could produce a 32 MB block and every node would download, verify and store it. The cap is now **1 MB**, chosen against the chain rather than tradition. Reading all 5709 blocks out of `blk0001.dat`: | | | |---|---| | largest block ever mined | 34,290 bytes | | median | 216 bytes | | p99 | 14,451 bytes | 1 MB leaves **29× of headroom** over the largest block this chain has ever carried, so nothing existing is rejected. A node built with the rule then synced genesis → 5706 on the live network with zero rejections, which is the same test that once caught BIP30 rejecting a real block at height 859. **Because it is consensus, it matters that you upgrade.** Until most nodes have it, a block above 1 MB would be accepted by old nodes and rejected by new ones — which is how a chain splits. Nobody is mining such blocks today; the gap is worth closing before somebody does. ## Spending could put your change on a key the phrase cannot recover When a wallet spends, the leftover goes back to you as *change*. This tree sent change to **the same key as one of the coins being spent** — 0.1.0 behaviour, and a privacy problem long tracked as #23. With recovery phrases it became a way to lose money. If the coin being spent sat on a key created *before* the seed — the wallet's original default address, an imported key, anything older than `-newphrase` — then the change went back to that same pre-seed key. So spending quietly moved your balance onto a key the twelve words do not reproduce, in a wallet you believed the words covered. Change now comes from a newly derived, phrase-backed key. **If that derivation fails, the transaction is refused rather than created**, because a failed send is recoverable and unrecoverable change is not. Wallets with no seed keep the old behaviour exactly. Restore also now scans past the pre-generated key-pool window before accepting an empty batch as the end, so a restore cannot stop short while used addresses sit just beyond it. ## One peer could hold up the whole node `ProcessMessages` runs in a single thread that serves every peer. When a message header announced more bytes than had arrived, the old code consumed the header, inserted it back at the *front* of the receive buffer — an O(n) memmove on a buffer that could hold 256 MB — and then slept 100 ms **inside that shared thread**. A peer that announced a large message and dripped bytes could make every pass pay both costs, forever, while looking perfectly active to the inactivity reaper. The parser now reads the header from a copy without consuming it, never sleeps in the shared thread, and disconnects a peer that sits on an incomplete message for two minutes. The wire cap drops from 256 MB to `MAX_SIZE`. ## The rendezvous holds more than one registration A node's registration at a rendezvous relay was consumed by the first caller, and registering again *replaced* the previous one — so a node was reachable to exactly one peer at a time and unreachable for the whole gap between being paired and registering again. Measured on a live node: descriptors resolved 53 times out of 54, its own registrations paired 11 out of 12, and **half of every outbound dial failed**. All three relays now keep a queue per node and pair with the oldest registration still alive. **This is already deployed** — you get it without upgrading. The matching node-side change, which parks spare registrations, is deliberately **not** in this release: it measured worse in the field than the code it replaced and will not ship until that is explained. ## Restoring from a phrase now looks far enough Found by proving the change fix above with real coin, and caused by it. Restoring derived forward in batches of a hundred and stopped at the first batch that turned up nothing. The wallet digs a wider gap than that by itself: a restore leaves the derivation counter at the depth it scanned, the key pool derives a hundred more, and change takes the index after those. So the address used *after* a restore can sit two hundred indices past the last one used before it, with nothing in between. On a real wallet: receive, restore, spend once — the outputs land at indices 201 and 302. Restoring again reported ``` Restored: 1 transaction(s) across 201 derived addresses ``` and the spend was invisible, both the payment and the change. The money was derived and covered by the phrase; the search stopped short of it. Three quiet batches instead of one, and the same wallet reports `2 transaction(s) across 601 derived addresses`. Change returning to an input's key used to hide this, because that key sat at a low index the scan had already passed. Fixing recoverability moved change out to where the search stopped looking, so the two had to be fixed together. The gap is self-inflicted and grows with each restore, so a long enough history can still outrun a fixed number of quiet batches. `-restoredepth=N` looks as far as you ask. The structural fix is tracked separately. ## A headless node can finally spend `SendMoney()` has been in this tree since 0.1.0 and only the window ever called it, so a node without a screen could be paid and could never pay — it could hold a balance with no way to move it. Found while trying to prove the change fix, which needs a spend. ``` bitflash -sendto=ADDRESS,AMOUNT ``` Refuses an address that does not decode, an amount that is zero, negative or not a number, and a wallet whose chain is not loaded — all before touching the wallet. A transaction created while the node is stopped is not broadcast until the node starts. ## Also - `-help` printed nothing at all on Windows. This tree remaps `printf` to the debug-log writer, and a `-mwindows` binary has no console, so the one command whose job is to tell you something returned 0 in silence. - The README described a program from several releases ago — deterministic restore listed as an open issue, mining mode described as forgotten between restarts, and every flag written in the slash form that MSYS2 rewrites into a path. - Diagnostics now report why a socket close failed, per error code and per site, and flag a handle handed back while some part of the program still claims it. ## Downloads | File | Platform | Notes | |------|----------|-------| | `Bitflash-1.2.14-windows.zip` | Windows x86_64 | Extract and run | | `Bitflash-1.2.14-x86_64.AppImage` | Linux x86_64 | Desktop/GUI — `chmod +x` and run | | `bitflash-node-1.2.14-x86_64` | Linux x86_64 | Headless server node, no libGL or FUSE | Verify with `sha256sum -c SHA256SUMS`. Everything in [v1.2.13](https://github.com/Bitflash-sh/bitflash/releases/tag/v1.2.13) is included.