Skip to content

Releases: AMA-CSharp-Code/blazecoin-wallet

Blazecoin Wallet 2.0.12 (Windows)

Choose a tag to compare

@AMA-CSharp-Code AMA-CSharp-Code released this 09 Oct 07:55

Blazecoin Wallet 2.0.12 (Windows)

What changed: nothing in the wallet itself. This is the 2.0.11 wallet re-bundled with Blazecoin Core 2.1.1, so the Windows installer ships the same node as the macOS 2.0.11 app.

Why 2.1.1 matters. It is the first build that carries the post-quantum checkpoint at block 4,250,000 and refreshes the assume-valid anchor to block 4,319,107, so a fresh install verifies the chain from a point three days old instead of from the 2.1.0 anchor. No consensus change: 2.1.0 and 2.1.1 nodes stay on one chain, so upgrading is recommended rather than required.

What 2.0.11 brought, if you are coming from 2.0.10 or older: Preferences → Sign Message proves an address to the website in one paste and one click (post-quantum BQ… addresses included), Console commands go to the window's active wallet, and a start-up crash that affected builds published after 30 September is fixed.

Install: run BlazecoinWalletV2-Setup-2.0.12.exe over an existing 2.0.x install. Settings, wallets and the data directory are kept. The installer replaces blazecoind.exe and blazecoin-cli.exe with the 2.1.1 node; the wallet starts it as before.

13171aa1a84e8fcf34e0e5864d1bbed7172ebd7cd0faf09d4838231009b913ff  BlazecoinWalletV2-Setup-2.0.12.exe

Requires Windows 10/11 x64. Unsigned build, so SmartScreen will ask once. macOS users already have 2.1.1 in v2.0.11-macos; no Mac release this time.

Blazecoin Wallet 2.0.11 (Windows)

Choose a tag to compare

@AMA-CSharp-Code AMA-CSharp-Code released this 08 Oct 22:44

Blazecoin Wallet 2.0.11 (Windows)

What changed: proving that an address is yours is now one paste and one click. It still bundles Blazecoin Core 2.1.0, the post-quantum fork daemon; nothing changes on the node side.

Sign Message, in Preferences. The website's Wallet Address card asks you to sign a short challenge with the key behind your address before it will lock that address to your account (the gate for the collector rewards). Until now that meant typing an RPC command into the Console. Now:

  • Open Preferences and scroll to Sign Message (the sidebar button takes you straight there).
  • Paste the whole signmessage "…" "blazecoin-verify:…" line the card shows, or just the challenge text. The address and message fill in by themselves.
  • Click Sign, then Copy signature, and paste it into the card.

The wallet finds which of your loaded wallets holds the address, so it works from any window. If that wallet is encrypted it asks for the passphrase in place, unlocks for 60 seconds, signs, and locks again. It checks the signature against the node before showing it. Post-quantum BQ… addresses sign too: their signature is about 5,000 characters, shown whole, and the website accepts it.

Also fixed

  • Console. Wallet commands typed into the Console failed with "Wallet file not specified" whenever more than one wallet was loaded. They now go to the window's active wallet.
  • Start-up crash in builds published after 30 September. A command-line tool committed on that date had been swept into the application's build and became its entry point, so any wallet published from that code crashed on launch. No released installer carried it (2.0.10 was published earlier that day), but this build has the fix.

Install: run BlazecoinWalletV2-Setup-2.0.11.exe over an existing 2.0.x install. Settings, wallets and the data directory are kept. The installer replaces blazecoind.exe and blazecoin-cli.exe with the same 2.1.0 node as before.

148f18ca916abce926722d847e5e51a44204518f82b08d3a3eb85e7c7505d2f8  BlazecoinWalletV2-Setup-2.0.11.exe

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

Blazecoin Wallet 2.0.11 (macOS)

Choose a tag to compare

@AMA-CSharp-Code AMA-CSharp-Code released this 09 Oct 06:36

Blazecoin Wallet 2.0.11 (macOS)

What changed: proving that an address is yours is now one paste and one click, and this build carries
Blazecoin Core 2.1.1, the maintenance release of the post-quantum fork node. Same wallet as the Windows 2.0.11,
as a universal app for Apple Silicon and Intel Macs.

Sign Message, in Preferences. The website's Wallet Address card asks you to sign a short challenge with the key
behind your address before it will lock that address to your account (the gate for the collector rewards). Until
now that meant typing an RPC command into the Console. Now:

  • Open Preferences and scroll to Sign Message (the sidebar button takes you straight there).
  • Paste the whole signmessage "…" "blazecoin-verify:…" line the card shows, or just the challenge text. The address
    and message fill in by themselves.
  • Click Sign, then Copy signature, and paste it into the card.

The wallet finds which of your loaded wallets holds the address, so it works from any window. If that wallet is
encrypted it asks for the passphrase in place, unlocks for 60 seconds, signs, and locks again. It checks the
signature against the node before showing it. Post-quantum BQ… addresses sign too: their signature is about
5,000 characters, shown whole, and the website accepts it.

Also fixed

  • Console. Wallet commands typed into the Console failed with "Wallet file not specified" whenever more than one
    wallet was loaded. They now go to the window's active wallet.

Bundled node: Blazecoin Core 2.1.1 (the Windows 2.0.11 installer still ships 2.1.0; the Mac build is the first
wallet with 2.1.1). Consensus is unchanged — a 2.1.0 node and a 2.1.1 node follow the same rules and stay on the
same chain. 2.1.1 adds a checkpoint at the post-quantum activation block 4,250,000 and refreshes the initial-sync
anchors to block 4,319,107, so a Mac syncing from scratch gets there faster and rejects a wrong chain at the fork
before validating it. No rescan or re-index is needed; wallets and chain data carry over unchanged.

Everything from the earlier macOS releases is included: the Provenance trace for post-quantum-consolidated wallets
(2.0.10), post-quantum receive, change and Move to post-quantum (2.0.9), full-speed Intel Macs with the discrete
GPU on dual-GPU MacBook Pros, cached images, and direct V1.5 wallet import (2.0.8).

Download & verify

  • BlazecoinWalletV2-2.0.11-macOS-universal.zip — the wallet application (126 MB)
shasum -a 256 BlazecoinWalletV2-2.0.11-macOS-universal.zip

Expected:

5e08831cc8c73cb5758aa188f8090a73045ca821a449cecf8de54df51523e4c6

Install or update

Quit the wallet first (that stops its node), unzip, and move Blazecoin Wallet V2.app into /Applications,
replacing the old one. Wallets, settings and chain data in ~/Library/Application Support/BlazecoinV2.0/ are kept,
and the new node picks them up as they are.

The build is ad-hoc signed, not notarized, so Gatekeeper blocks the first launch of each new download:

macOS 15 (Sequoia) and later — double-click the app, click Done on the "Apple could not verify…" dialog, open
System Settings → Privacy & Security, click Open Anyway next to the app and confirm. (On macOS 12–14:
right-click the app → Open → Open.)

Any version, one Terminal command:

xattr -dr com.apple.quarantine "/Applications/Blazecoin Wallet V2.app"

Known limitations

  • Requires macOS 12 (Monterey) or newer; PDF export requires macOS 15 or newer.
  • Not notarized: the Gatekeeper step above is needed on every fresh download.
  • Provenance needs the node's transaction index, which builds in the background after the first launch (about
    15 minutes on an M1).
  • The Backup page has no folder picker on macOS — type or paste the destination path.
  • Transaction exports save straight to ~/Downloads.

Blazecoin Wallet 2.0.10 (Windows)

Choose a tag to compare

@AMA-CSharp-Code AMA-CSharp-Code released this 30 Sep 07:20

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.

Blazecoin Wallet 2.0.10 (macOS)

Choose a tag to compare

@AMA-CSharp-Code AMA-CSharp-Code released this 30 Sep 09:37

Blazecoin Wallet 2.0.10 (macOS)

What changed: the Provenance page now traces wallets whose coins were moved to post-quantum addresses. Same
release as the Windows 2.0.10, as a universal app for Apple Silicon and Intel Macs. It still bundles Blazecoin
Core 2.1.0
, the fork node; 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: 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.

Everything from the earlier macOS releases is included: post-quantum receive, change and Move to post-quantum
(2.0.9), full-speed Intel Macs with the discrete GPU on dual-GPU MacBook Pros, cached images, and direct V1.5 wallet
import (2.0.8).

Download & verify

  • BlazecoinWalletV2-2.0.10-macOS-universal.zip — the wallet application (126 MB)
shasum -a 256 BlazecoinWalletV2-2.0.10-macOS-universal.zip

Expected:

d076e865c4a1da4c9c2f170e1fa8fb79ae2cf9f31a551d007b4e138264d46051

Install or update

Quit the wallet first (that stops its node), unzip, and move Blazecoin Wallet V2.app into /Applications,
replacing the old one. Wallets, settings and chain data in ~/Library/Application Support/BlazecoinV2.0/ are kept.

The build is ad-hoc signed, not notarized, so Gatekeeper blocks the first launch of each new download:

macOS 15 (Sequoia) and later — double-click the app, click Done on the "Apple could not verify…" dialog, open
System Settings → Privacy & Security, click Open Anyway next to the app and confirm. (On macOS 12–14:
right-click the app → Open → Open.)

Any version, one Terminal command:

xattr -dr com.apple.quarantine "/Applications/Blazecoin Wallet V2.app"

Known limitations

  • Requires macOS 12 (Monterey) or newer; PDF export requires macOS 15 or newer.
  • Not notarized: the Gatekeeper step above is needed on every fresh download.
  • Provenance needs the node's transaction index, which builds in the background after the first launch (about
    15 minutes on an M1).
  • The Backup page has no folder picker on macOS — type or paste the destination path.
  • Transaction exports save straight to ~/Downloads.

Blazecoin Wallet 2.0.9 (Windows)

Choose a tag to compare

@AMA-CSharp-Code AMA-CSharp-Code released this 28 Sep 20:25

Blazecoin Wallet 2.0.9 (Windows)

What changed: the desktop wallet now puts your coins on post-quantum addresses — BQ… addresses, secured by ML-DSA-44 since the post-quantum fork at block 4,250,000 — and keeps them there. It still bundles Blazecoin Core 2.1.0, the fork daemon; nothing about the node changes.

New in this release:

  • Move to post-quantum. On the Quantum Exposure page every legacy address has a Move to BQ button, and Move everything to post-quantum moves the whole wallet in one go. The destination is a fresh BQ… address from the wallet itself, and the page refuses anything that is not one. A plan is sent once; if a send times out the page says its result is unknown rather than inviting a retry.
  • Create a post-quantum wallet, right there. A wallet created before node 2.1.0 has no post-quantum keys and cannot make a BQ… address. The Quantum page now says so plainly and offers to create a new wallet on the spot: encrypted with your passphrase by default (an unencrypted option exists for wallets that must sign on their own), backed up to a file you choose, and its first BQ… address filled in as the destination. Nothing is sent until you press Broadcast.
  • Receive on post-quantum addresses. The Receive page offers Post-quantum (BQ…) or Legacy (B…), post-quantum by default whenever the wallet can make one, and the list shows each address's type. A BQ… address can be paid by the desktop wallet 2.0.5 or later, the web wallet and the Android lite wallet 1.2.0 or later; V1.5 and older wallets cannot pay a BQ… address, so give those senders a legacy address.
  • Change stays post-quantum. When you send from a wallet with post-quantum keys, the change comes back to a new BQ… address, and the review step shows where the change goes. A send that times out now says its result is unknown and asks you to check Transactions before sending again.
  • Solo mining pays to BQ…. The built-in miner's automatic payout address is post-quantum when the wallet can make one.
  • Clearer Quantum table. Legacy addresses are listed above post-quantum ones, wear their own amber "Legacy · unexposed" badge, and the collapsed row says how many of each it hides.
  • Stricter address check. A Bitcoin "1…" address is no longer mistaken for a legacy Blazecoin address.

Install: run BlazecoinWalletV2-Setup-2.0.9.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:

24922129c5dc0bf95547bbba83804423c5ffc94d0934675e16296691f0b8614f  BlazecoinWalletV2-Setup-2.0.9.exe

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

Blazecoin Wallet 2.0.9 (macOS)

Choose a tag to compare

@AMA-CSharp-Code AMA-CSharp-Code released this 28 Sep 20:54

Blazecoin Wallet 2.0.9 (macOS)

What changed: the desktop wallet now puts your coins on post-quantum addresses — BQ… addresses, secured by
ML-DSA-44 since the post-quantum fork at block 4,250,000 — and keeps them there. Same release as the Windows
2.0.9, as a universal app for Apple Silicon and Intel Macs. It still bundles Blazecoin Core 2.1.0, the fork
node; nothing about the node changes.

New in this release:

  • Move to post-quantum. On the Quantum Exposure page every legacy address has a Move to BQ button, and
    Move everything to post-quantum moves the whole wallet in one go. The destination is a fresh BQ… address from
    the wallet itself, and the page refuses anything that is not one. A plan is sent once; if a send times out the page
    says its result is unknown rather than inviting a retry.
  • Create a post-quantum wallet, right there. A wallet created before node 2.1.0 has no post-quantum keys and
    cannot make a BQ… address. The Quantum page now says so plainly and offers to create a new wallet on the spot:
    encrypted with your passphrase by default (an unencrypted option exists for wallets that must sign on their own),
    backed up to a file you choose (by default in ~/Documents/Blazecoin Wallet Backups/), and its first BQ… address
    filled in as the destination. Nothing is sent until you press Broadcast.
  • Receive on post-quantum addresses. The Receive page offers Post-quantum (BQ…) or Legacy (B…),
    post-quantum by default whenever the wallet can make one, and the list shows each address's type. A BQ… address can
    be paid by the desktop wallet 2.0.5 or later, the web wallet and the Android lite wallet 1.2.0 or later;
    V1.5 and older wallets cannot pay a BQ… address, so give those senders a legacy address.
  • Change stays post-quantum. When you send from a wallet with post-quantum keys, the change comes back to a new
    BQ… address, and the review step shows where the change goes. A send that times out now says its result is unknown
    and asks you to check Transactions before sending again.
  • Solo mining pays to BQ…. The built-in miner's automatic payout address is post-quantum when the wallet can
    make one.
  • Clearer Quantum table. Legacy addresses are listed above post-quantum ones, wear their own amber
    "Legacy · unexposed" badge, and the collapsed row says how many of each it hides.
  • Stricter address check. A Bitcoin "1…" address is no longer mistaken for a legacy Blazecoin address.

Everything from the 2.0.8 macOS re-issues is included: Intel Macs run at full speed and dual-GPU MacBook Pros use
their discrete GPU while the wallet is open, images are cached between pages, Provenance works out of the box, and
V1.5 wallets import directly.

Download & verify

  • BlazecoinWalletV2-2.0.9-macOS-universal.zip — the wallet application (126 MB)
shasum -a 256 BlazecoinWalletV2-2.0.9-macOS-universal.zip

Expected:

907b7ba442a6b5729343c3b547376e7a7d526960fd927539168f64ecec7c4d09

Install or update

Quit the wallet first (that stops its node), unzip, and move Blazecoin Wallet V2.app into /Applications,
replacing the old one. Wallets, settings and chain data in ~/Library/Application Support/BlazecoinV2.0/ are kept.

The build is ad-hoc signed, not notarized, so Gatekeeper blocks the first launch of each new download:

macOS 15 (Sequoia) and later — double-click the app, click Done on the "Apple could not verify…" dialog, open
System Settings → Privacy & Security, click Open Anyway next to the app and confirm. (On macOS 12–14:
right-click the app → Open → Open.)

Any version, one Terminal command:

xattr -dr com.apple.quarantine "/Applications/Blazecoin Wallet V2.app"

Known limitations

  • Requires macOS 12 (Monterey) or newer; PDF export requires macOS 15 or newer.
  • Not notarized: the Gatekeeper step above is needed on every fresh download.
  • The Backup page has no folder picker on macOS — type or paste the destination path.
  • Transaction exports save straight to ~/Downloads.

Blazecoin Wallet 2.0.8 (Windows)

Choose a tag to compare

@AMA-CSharp-Code AMA-CSharp-Code released this 24 Sep 15:22

Blazecoin Wallet 2.0.8 (Windows)

What changed: the Windows build of the 2.0.8 line, the same wallet code as the macOS 2.0.8 release. It still bundles Blazecoin Core 2.1.0, the post-quantum fork daemon (the fork activated at block 4,250,000 on 16 September 2026). If you are on wallet 2.0.4 or earlier, your bundled node stopped following the chain at that height; install this release.

New in this release:

  • Provenance traces the whole ancestry. The wallet now starts its node with a transaction index, which the Provenance page needs to follow a coin back through transactions that are not your own. On the first launch after upgrading, the node builds the index in the background (about 15 minutes on this chain; the wallet is usable meanwhile) and Provenance shows full results once it is complete.
  • Sync progress from the first minute. While the node pre-syncs and downloads headers the status bar says so, with a count, instead of sitting at "0 / 0 blocks".
  • One-click "Create wallet" on the first-run screen (the command-line fallback is still shown).
  • V1.5 wallet import converts the old Berkeley DB file directly, including files written by the macOS V1.5 build, and rescans from where V1.5 left off.
  • Smoother animations. The Quantum Exposure atoms and the Import and Backup backgrounds are drawn as composited sprites instead of redrawing the whole screen every frame; the dashboard coins are sharp on high-DPI displays.

Install: run BlazecoinWalletV2-Setup-2.0.8.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:

5f078c1ab6f97d26fbd3d11010d805d55eb680c4c13ad469b2935f2db62a62ce  BlazecoinWalletV2-Setup-2.0.8.exe

Requires Windows 10/11 x64. Unsigned build, so SmartScreen will ask once.

Blazecoin Wallet 2.0.8 (macOS)

Choose a tag to compare

@AMA-CSharp-Code AMA-CSharp-Code released this 24 Sep 06:45

Blazecoin Wallet 2.0.8 (macOS)

What this is: the first macOS build of the V2 desktop wallet — the same wallet as the Windows release,
as a universal app (Apple Silicon and Intel), bundling Blazecoin Core v2.1.0, the post-quantum
fork node. It runs a full node on your Mac; the wallet talks to it locally, nothing leaves your machine
except normal peer-to-peer traffic.

Re-issued 2026-09-24. The zip on this tag was replaced during the day as the Intel build was brought
up to the Apple Silicon one (details under What changed). If you downloaded earlier, download again
and check the hash below; the Apple Silicon build only gained the smaller fixes.

Download & verify

  • BlazecoinWalletV2-2.0.8-macOS-universal.zip — the wallet application (126 MB)

Verify the download is intact:

shasum -a 256 BlazecoinWalletV2-2.0.8-macOS-universal.zip

Expected:

51c57a6c852311cb6d06245c133278a1bed939465041c45d0691a4d6c4c51f09

Install & first launch

This build is ad-hoc signed (not notarized — there is no Apple Developer account behind it), so macOS
Gatekeeper blocks the first launch. Unzip the download and move Blazecoin Wallet V2.app into /Applications,
then get past Gatekeeper one of two ways:

macOS 15 (Sequoia) and later — double-click the app, click Done on the "Apple could not verify…"
dialog, open System Settings → Privacy & Security, scroll down to Security, click Open Anyway
next to the app and confirm. (On macOS 12–14: right-click the app → Open → Open.)

Any version, one Terminal command — removes the download's quarantine flag:

xattr -dr com.apple.quarantine "/Applications/Blazecoin Wallet V2.app"

What changed in the re-issues (2026-09-24)

Verified on a 2021 M1 Pro (macOS 27) and a 2019 16-inch Intel MacBook Pro (macOS 26.5).

  • Intel Macs launch and run properly. The first upload quit on launch on Intel; the Intel half of the
    app now runs the standard .NET runtime instead of an interpreter, so it is as responsive as the Apple
    Silicon half.
  • Dual-GPU Intel MacBook Pros use their discrete GPU while the wallet is open. macOS was driving the
    Retina display with the integrated GPU, which made every page feel slow. Expect a little more fan and
    battery use on those machines while the wallet runs; it hands the GPU back when you quit.
  • Faster page changes and image loading on every Mac: background images are cached between pages
    instead of being reloaded and decoded every time, and the Import, Backup and Quantum Exposure
    animations no longer redraw the whole screen every frame.
  • Provenance works out of the box. The bundled node now keeps a transaction index, which the
    Provenance page needs. The index builds in the background after the first launch and takes about
    15 minutes on an M1; Provenance shows results once it is complete.
  • Sync progress is visible from the first minute. While the node pre-syncs headers the status bar
    says so, with a count, instead of sitting at "0 / 0 blocks".
  • One-click "Create wallet" on the first-run screen (the Terminal command is still shown as a fallback).
  • PDF export of transactions works on Apple Silicon. It needs macOS 15 or newer.
  • V1.5 wallet import converts the old Berkeley DB file directly, including files written by the
    macOS V1.5 build, and rescans from where V1.5 left off.
  • The app icon is the Blazecoin icon, the dashboard coins are sharp on Retina displays, and the window
    is dark regardless of the system appearance.

Notes for users

  • Wallet and chain data live at ~/Library/Application Support/BlazecoinV2.0/. The wallet starts the
    bundled node on launch and stops it cleanly when you quit; a node you started yourself is left alone
    (and then keeps running after you quit — stop it with the command below if you need to).

  • First launch downloads and verifies the full chain — allow a few hours. The status bar shows the
    header pre-sync, then headers, then blocks.

  • A brand-new install has no wallet yet, so the first screen says No wallet found — click
    Create wallet "Primary" and the app makes one. (The card also shows the equivalent Terminal
    command; the node's tools live inside the app bundle, which is why it carries the full path:

    "/Applications/Blazecoin Wallet V2.app/Contents/MacOS/blazecoin-cli" -named createwallet wallet_name="Primary"
    

    Then click Check again. (… blazecoin-cli stop stops the node the same way.)

  • Bringing a V1.5 wallet across: Import page → Choose wallet.dat… → your V1.5 wallet.dat (on a Mac
    it is at ~/Library/Application Support/BlazecoinV1.5/wallet.dat; the file dialog hides the Library
    folder, so press ⌘⇧G and paste the path, or copy the file to your Desktop first). It is converted to the
    V2 descriptor format and rescanned from where V1.5 left off; your V1.5 file is not modified and a
    .legacy.bak copy is kept beside the new wallet.

  • Back up your wallet (Backup page) after you receive coins.

Known limitations

  • Requires macOS 12 (Monterey) or newer; PDF export requires macOS 15 or newer.
  • Not notarized: the Gatekeeper step above is needed on every fresh download.
  • The Backup page has no folder picker on macOS — type or paste the destination path.
  • Transaction exports save straight to ~/Downloads.
  • On the Intel MacBook Pro the Quantum Exposure page's drifting background can still drop the odd frame.

Blazecoin Wallet 2.0.7 (Windows)

Choose a tag to compare

@AMA-CSharp-Code AMA-CSharp-Code released this 15 Sep 16:35

Blazecoin Wallet 2.0.7 (Windows)

What changed: a wallet update on top of 2.0.6. It still bundles Blazecoin Core 2.1.0, the post-quantum fork daemon required before block 4,250,000. If you are on wallet 2.0.4 or earlier, install this release before the fork height so the bundled node follows the chain through it.

New in this release:

  • Faster Quantum Exposure scan on large wallets. The scan now reads the wallet's history in one pass. A mining wallet with tens of thousands of transactions previously sat at "listing" for several minutes; it now finishes in seconds. While it reads, the page shows "reading wallet history" with a running timer, so it never looks frozen.
  • Quantum Exposure table fixes. The Outputs and BLZ figures now sit in their own columns (the BLZ amount was wrapping under the output count), headers and figures are centred, and stacked status badges such as Unexposed and Reused have a clear gap between them.

Install: run BlazecoinWalletV2-Setup-2.0.7.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:

bb419432b85ab2ecb3675bc270f0df7904e683c362d33586347f821145578404  BlazecoinWalletV2-Setup-2.0.7.exe

Requires Windows 10/11 x64. Unsigned build, so SmartScreen will ask once.