Skip to content

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

Choose a tag to compare

View all tags
@AMA-CSharp-Code AMA-CSharp-Code released this 15 Sep 11:05
· 1 commit to main since this release
v2.1.0-linux
2a24699

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.

Assets 4
Loading