[ANN] Quantum Bitcoin (QBTC) - GPU & CPU PoW Mainnet (ML-DSA-65, Fair Launch)

[qbtc-core]

Background: Why Quantum Bitcoin (Q-BTC)?

The physical qubit threshold required to break elliptic-curve cryptography (secp256k1) is dropping faster than anticipated. In legacy PoW networks, Shor's algorithm does not just threaten dormant addresses with exposed public keys; broadcasting a standard transaction exposes the public key in the mempool, turning the 10-minute confirmation window into a direct attack surface. Meanwhile, retrofitting legacy chains faces severe coordination bottlenecks, millions of unmigrated coins, and block-size bloat from large post-quantum signatures.

Quantum Bitcoin (Q-BTC) was built from scratch in Rust to solve this cleanly from Block 0 - combining Bitcoin's sound monetary rules (21,000,000 cap, pure PoW, fair launch) with native post-quantum security from Genesis.

Motto: "17/May/2026: The quantum age dawns. The 21,000,000 truth shines eternal."

Core Architecture & Specifications:

• Consensus & Cryptography: Full deprecation of ECDSA. Native L1 integration of NIST FIPS 204 ML-DSA-65 (Module-Lattice-Based Digital Signature) from Genesis, protecting public keys both in the mempool and on-chain.
• Witness Commitment & Relay: Dual-Merkle 120-byte block headers committing simultaneously to stripped transaction IDs (merkle_root) and full ML-DSA-65 witness hashes (commit_merkle_root), paired with Q-BIP-152 Compact Block relay.
• State & Storage (PQ-SegWit): 8MB / 32M WU PQ-SegWit architecture isolating large post-quantum signatures (~3,309 bytes) from core transaction data, backed by hot/cold RocksDB storage partitioning.
• Monetary & Mining Rules: Pure PoW (SHA-256) with deterministic ASERTi3-2d per-block difficulty adjustment. Strict 21,000,000 supply cap. No premine, no ICO, no dev tax.

Official Links:
- Source Code (GitHub): https://github.com/Q-Jack-core/quantum-btc
- Desktop GUI Miner: https://github.com/Q-Jack-core/qbtc-desktop
- Live Block Explorer & Web Wallet: https://explorer.qbtc-core.org
- Official Telegram: https://t.me/qbtc_genesis

------------------------------------------------------------------------
[UPDATE: October 19, 2026 - Block 25,450+ | Core v2.6.2 & GUI v1.2.2 | Full GTX 10 to RTX 50 Support]

The Q-BTC mainnet has crossed Block 25,450+ (with the Block 25,000 witness commitment upgrade smoothly activated).
Core v2.6.2 and Desktop GUI v1.2.2 are now live, featuring sync improvements and full NVIDIA CUDA support across all GPU architectures from GTX 10 series to RTX 50 series (0% Dev Fee, with multi-threaded CPU fallback):

- Core v2.6.2 (CUDA & CPU): https://github.com/Q-Jack-core/quantum-btc/releases/tag/v2.6.2
- Desktop GUI Miner v1.2.2: https://github.com/Q-Jack-core/qbtc-desktop/releases/tag/v1.2.2
- Live Explorer & Web Wallet: https://explorer.qbtc-core.org
- Official Telegram: https://t.me/qbtc_genesis
------------------------------------------------------------------------

[UPDATE: October 10, 2026 - 24,000+ Blocks & Native CUDA GPU Mining Live]

The Q-BTC mainnet has crossed Block 24,000+ with network hashrate surpassing 6+ GH/s!
To prevent closed-source mining monopolies and protect a strictly fair launch, Core v2.6.0 and Desktop Miner v1.2.0 have officially integrated an in-tree native CUDA GPU engine (0% Dev Fee), alongside multi-threaded CPU fallback:

- Core v2.6.0 (CUDA & CPU): https://github.com/Q-Jack-core/quantum-btc/releases/tag/v2.6.0
- Desktop GUI Miner v1.2.0: https://github.com/Q-Jack-core/qbtc-desktop/releases/tag/v1.2.0
- Stratum Pool: stratum+tcp://144.172.110.193:3334
- Pool Stats API: http://144.172.110.193:3335/api/stats
--------------------------------------------------

[UPDATE: September 14, 2026 - 20,000 Blocks Milestone & Official Community]

The Q-BTC mainnet has successfully crossed the 20,000 block milestone! The base layer consensus and ML-DSA-65 architecture have proven exceptionally stable under live network conditions.

With the core node, GUI miner, and Stratum pool fully deployed, the foundational infrastructure is now complete. As the network hashrate grows, it's time to gather the collective wisdom of our early miners.

To coordinate network upgrades, gather miner feedback, and discuss the future roadmap, the official Telegram group is now open. All active miners and early believers are welcome to join the Genesis Members:

Official Telegram: https://t.me/qbtc_genesis
---------------------------------------------------------------------

[UPDATE: August 31, 2026 - Web Explorer & Faucet Deployed]

A web-based explorer and faucet have been deployed:
https://explorer.qbtc-core.org

Users can generate an ML-DSA-65 address directly in the browser (keys are generated and kept client-side) and claim 5 QBTC to interact with the network and execute transactions. The faucet is strictly rate-limited to 1 request per IP address every 24 hours.
-------------------------------------------------------------------

[UPDATE: May 17, 2026 - Mainnet Officially Launched]
The Genesis block has been established. The April blueprint is now reality:
"17/May/2026: The quantum age dawns. The 21,000,000 truth shines eternal."

[UPDATE: Late July 2026 - Technical Rationale & Design Choices]

Some have asked about the necessity of a new chain. Q-BTC is designed as a cryptographic insurance policy for Nakamoto consensus. When ECDSA inevitably fails against quantum adversaries, a purely L1 post-quantum ledger must already be operational and distributed. Here is the architecture.

Q: Why ML-DSA-65 (FIPS 204) over hash-based signatures like SPHINCS+?
SPHINCS+ is conservative (relying solely on SHA-256 collision resistance) but yields 40 KB signatures. It breaks native P2P network propagation without heavy Layer-2 ZK wrappers. We opted for Base-Layer viability. ML-DSA-65 provides Category 3 post-quantum security with ~3.3 KB payloads. It is the pragmatic engineering choice between lattice-based security and maintaining an unpruned, decentralized mesh network.

Q: Won't ~3.3 KB signatures cause massive blockchain bloat and disk I/O bottlenecks?
Yes, if handled naively. We mitigated this via Post-Quantum Segregated Witness (PQ-SegWit) engineered directly at the storage engine layer (storage.rs). Signature payloads are strictly decoupled from core UTXO state mutations and flushed atomically to cold partitions via RocksDB WriteBatch. Furthermore, nodes can prune historical witness data past a specific block depth, keeping IOPS lean for standard hardware.

Q: How does the network handle sudden hashrate spikes?
We use ASERTi3-2d. It is a continuous, per-block difficulty adjustment algorithm using fixed-point 128-bit math. Unlike the legacy 2016-block retargeting, ASERT adjusts target bounds instantly based on a 12-hour half-life. A high-core-count farm joining or leaving will seamlessly alter the target within blocks, preventing network stagnation.

Q: Is there a pre-mine, dev tax, or VC fund?
No dev tax. No VC. No ICO.
Full disclosure: The Genesis block was mined on May 17, 2026. The first 200 blocks were mined by the founder to establish Checkpoint 200 (Mainnet Launch Anchor). This bootstrap phase was mathematically required to stabilize the exponential ASERT algorithm and prevent cheap 51% attacks during network infancy. After Block 200, the source code was published. The network now relies strictly on public consensus.

[qbtc-core]

UPDATE: May 22, 2026 (Bitcoin Pizza Day) - MAINNET IS LIVE & WHITEPAPER V2.0

Sixteen years ago today, classical Bitcoin established its first physical value boundary. Today, we establish its post-quantum survival boundary.

The theoretical blueprint phase is over. The Q-BTC Post-Quantum Mainnet is officially LIVE.

Over the past month, the architecture has been materialized from the ground up into a pure Rust physical implementation. The North American seed nodes (Dallas & Utah) are fully synchronized, and the network is actively hashing via the 128-bit fixed-point ASERTi3-2d continuous difficulty engine.

Core Deliverables Today:

• 100% Open Source Codebase Released: The complete Layer-1 consensus engine, featuring native ML-DSA-65 signatures, Actor-Driven UTXO rollbacks, and compact block routing, is now public.
  
• Official Whitepaper V2.0 Published: Deeply refined mathematical models, introducing the L1 Asymmetric Time-Lock Recovery Game and the ZK-STARKs stateless verification evolutionary roadmap.
  
• Genesis Bootstrapping Concluded: The initial 200-block physical bootstrapping phase is complete. This was executed strictly to calibrate the difficulty engine under live conditions and stress-test the RocksDB I/O against massive lattice signatures. The network has achieved operational equilibrium and is now completely open to global, decentralized PoW participation.
  

Official GitHub Repository (Source Code & Whitepaper V2.0):
https://github.com/Q-Jack-core/quantum-btc

There are no pre-compiled binaries for the masses yet, no VC allocations, no presales, and no complex tokenomics. Just pure, monolithic PoW consensus. True cypherpunks build for the protocol.

To participate: Clone the repository, compile from source (cargo build --release), and let your nodes sync.

"17/May/2026: The quantum age dawns. The 21,000,000 truth shines eternal."

[BoozyTalking]

Code:

INFO] System: Q-BTC mainnet genesis block generator initialized.
========================================================
INFO] Genesis: Initializing genesis block.
INFO] Genesis: Motto: "17/May/2026: The quantum age dawns. The 21,000,000 truth shines eternal."
INFO] Genesis: Identity: qbtc1tpv0e2s92eurft7z5v3l592l2m8a8cy0hdg967mcr3pk3pwh026qpkn68x 
INFO] Genesis Motto: "17/May/2026: The quantum age dawns. The 21,000,000 truth shines eternal."
INFO] Timestamp: 1778976000
INFO] Target Difficulty: 1099511627775
INFO] Engine started. Calculating nonce...

INFO] Progress: 2 million hashes computed. Rate: 8.13 MH/s.
INFO] Progress: 4 million hashes computed. Rate: 8.23 MH/s.
INFO] Progress: 6 million hashes computed. Rate: 8.22 MH/s.

========================================================
INFO] Valid nonce discovered.
========================================================
INFO] Nonce: 6759977
INFO] Genesis Hash: 0x00000039ed259365a978de048e4c3d22a75e07573035e00ef4d0f1ea1b934402                                                                               │
INFO] Time elapsed: 0.82 seconds.
========================================================
INFO] Action required: Update src/block.rs with the discovered nonce.

[jooosen]

Where is website,How to mine this coin

[qbtc-core]

Code:

INFO] System: Q-BTC mainnet genesis block generator initialized.
========================================================
INFO] Genesis: Initializing genesis block.
INFO] Genesis: Motto: "17/May/2026: The quantum age dawns. The 21,000,000 truth shines eternal."
INFO] Genesis: Identity: qbtc1tpv0e2s92eurft7z5v3l592l2m8a8cy0hdg967mcr3pk3pwh026qpkn68x 
INFO] Genesis Motto: "17/May/2026: The quantum age dawns. The 21,000,000 truth shines eternal."
INFO] Timestamp: 1778976000
INFO] Target Difficulty: 1099511627775
INFO] Engine started. Calculating nonce...

INFO] Progress: 2 million hashes computed. Rate: 8.13 MH/s.
INFO] Progress: 4 million hashes computed. Rate: 8.23 MH/s.
INFO] Progress: 6 million hashes computed. Rate: 8.22 MH/s.

========================================================
INFO] Valid nonce discovered.
========================================================
INFO] Nonce: 6759977
INFO] Genesis Hash: 0x00000039ed259365a978de048e4c3d22a75e07573035e00ef4d0f1ea1b934402                                                                               │
INFO] Time elapsed: 0.82 seconds.
========================================================
INFO] Action required: Update src/block.rs with the discovered nonce.

Welcome to the quantum age, BoozyTalking.
The genesis block was just the ignition. The network is alive and the target is adjusting. May your hashes be fast.

Where is website,How to mine this coin

Welcome! We are building this from the ground up, so it's just pure code right now—no fancy websites.
Mining currently requires running a full node and compiling the Rust code yourself. We'd love to have you onboard if you enjoy tinkering with new open-source protocols. Check the GitHub link in the main post to get started!

[Geobees]

Code:

verify_recovery_reveal

is a stub, recovery claims are unverified.
In

Code:

utxo.rs

, the function that's supposed to validate a delayed-recovery claim against the committed

Code:

recovery_hash

does absolutely nothing:

Code:

fn verify_recovery_reveal(&self, tx: &Transaction, input_idx: usize, _target_hash: &[u8; 32]) -> bool {
    // "For the current version, existence of a valid witness for the heir is checked."
    tx.witnesses.get(input_idx).is_some()
}

The

Code:

_target_hash

parameter is ignored entirely. Any attacker who knows a UTXO has a

Code:

RecoveryInfo

field, and waits out the

Code:

activation_height

, can steal those coins by supplying any valid witness at all. The recovery hash commitment provides zero protection. This is a fund theft vector and a disqualifying bug for any mainnet use.

[qbtc-core]

Code:

verify_recovery_reveal

is a stub, recovery claims are unverified.
In

Code:

utxo.rs

, the function that's supposed to validate a delayed-recovery claim against the committed

Code:

recovery_hash

does absolutely nothing:

Code:

fn verify_recovery_reveal(&self, tx: &Transaction, input_idx: usize, _target_hash: &[u8; 32]) -> bool {
    // "For the current version, existence of a valid witness for the heir is checked."
    tx.witnesses.get(input_idx).is_some()
}

The

Code:

_target_hash

parameter is ignored entirely. Any attacker who knows a UTXO has a

Code:

RecoveryInfo

field, and waits out the

Code:

activation_height

, can steal those coins by supplying any valid witness at all. The recovery hash commitment provides zero protection. This is a fund theft vector and a disqualifying bug for any mainnet use.

Hey Geobees,

You are absolutely right. Fantastic catch. This is exactly why we launched this experimental mainnet with zero VC backing and open-sourced everything—to test the anti-quantum architecture in the wild under the scrutiny of true cypherpunks like you.

The `verify_recovery_reveal` stub was indeed a critical oversight during our rapid transition from the testnet sandbox to the live mainnet environment.

**Action Taken:**
We have immediately addressed this. The Zero-Day vulnerability is completely patched in our latest release (**v2.0.3**).

The new consensus rule now strictly enforces:
1. Absolute SHA-256 hash matching against the committed `target_hash`.
2. A mandatory cryptographic proof of ownership via `crypto::ml_dsa::verify_signature` using the backup post-quantum key.

Our North American seed nodes and the majority of our hashing power have already been hard-forked to the v2.0.3 consensus rules.

**To all other miners currently on v2.0.2 or older:**
You MUST update your binaries or pull the latest source code from GitHub immediately. If a malicious recovery transaction is broadcasted, your outdated nodes will fork off onto an invalid chain, and your mined blocks will be rejected by the mainnet.

Thank you again, Geobees. The true spirit of decentralized security is alive and well.

Download v2.0.3 here: https://github.com/Q-Jack-core/quantum-btc/releases/latestHi Geobees,

Thank you for your diligent catch on the verify_recovery_reveal issue. Your report was spot on and successfully prevented a potential major incident.

I have just pushed a comprehensive patch (v2.0.3) to resolve this, which is now live.

We value feedback from those who engage deeply with our architecture. If you are running a node or actively involved with the Q-BTC network, we would love to hear about your experience. Your keen eye for detail regarding our architecture exemplifies the essence of the decentralized spirit.

Thank you again for strengthening our security baseline.

Best regards,
-J.
Q-BTC Core

[luk3Z]

Hi Q-BTC Core team. Who are you ? Please tell us something about you.

[qbtc-core]

Hi Q-BTC Core team. Who are you ? Please tell us something about you.

Hi luk3Z,

Who we are is irrelevant. In a decentralized system, personal identity is just a distraction.

We simply saw the impending quantum threat and decided to build a lifeboat before it was too late. You don't need to know us; you only need to verify the open-source code and trust the mathematics.

As our Genesis block states:
"17/May/2026: The quantum age dawns. The 21,000,000 truth shines eternal."

[qbtc-core]

Update: July 19, 2026 - Mainnet passed block 12,000

Hey everyone. Just wanted to drop a quick update here. The Q-BTC mainnet has been running smoothly and we just successfully crossed block height 12,000 in the wild.

The 128-bit fixed-point ASERT difficulty algorithm is holding block times perfectly stable. The network is healthy, but as we continue to grow, we are looking to expand the decentralized hash rate.

If anyone here has idle EPYC or Ryzen rigs and is looking for a genuine CPU-only project, this is a great time to jump in and point your hash power here.

Just a quick reminder on the architecture: Q-BTC natively integrates ML-DSA-65 post-quantum signatures at the consensus layer. It is the sheer mathematical complexity of our custom consensus algorithm—built around this heavy lattice-based cryptography—that naturally renders legacy ASICs completely useless. It enforces strictly bare-metal CPU PoW by design.

There is no pre-mine and no VC backing. It is a 100% grassroots fair launch.

You can compile the node from source (pure Rust) and start hashing today.

Source and instructions: https://github.com/Q-Jack-core/quantum-btc

Let me know if you have any issues compiling in your terminal.

Code:

[INFO] Miner: 42200 million hashes calculated.
[INFO] Miner: 42300 million hashes calculated.
[INFO] Miner: 42400 million hashes calculated.
[INFO] Miner: 42500 million hashes calculated.

[qbtc-core]

Update on Q-BTC Mainnet: Block 13,000 and Core v2.1.0

The illusion of perpetual security is the root problem of today's crypto ecosystem. With Google's Willow chip crossing the fault-tolerance threshold, ECDSA is on a definitive countdown. The industry is building on a fault line.

Q-BTC was ignited on May 17, 2026, to address this singular point of failure:
"17/May/2026: The quantum age dawns. The 21,000,000 truth shines eternal."

Without fanfare, pre-mines, or VC backing, the network has quietly surpassed block 13,000.

The protocol works. The ASERTi3-2d algorithm has stabilized the block time, and our node architecture flawlessly handles the heavy ~3.3 KB ML-DSA-65 signatures.

To scale with growing hashrate, Core Release v2.1.0 is now live on GitHub.

Dynamic CPU Isolation Engine: We rewrote the core scheduler. Consensus and P2P network threads are now physically isolated from hashing threads at the OS level.

Result: Zero P2P freezing on high-core-count rigs (EPYC/Threadripper). 100% bare-metal hashing throughput.

The genesis bootstrap phase is complete. The network is public. It remains strictly CPU-bound to preserve the original "one-CPU-one-vote" ethos.

Security relies on mathematical proof, not hope. The software is available.

The network is waiting.

-J.
Q-BTC Core

[qbtc-core]

[UPDATE: Architecture Deep Dive - Why Q-BTC is Immune to NIST/NSA Backdoors]

Recently, there has been significant noise in cryptography mailing lists regarding NIST's "post-quantum" standardization process, IBM's heavy involvement, and the historical specter of NSA-engineered backdoors (e.g., Dual_EC_DRBG).

Let's clear this up right now. Q-BTC does not trust institutions. We trust math, and we trust bare-metal, open-source consensus.

Here is exactly why Q-BTC’s implementation of ML-DSA-65 is mathematically and physically insulated from any institutional interference or backdoor attempts.

1. The Mathematical Layer: No "Magic Numbers"

Legacy elliptic curves often relied on official "magic numbers" handed down by authorities. If the creator knew the discrete log relations behind those constants, they held a backdoor. ML-DSA (based on the Module-LWE problem) cuts this off at the source.

No Global Constants: The massive polynomial matrix A used in ML-DSA is not a global parameter predefined by NIST or IBM.

Local Entropy Driven: When generating your keys, Matrix A is expanded directly from a pure random seed generated by your local wallet's physical TRNG, fed through the SHAKE-128/256 hash function.

NIST never touches your seed. To backdoor your matrix, an agency would have to break the pre-image resistance of the Keccak (SHA-3) family. As long as Keccak holds, your public key matrix is a cryptographically transparent labyrinth that belongs solely to you.

2. The Physical Defense: Q-BTC’s 4-Layer Architecture

On the engineering side, we enforce absolute decentralization.

Zero C/C++ FFI (100% Pure Rust): We completely discarded the official NIST/IBM C reference code. There are no pre-compiled binaries, no .so or .dll black boxes. Q-BTC is compiled from scratch in Pure Rust, bricking traditional buffer overflows and pointer traps at the compiler level.

Autonomous Derivation: Public parameters are derived deterministically from transaction hashes. There are no hidden "if" branches, no admin keys, and no remote execution vectors in our lattice algebra library.

Strict Constant-Time Execution: We are well aware that ML-DSA utilizes rejection sampling (Fiat-Shamir with aborts), making the total signature time variable. However, our lower-level Rust implementation heavily isolates this: every single operation that touches the private key (e.g., high-precision NTT polynomial multiplications) is forced into strict constant-time execution. Cache-miss and timing side-channel attacks are physically bricked.

The Thermodynamic Backstop (Nakamoto PoW): What if the absolute worst happens and an unknown lattice weakness is discovered? Q-BTC's base layer is anchored by proof-of-work, not authorized signers. An attacker might forge a signature to steal an isolated UTXO, but they can never hijack the network, alter historical blocks, or issue a "pause" command. Thermodynamic PoW guarantees we survive long enough to hard-fork and rebuild. The protocol does not die.

We use ML-DSA-65 because decades of cryptanalysis on Module-LWE prove it works, not because NIST stamped it.

Cryptography belongs to mathematics, and mathematics belongs to everyone.

-J.
Q-BTC Core

[Larppa]

I've been mining Q-BTC for a little while now and the network seems to have grown quite a lot. I'm currently seeing around 1.15 GH/s network hashrate.

Mining and the node have been working fine for me, so I'm curious what the next steps are for the project. Is there anything new being worked on after v2.1.0?

Also, are there any plans for a pool/Stratum support or improvements to the explorer? I think those would make it much easier for more miners to try Q-BTC.

Would also be interesting to know if there are any plans for Discord/Telegram or some other place for the community. At the moment it still seems pretty quiet outside this thread and GitHub.

Keep up the interesting work and greeting from Finland

[qbtc-core]

Hi Larppa,

Thanks for mining and contributing hashing power from Finland. Good to see the network steadily building up.

v2.1.0 has been running reliably despite the recent hashrate swings. I don't plan on making unnecessary changes to the base consensus unless a critical bug shows up. My main focus right now is researching Layer 2 scaling and stateless verification, as outlined in Chapter 6 of the paper.

Regarding pools and explorers, the standard RPC interfaces are already in place, so anyone interested is completely free to build third-party pool software or better web tools on top of them.

As for Discord or Telegram, I don't plan to manage any community channels myself since I need to keep my focus entirely on development. That said, if you or anyone else in the community would like to set one up and take the lead on it, you're more than welcome to do so. I'll continue to keep technical discussions open here and on GitHub.

-J
Q-BTC Core

[qbtc-core]

Also, are there any plans for a pool/Stratum support or improvements to the explorer? I think those would make it much easier for more miners to try Q-BTC.

Hi Larppa,

Regarding the explorer improvements, I have deployed an update to the existing web explorer today as the network passed block height 18,100.

URL: https://explorer.qbtc-core.org

New features added in this deployment:
1. Web Wallet Interface: A seamless frontend to the node's RPC. Users can generate an ML-DSA-65 wallet (encrypted securely on the host node) and broadcast transactions directly from the browser.
2. Faucet: Distributes 5 QBTC to facilitate early on-chain activity. This endpoint is rate-limited to one claim per IP address per 24-hour window to prevent mempool spam.

This infrastructure allows developers and users to interact with post-quantum signature verification and dynamic fee mechanisms without compiling the Rust node locally.

-J.
Q-BTC Core

[qbtc-core]

[UPDATE: September 13, 2026 - GUI Miner & Stratum Pool Infrastructure]

Hello everyone, and thank you to @Larppa for the recent inquiry regarding pool support.

I have released the necessary infrastructure to support pooled mining, alongside a graphical client to make network participation easier for standard users. To ensure the codebase remains maintainable and modular, the project is now organized into three separate repositories:

1. Q-BTC Desktop Miner
Repository: https://github.com/Q-Jack-core/qbtc-desktop
A graphical client written in Rust and Tauri. It is designed to handle the underlying stratum connections and hashing without requiring manual terminal configuration. Pre-compiled binaries are available for macOS and Windows. You only need to provide your receiving address to begin.

2. Q-BTC Stratum Pool
Repository: https://github.com/Q-Jack-core/qbtc-stratum-pool
The reference implementation of the Q-BTC Stratum protocol. For those with available server capacity, this allows you to operate an independent pool, aggregate hash power, and distribute block rewards according to the network consensus.

3. Q-BTC Core Node
Repository: https://github.com/Q-Jack-core/quantum-btc
The foundational L1 node implementing the ML-DSA-65 post-quantum signature scheme. This remains essential for users who prefer to independently audit the ledger, run a full node, or solo mine directly from the source.

A robust, decentralized network relies on a wide distribution of nodes and hash power. I hope these new tools make it more practical for anyone with spare compute cycles to participate and secure the chain.

Please let me know if you encounter any bugs or have suggestions for improvement.

-J.
Q-BTC Core

Hello,

I would like to start writing some content about your project QBTC for my website. If you're interested, please visit https://hashpower.site/list-your-coin/ and share some basic information with me to get started.

Thanks!

admin@hashpower.site

Hello, and thank you for your interest in Q-BTC.

You can find all the necessary technical details and our Genesis Whitepaper on our GitHub repository. Additionally, our live network status and blockchain data can be monitored directly through our official explorer:
https://explorer.qbtc-core.org

Our mainnet has recently passed the 20,000 blocks milestone. Anyone interested in the project is welcome to join our official Telegram community to connect with the Genesis Miners:
https://t.me/qbtc_genesis

[qbtc-core]

[DEVELOPER UPDATE: September 15, 2026 - Decentralization & Performance Bottlenecks]

The network is stable past Block 20,000. Our official reference Stratum pool (port 3334) and automated payout daemon are running perfectly, and the GUI miner connects to it seamlessly.

However, a healthy PoW network cannot rely on a single official pool. I am shifting my focus back to core protocol optimizations. There are two open frontiers for the community right now:

1. Pool Decentralization & Web UI (The Free Market):
The Stratum pool source code is fully open. I encourage node operators to deploy their own competing pools. Furthermore, we currently lack a commercial-grade web dashboard (for miners to track worker hashrate, graphs, and payouts). The first developer to build a robust open-source pool frontend, or launch a reliable third-party pool, will naturally capture a massive share of the incoming hashrate and the pool fees that come with it.

2. ML-DSA-65 AVX-512 Optimization (Nerd Sniping):
While our pure Rust implementation works perfectly for constant-time execution, I am hitting a performance wall with vectorization (SIMD / AVX-512) during matrix multiplications. If any low-level C/Rust devs want to tear apart the hashing logic and show me a more elegant memory-isolation solution for AVX-512, the codebase is completely open.

Code & Architecture: https://github.com/Q-Jack-core/quantum-btc
Technical Discussion (Telegram): https://t.me/qbtc_genesis

Let's see what this community can build.

-J.

[qbtc-core]

[UPDATE: Block 21,900+ Reached & v2.3.1 Node Upgrade]

Hey everyone, just dropping a quick update now that we've pushed past block 21,900.

The network is running super smooth right now. The ML-DSA-65 post-quantum signatures are working flawlessly on-chain, and the ASERT difficulty adjustment is handling hashrate spikes exactly as intended.

A quick note for our early miners: We had a successful network upgrade at block 21,500. If you are occasionally seeing "orphan" blocks in your console, it likely means you are still running the older pre-fork code. Please make sure to update to the latest v2.3.1 to stay synced and ensure your hashes count!

If you've been waiting on the sidelines, now is a great time to jump in. We built qbtc-desktop to make running a node and mining as straightforward as possible—no specialized mining hardware needed, you can just hash away on your everyday machine.

• GitHub (Core Node v2.3.1): https://github.com/Q-Jack-core/quantum-btc
• GitHub (Desktop GUI Miner): https://github.com/Q-Jack-core/qbtc-desktop
• Web Explorer: https://explorer.qbtc-core.org
• Official Telegram: https://t.me/qbtc_genesis

Hop into Telegram if you need any help setting up your miners. Cheers!

[BitcoinQPoW]

Independent Q-BTC Field Test — Mining, Core v2.5.0 & Node Recovery

Hi everyone,

I've been independently testing Q-BTC on two ordinary computers over the last few weeks.

Rather than looking only at specifications, I wanted to see what actually happens when the software is installed, upgraded, mined and recovered on the live network.

Machine #1 — Solo mining

Q-BTC Core v2.5.0
13,600.39 QBTC confirmed on-chain
450 QBTC coinbase locked/maturing at the time of the test

The node upgraded successfully and returned to normal mining operation.

Machine #2 — Node synchronization & recovery

The second machine developed persistent synchronization problems.

Instead of hiding the failure, I treated it as part of the test.

The wallet/keystore was preserved, the old local chain state was isolated, and the node was rebuilt from a fresh chain database.

Result:

- 23,000+ blocks cryptographically verified during the rebuild
- node successfully resynchronized with the live network
- original wallet preserved
- 150 QBTC confirmed on-chain after recovery

So far the most interesting part of testing Q-BTC hasn't been that everything worked perfectly — because it didn't.

It's that we've been able to observe how the software behaves during mining, upgrades, synchronization problems and recovery.

I'm documenting the field tests publicly here:

https://x.com/BitcoinQPoW

No price predictions and no investment claims — just independent testing of emerging post-quantum Proof-of-Work infrastructure.

I'd also be interested in comparing experiences with anyone running Q-BTC or other post-quantum PoW nodes.

Run it. Measure it. Report it.

[paulmbcufc]

Hey

I created a web wallet. I got my address and seedphrase.

I don't see how to open the web wallet again. Only create new wallet is there.

how?