Blazecoin Wallet 2.0.10 (Windows)

Blazecoin Wallet 2.0.10 (Windows)

What changed: the Provenance page now traces wallets whose coins were moved to post-quantum addresses. It still bundles Blazecoin Core 2.1.0, the fork daemon; nothing about the node changes.

Moving a wallet to post-quantum (2.0.9's Move everything to post-quantum) folds many small outputs into a few large ones, and a large output can have a very long history behind it: for a mining or payout wallet, every block it ever mined. In 2.0.9 a trace of such a wallet could sit with nothing but a running clock for a long time and, on the biggest wallets, never finish. In 2.0.10:

• The trace reports as it reads. The counter of transactions read moves from the first seconds, whether the wallet has ten thousand small coins or one large one.
• Cancel. A running trace has a Cancel button, and leaving the page stops it.
• The wallet stays responsive while a trace runs: the walk happens in the background, and the page only paints.
• It finishes. The proportional ("haircut") lineage is now kept per vintage — a calendar month, or a special block — instead of per block, so the memory a trace needs no longer grows with the chain's history. A payout-sized wallet with 250,000 blocks behind its coins traces in a few minutes. The pedigree (FIFO) view is unchanged and still exact per block.
• Fewer round trips. A transaction's parents are read from the node in batches rather than one at a time.
• Honest limits. If a lineage is larger than the trace's read budget, the page says so and shows the catalogue as a floor: what could not be read is left unproven, never guessed.

Legacy wallets and legacy B… coins trace exactly as before.

Also in this build: both accounting models on every table. The Year Vintages and Special Vintages tables show the pedigree (FIFO) figure and the proportional figure side by side — what is sendable next to what the website credits — with a dash where a model holds nothing, and the block counts per model. The Pedigree/Proportional switch is gone; the summary line reports both totals.

Also fixed (re-issued build of 2.0.10): sending a vintage that sits in the middle of a blended coin. Such a send returns other lineage to you both before and after the vintage, and the wallet gave both of those change outputs the same address — which the node refuses ("duplicated address"). The leading change now goes to a second fresh address, and a plan that would pay any address twice is refused at planning time with the reason.

Install: run BlazecoinWalletV2-Setup-2.0.10.exe over an existing 2.0.x install. Settings, wallets and the data directory are kept. The installer replaces blazecoind.exe / blazecoin-cli.exe beside the wallet; close the wallet (which stops its node) before running it. Verify the download against SHA256SUMS first:

5c1a2a3193aea3608279b5f362e4049831775c6bb1918c3f2afb885d20832bc8  BlazecoinWalletV2-Setup-2.0.10.exe

Requires Windows 10/11 x64. Unsigned build, so SmartScreen will ask once. The macOS build of 2.0.10 follows separately.