QSDM

QSDM (Quantum-Secure Dynamic Mesh ledger) is a ledger with post-quantum (ML-DSA-87) wallet signatures and a two-tier node model — CPU-only validators are designed to run the PoE + BFT consensus, and miners run an additive, Mesh3D-tied Proof-of-Work that mints the native coin, Cell (CELL). Consumers use QSDM Hive (Windows/Linux) for wallets, signed tasks, NVIDIA mining, and Mother Hive edge pools. Operators use Core plus optional home gateway, tray monitor, and attestation sidecars.

Wallet transactions are signed with ML-DSA-87 (NIST FIPS 204, via Cloudflare CIRCL) — the standardised post-quantum signature scheme. It is designed so that signatures made today stay unforgeable even against a future cryptographically relevant quantum computer.

Latest tagged ledger release: v0.4.3. Public site: qsdm.tech.

Network status

QSDM is a public pilot network (pre-mainnet). Today:

• Blocks come from a single block producer during recovery; a backup node follows the chain. Live peer count and consensus flags are published at /api/v1/status and qsdm.tech/network.html.
• CELL wallet transactions (Hive, web wallet, qsdmcli) are signed with ML-DSA-87. The generic peer-to-peer transaction verifier still also accepts Ed25519 signatures.
• Signed consensus messages are supported in the node but not yet active (signed_consensus_active: false).
• Proof-of-Entanglement: every node checks each transfer's ML-DSA-87 signature under the sender's own key. The parent rules (each transfer names committed earlier transactions) are enforced on the public pilot from block 816,600 (11 October 2026; consensus_auth.poe_active in /api/v1/status). See PROOF_OF_ENTANGLEMENT.md.
• GPU mining (NVIDIA today) is open to enrolled QSDM Hive miners.
• Consensus signing, independent validators, the Tier 0 treasury multisig, an official genesis manifest and an independent external audit are on the roadmap. Until those gates close, treat the chain as a pilot, not a mainnet (see TREASURY_POLICY.md §9).
• Max supply is 90,000,000 CELL, all from mining. A 10,000,000 CELL genesis treasury is a mainnet proposal; it is not built and is not part of the current chain.

What is running (October 2026)

• Core: release hardened-legacy-20261002-d7ffcd4-hl2, built from this repository's QSDM/source (d7ffcd4 plus the recovery patches and the HL1/HL2 hardened-legacy mining work listed in the changelog). The chain was stopped on 2026-09-22 and restarted on 2026-09-27; public mining reopened on 2026-10-02.
• Mining: NVIDIA GPU miners enrolled through QSDM Hive, in time-boxed public windows with per-owner limits. The node accepts owner-signed (ML-DSA-87 operator_sig) proofs, and each window's configuration decides whether the signature is required.
• Hive: 1.4.21 for Windows and Linux, from qsdm.tech/downloads/hive-v2/. Hive 1.4.21 signs mining proofs with the unlocked Hive wallet automatically. Moving from 1.4.20 (Windows) or 1.4.17 (Linux) is a one-time manual install from the download page.

Rebrand notice. Folder names such as apps/qsdm-landing/ and configuration identifiers (qsdm.* configs, QSDM_* env vars, X-QSDM-* headers) continue to work during the deprecation window. See QSDM/docs/docs/REBRAND_NOTES.md for the full migration table.

Repository layout

Path	What it is
QSDM/	Ledger node — Go implementation (consensus, storage, ML-DSA-87 signatures, wallet/token/mining/governance/bridge APIs). Native coin is Cell (CELL).
QSDM/docs/docs/	User-facing documentation: API reference, mining protocol, node-role split, quickstarts, tokenomics, roadmap.
QSDM/deploy/landing/	Production website served at qsdm.tech (marketing pages, docs SPA, wallet WASM, explorer, audit, trust).
apps/	Products and sidecars that use the node but are not required to run the core ledger.
apps/qsdm-hive/	QSDM Hive desktop client (CELL wallets, tasks, mining, edge).
apps/qsdm-edge-agent/	Edge Agent / Relay / Edge Control utilities for Mother Hive pools.
apps/qsdm-tray-monitor/	Windows tray health monitor for the local home stack.
apps/qsdm-nvidia-ngc/	Optional NVIDIA NGC GPU attestation sidecar — opt-in, per-operator API policy, not a consensus rule. See NVIDIA_LOCK_CONSENSUS_SCOPE.md.
apps/qsdm-landing/	Legacy marketing stub. Prefer QSDM/deploy/landing/ for the live site.

Start here

• Feature summary (current capabilities): QSDM/docs/docs/Feature Summary.md
• Operator wiki (end-to-end): QSDM/docs/docs/OPERATOR_GUIDE.md ⭐ start here if you are new
• Download Hive: qsdm.tech/download.html (Hive 1.4.21 and later: qsdm.tech/downloads/hive-v2/, signed with the v2 release key pinned in QSDM/deploy/release-trust/qsdm-hive-release-key-v2.json)
• Archived documents: QSDM/docs/archive/
• Live bootstrap peers: qsdm.tech/validators.html
• Run a validator (CPU-only): QSDM/docs/docs/VALIDATOR_QUICKSTART.md
• Run a miner (Hive or console; CUDA solver bundled): QSDM/docs/docs/MINER_QUICKSTART.md
• Home gateway (narrow public mining/status): QSDM/docs/docs/HOME_GATEWAY.md
• Edge pool / Mother Hive: QSDM/docs/docs/EDGE_POOL.md
• Run the NGC attestation sidecar: apps/qsdm-nvidia-ngc/QUICKSTART.md
• API reference: QSDM/docs/docs/API_REFERENCE.md and openapi.yaml
• Protocol specs: MINING_PROTOCOL_V2.md, NODE_ROLES.md, CELL_TOKENOMICS.md
• Release notes: CHANGELOG.md
• Code signing policy: CODE_SIGNING_POLICY.md
• Privacy policy: PRIVACY.md
• Security reporting: SECURITY.md

New? The operator wiki answers the three questions every new node operator asks: do I need an NVIDIA GPU, do I need a paid NGC plan, and do I have to sync to your VPS? Spoiler: no, no, and no — but NVIDIA is the first-class mining path today and api.qsdm.tech is the recommended bootstrap peer for Phase 4.

Trust surface (live reference node)

The reference deployment at https://api.qsdm.tech/ publishes endpoints that make coverage legible:

• GET /api/v1/trust/attestations/summary — aggregate attested / total_public ratio across the validator set.
• GET /api/v1/trust/attestations/recent — recent peer attestations with coarse region/GPU-arch metadata only (no PII).
• GET /api/v1/audit/summary and /api/v1/audit/items — public audit checklist.

Consumed by qsdm.tech (/trust.html, /audit.html) and the dashboard. See NVIDIA_LOCK_CONSENSUS_SCOPE.md for why NVIDIA-lock is a transparency signal, not a consensus rule.

License

MIT © 2024-2026 Joedel Lopez Dalioan (Blackbeard).

The ledger node and sidecars are permissively licensed. Vendored third-party dependencies under QSDM/source/wasmer-go-patched/ retain their own licences (see QSDM/source/wasmer-go-patched/LICENSE).

Windows signing

QSDM is preparing an application for free open-source signing through SignPath Foundation. The application is pending, and no artifact may be represented as SignPath-signed until it passes the repository's release gates. See the code signing policy for roles, provenance, approval, verification, and incident-response requirements.