Blazecoin Core 2.1.1 (Windows)

Blazecoin Core 2.1.1 — maintenance release: the post-quantum fork checkpoint and refreshed sync anchors.

A small release on top of 2.1.0. Consensus is unchanged: a 2.1.0 node and a 2.1.1 node follow the same rules and stay on the same chain. Upgrading is recommended but not mandatory.

What is in this release

• Checkpoint at block 4,250,000, the post-quantum activation height (H_Q, passed on 2026-09-16). A node syncing from scratch now rejects any chain that disagrees with the real history at the fork, before it has done the work of validating it.
• Fresh initial-sync anchors. defaultAssumeValid moves to block 4,319,107 (2026-10-09), with the minimum chain work set to that block's exact chain work and the chain statistics (4,849,335 transactions, one-year rate) refreshed from the same anchor. A new node skips signature checks up to that block on its first sync, as 2.1.0 did up to block 4,168,925; proof of work is still checked on every block.
• Version 2.1.1 is reported by getnetworkinfo and --version.

Upgrade: stop the old daemon (blazecoin-cli stop), replace blazecoind and blazecoin-cli, start again. No rescan or re-index is needed. Wallets, data directories and configuration carry over unchanged.

Downloads

• Blazecoin-Core-V2.1.1-windows-x64.zip — blazecoind.exe, blazecoin-cli.exe, a blazecoin.conf template and a README. Windows 10/11 x64.
• Blazecoin-Core-V2.1.1-linux-x86_64.tar.gz — blazecoind, blazecoin-cli. Needs glibc 2.35 or later (Ubuntu 22.04 and newer, Debian 12 and newer).

SHA256SUMS lists both archives.

Blazecoin Core 2.1.1 (Linux)

Blazecoin Core 2.1.1 — maintenance release: the post-quantum fork checkpoint and refreshed sync anchors.

A small release on top of 2.1.0. Consensus is unchanged: a 2.1.0 node and a 2.1.1 node follow the same rules and stay on the same chain. Upgrading is recommended but not mandatory.

What is in this release

• Checkpoint at block 4,250,000, the post-quantum activation height (H_Q, passed on 2026-09-16). A node syncing from scratch now rejects any chain that disagrees with the real history at the fork, before it has done the work of validating it.
• Fresh initial-sync anchors. defaultAssumeValid moves to block 4,319,107 (2026-10-09), with the minimum chain work set to that block's exact chain work and the chain statistics (4,849,335 transactions, one-year rate) refreshed from the same anchor. A new node skips signature checks up to that block on its first sync, as 2.1.0 did up to block 4,168,925; proof of work is still checked on every block.
• Version 2.1.1 is reported by getnetworkinfo and --version.

Upgrade: stop the old daemon (blazecoin-cli stop), replace blazecoind and blazecoin-cli, start again. No rescan or re-index is needed. Wallets, data directories and configuration carry over unchanged.

Downloads

• Blazecoin-Core-V2.1.1-windows-x64.zip — blazecoind.exe, blazecoin-cli.exe, a blazecoin.conf template and a README. Windows 10/11 x64.
• Blazecoin-Core-V2.1.1-linux-x86_64.tar.gz — blazecoind, blazecoin-cli. Needs glibc 2.35 or later (Ubuntu 22.04 and newer, Debian 12 and newer).

SHA256SUMS lists both archives.

Blazecoin Core 2.1.0 — post-quantum fork at block 4,250,000

Blazecoin Core 2.1.0 — post-quantum fork at block 4,250,000.

This release adds P2PQH, a post-quantum output type: coins can now be sent to BQ… addresses whose
spends are signed with ML-DSA-44 (NIST FIPS 204, a lattice-based signature scheme) instead of
ECDSA. Legacy B… addresses and their ECDSA spends remain valid for ever — nothing about existing
keys, addresses or coins changes, and no action is needed to keep them. The new outputs become
spendable at block 4,250,000; from that height the network follows consensus rules that no earlier
release implements.

Mandatory for every node before block 4,250,000. A 2.0.x node stops at the first post-quantum spend
after the fork and does not recover without this release. Upgrade in place: stop the old daemon
(blazecoin-cli stop), replace the binaries, start again; no rescan or re-index is needed.
V1.5.x and the 2014 client are retired by this fork.

Using it

• getnewaddress "" pq — a new post-quantum BQ… address (52 characters; may be generated before the
  fork, spendable from block 4,250,000). pq is also accepted by getrawchangeaddress and -changetype.
• validateaddress / getaddressinfo report "type": "pqkh" and "algorithm": "ML-DSA-44" for a
  BQ… address; decodescript names the script type pqkh.
• signmessage / verifymessage work with BQ… addresses (an ML-DSA-44 signature, base64, 3,733
  characters).
• getdeploymentinfo lists the fork as pqsig (buried, height 4,250,000) next to phoenix413.
• Wallets: a descriptor wallet created with 2.1.0 carries a post-quantum receive/change chain from
  creation; the PQ seed is covered by wallet encryption like any other key. A wallet created before
  2.1.0 loads and works unchanged but has no post-quantum chain — getnewaddress "" pq returns a clear
  error; create a new descriptor wallet to receive at BQ… addresses (legacy, non-descriptor wallets
  cannot hold post-quantum keys). dumpprivkey/importprivkey do not apply to BQ… addresses.
• Specification: PQ_SIGNATURES.md in the source tree (output type, digest, addresses, activation).

What is in this release

• Blazecoin-Core-V2.1.0-windows-x64.zip — blazecoind + blazecoin-cli + a default blazecoin.conf
  (daemon build of 2026-09-15).
• Blazecoin-Core-V2.1.0-linux-x86_64.tar.gz — the same daemon + cli for Linux x86_64 (glibc 2.35+;
  boost, libevent and sqlite built in). Linux is daemon-only: the graphical wallet is Windows; on
  Linux use the web wallet at https://gw.blazecoin.co.uk.
• The daemon inside both bundles reports Blazecoin Core version v2.1.0 (Windows and Linux alike).

Verify every file against SHA256SUMS before running it:

9f98c660839c24cd313a947c280867184d75b7dc08a61e9b333eb4373ed62add  Blazecoin-Core-V2.1.0-linux-x86_64.tar.gz
1327914d92a671c2cff62decf3da8f971f2b596c51a07af1e62d1e3941fb90e7  Blazecoin-Core-V2.1.0-windows-x64.zip

Network: P2P 55414, RPC 55413 (loopback). Fixed seeds: the two public relays. Addresses start with
B (legacy) or BQ (post-quantum); there is no bech32.

Your keys: the wallet keeps wallet.dat under the datadir; back it up — a backup taken before a
post-quantum chain was added to a wallet does not contain that chain, so take a fresh one after your
first getnewaddress "" pq. Nobody can recover coins for you.

Blazecoin Core 2.1.0 — Linux x86_64 (post-quantum fork at block 4,250,000)

Blazecoin Core 2.1.0 — post-quantum fork at block 4,250,000.

This release adds P2PQH, a post-quantum output type: coins can now be sent to BQ… addresses whose
spends are signed with ML-DSA-44 (NIST FIPS 204, a lattice-based signature scheme) instead of
ECDSA. Legacy B… addresses and their ECDSA spends remain valid for ever — nothing about existing
keys, addresses or coins changes, and no action is needed to keep them. The new outputs become
spendable at block 4,250,000; from that height the network follows consensus rules that no earlier
release implements.

Mandatory for every node before block 4,250,000. A 2.0.x node stops at the first post-quantum spend
after the fork and does not recover without this release. Upgrade in place: stop the old daemon
(blazecoin-cli stop), replace the binaries, start again; no rescan or re-index is needed.
V1.5.x and the 2014 client are retired by this fork.

Using it

• getnewaddress "" pq — a new post-quantum BQ… address (52 characters; may be generated before the
  fork, spendable from block 4,250,000). pq is also accepted by getrawchangeaddress and -changetype.
• validateaddress / getaddressinfo report "type": "pqkh" and "algorithm": "ML-DSA-44" for a
  BQ… address; decodescript names the script type pqkh.
• signmessage / verifymessage work with BQ… addresses (an ML-DSA-44 signature, base64, 3,733
  characters).
• getdeploymentinfo lists the fork as pqsig (buried, height 4,250,000) next to phoenix413.
• Wallets: a descriptor wallet created with 2.1.0 carries a post-quantum receive/change chain from
  creation; the PQ seed is covered by wallet encryption like any other key. A wallet created before
  2.1.0 loads and works unchanged but has no post-quantum chain — getnewaddress "" pq returns a clear
  error; create a new descriptor wallet to receive at BQ… addresses (legacy, non-descriptor wallets
  cannot hold post-quantum keys). dumpprivkey/importprivkey do not apply to BQ… addresses.
• Specification: PQ_SIGNATURES.md in the source tree (output type, digest, addresses, activation).

What is in this release

• Blazecoin-Core-V2.1.0-windows-x64.zip — blazecoind + blazecoin-cli + a default blazecoin.conf
  (daemon build of 2026-09-15).
• Blazecoin-Core-V2.1.0-linux-x86_64.tar.gz — the same daemon + cli for Linux x86_64 (glibc 2.35+;
  boost, libevent and sqlite built in). Linux is daemon-only: the graphical wallet is Windows; on
  Linux use the web wallet at https://gw.blazecoin.co.uk.
• The daemon inside both bundles reports Blazecoin Core version v2.1.0 (Windows and Linux alike).

Verify every file against SHA256SUMS before running it:

9f98c660839c24cd313a947c280867184d75b7dc08a61e9b333eb4373ed62add  Blazecoin-Core-V2.1.0-linux-x86_64.tar.gz
1327914d92a671c2cff62decf3da8f971f2b596c51a07af1e62d1e3941fb90e7  Blazecoin-Core-V2.1.0-windows-x64.zip

Network: P2P 55414, RPC 55413 (loopback). Fixed seeds: the two public relays. Addresses start with
B (legacy) or BQ (post-quantum); there is no bech32.

Your keys: the wallet keeps wallet.dat under the datadir; back it up — a backup taken before a
post-quantum chain was added to a wallet does not contain that chain, so take a fresh one after your
first getnewaddress "" pq. Nobody can recover coins for you.

Blazecoin V2.0.1 — Windows x64

Blazecoin V2.0.1 — the first public V2 release.

V2 is the 2014 Blazecoin chain on a Bitcoin Core 28 node. Consensus is unchanged from 2014 except for
Phoenix-413, the per-block difficulty retarget that activated at block 4,194,000 on 26 August 2026;
this release validates the whole chain from genesis and follows it past the fork. Pre-fork clients
(V1.5.x, the 2014 0.8.6.2 client) cannot.

What is in this release

• Blazecoin-Core-V2.0.1-windows-x64.zip — blazecoind + blazecoin-cli + a default blazecoin.conf (daemon build of 2026-08-26).
• Blazecoin-Core-V2.0.1-linux-x86_64.tar.gz — the same daemon + cli for Linux x86_64 (glibc 2.35+; boost, libevent and sqlite built in). Linux is daemon-only: the graphical wallet is Windows; on Linux use the web wallet at https://gw.blazecoin.co.uk.
• The daemon inside both bundles reports Blazecoin Core version v2.0.0 (the 26 August build); 2.0.1 is the release/wallet version.
• BlazecoinWalletV2-Setup-2.0.1.exe — the desktop wallet (.NET 10 MAUI) with the daemon bundled; per-user install, no admin rights, WebView2 bootstrapped if absent. Unsigned: SmartScreen will ask you to confirm.

Verify every file against SHA256SUMS before running it.

Network: P2P 55414, RPC 55413 (loopback). Fixed seeds: the two public relays. Addresses start with B; there is no bech32.

Your keys: the wallet keeps wallet.dat under the datadir; back it up. Nobody can recover coins for you.

Blazecoin V2.0.1 — Linux x86_64

Blazecoin V2.0.1 — the first public V2 release.

V2 is the 2014 Blazecoin chain on a Bitcoin Core 28 node. Consensus is unchanged from 2014 except for
Phoenix-413, the per-block difficulty retarget that activated at block 4,194,000 on 26 August 2026;
this release validates the whole chain from genesis and follows it past the fork. Pre-fork clients
(V1.5.x, the 2014 0.8.6.2 client) cannot.

What is in this release

• Blazecoin-Core-V2.0.1-windows-x64.zip — blazecoind + blazecoin-cli + a default blazecoin.conf (daemon build of 2026-08-26).
• Blazecoin-Core-V2.0.1-linux-x86_64.tar.gz — the same daemon + cli for Linux x86_64 (glibc 2.35+; boost, libevent and sqlite built in). Linux is daemon-only: the graphical wallet is Windows; on Linux use the web wallet at https://gw.blazecoin.co.uk.
• The daemon inside both bundles reports Blazecoin Core version v2.0.0 (the 26 August build); 2.0.1 is the release/wallet version.
• BlazecoinWalletV2-Setup-2.0.1.exe — the desktop wallet (.NET 10 MAUI) with the daemon bundled; per-user install, no admin rights, WebView2 bootstrapped if absent. Unsigned: SmartScreen will ask you to confirm.

Verify every file against SHA256SUMS before running it.

Network: P2P 55414, RPC 55413 (loopback). Fixed seeds: the two public relays. Addresses start with B; there is no bech32.

Your keys: the wallet keeps wallet.dat under the datadir; back it up. Nobody can recover coins for you.