MAINNET PREVIEW · NIST FIPS 204 · NVIDIA-LOCKED

Post-quantum distributed trust,
NVIDIA GPU-attested by design.

QSDM is the Quantum-Secure Dynamic Mesh Ledger — a non-AI, hardware-agnostic electronic-cash and smart-contract fabric with a native coin, Cell (CELL). ML-DSA-87 post-quantum signatures, a dynamic 2D/3D mesh topology, Proof-of-Entanglement BFT consensus on CPU-only validators, and an additive NVIDIA-locked GPU mining layer that mints Cell from attested proofs.

Get a Wallet Mine Cell Run a Validator Open Dashboard

Signature scheme

ML-DSA-87

NIST FIPS 204 · 256-bit PQ security

Consensus

PoE + BFT

CPU-only validators · no proof-of-work

Native coin

Cell (CELL)

100 M cap · 4-year halvings · 0% pre-mine

Wallet

Self-custody

Browser + CLI · keys never leave your device

Use QSDM

Three ways to use it today.

You don't need a server to start. A QSDM wallet runs in your browser; mining runs on a home NVIDIA GPU; a validator runs on a modest VPS. Each path is independent and production-usable on its own.

Wallet · Browser + CLI · Self-custody

Hold & sign with ML-DSA-87

The wallet at qsdm.tech/wallet.html generates a quantum-secure keypair, encrypts the private key with your passphrase, and lets you sign or verify any message — entirely in your browser. The companion qsdmcli wallet subcommand produces byte-identical keystores offline.

PBKDF2-HMAC-SHA-256 (600 000 iterations) + AES-256-GCM
Browser WASM module reuses cloudflare/circl — same code as the validator
No server keeps your key; nothing about a generated keypair leaves your tab

Open Wallet Threat model

Miner · NVIDIA-locked · v2 only

Mine Cell on your GPU

Mining mints Cell (CELL) from attested NVIDIA proofs. The live mainnet runs v2 only — the v1 CPU path is rejected at consensus (ReasonBadVersion) and the v1 reference binary is no longer a public release artefact. Every accepted proof carries an NVIDIA attestation: nvidia-cc-v1 on Hopper / Blackwell datacenter GPUs with Confidential Compute, or nvidia-hmac-v1 on consumer RTX cards with a registered (node_id, gpu_uuid, hmac_key) tuple and a 10 CELL bond.

Hardware: any NVIDIA GPU you control + a host clock within 60 s of UTC
Tooling: qsdmminer-console --protocol=v2 — setup wizard, live panel, v2 client
On-chain: qsdmcli enroll bonds 10 CELL to your node_id
Funding caveat: v0.3.2 has no public faucet yet — new operators need a transfer from an existing CELL holder. See Appendix B.
Forged or replayed proofs are slashable (qsdm/slash/v1)
Halving emission, 90 M lifetime mining cap, 0 % pre-mine

Download Miner Quick-start (v2)

Validator · CPU-only · VPS-class

Run a validator

Validators are the consensus tier. They run Proof-of-Entanglement + BFT on CPU-only VPS-class hardware and earn transaction fees. No GPU required. NVIDIA NGC attestation is available as an opt-in transparency signal, but it never gates consensus.

4–8 vCPU, 8–16 GB RAM, 200 GB NVMe, 1 Gbps symmetric
Ubuntu 24.04+ and Windows 10+ today; macOS in development
libp2p + GossipSub · SQLite + Zstd → ScyllaDB migration path
Dashboard, Prometheus, audit reports, signed releases

Validator quick-start Live validators

Build on QSDM

Five ways in. One protocol.

Every QSDM surface is open. Pick the seam that fits your stack — the wire format, the public REST API, and the on-chain envelope are identical across all of them.

JavaScript SDK · npm

Type-safe ESM/CJS client. Wallet, transactions, mining-API helpers, signed status fetch.

npm install qsdm-sdk
# import { QSDMClient } from 'qsdm-sdk'

qsdm-sdk@0.3.0 · MIT · SLSA v1 provenance · npmjs.com/package/qsdm-sdk

Go SDK

Feature-equivalent Go client. Used by qsdmminer-console and qsdmcli.

go get github.com/blackbeardONE/QSDM/sdk/go
// client, _ := qsdm.NewClient("https://api.qsdm.tech")

tagged with the core repo · v0.3.1

Browser WASM Wallet

Drop-in wallet.wasm + wasm_exec.js. Stateless keypair / sign / verify.

<script src="/wasm_exec.js"></script>
<script src="/wallet.js"></script>
// qsdm_wallet_generate(), qsdm_wallet_sign(...)

~3.2 MB · pure Go-WASM · no CGO · ML-DSA-87 via circl

Public REST API

Health, status, mining challenge, enrollment / slashing reads + writes, transaction submit.

curl https://api.qsdm.tech/api/v1/health
curl https://api.qsdm.tech/api/v1/status

JWT auth · TLS at the edge · paginated cursors · OpenAPI in repo

Container images · GHCR

Validator, full-node, and miner images. Cosign-signed · SPDX SBOM attached as attestation.

docker pull ghcr.io/blackbeardone/qsdm-validator:0.3.1
docker pull ghcr.io/blackbeardone/qsdm-miner:0.3.1

Sigstore keyless · verify with cosign verify

Smart contracts · WASM

Native WASM contract runtime. qsdm/enroll/v1 and qsdm/slash/v1 live.

// Wallet, validator, and mining contracts
// see source/contracts/ in the repo

Deterministic gas · pinned imports · canonical-codec txs

Why it matters

Post-quantum, hardware-bound, non-AI.

QSDM combines three properties that no other production ledger ships together: lattice-based signatures that survive a quantum adversary, GPU-anchored mining identity, and Proof-of-Entanglement consensus that doesn't burn watts to order transactions.

Post-quantum

Harvest-now-decrypt-later safe

ML-DSA-87 (NIST FIPS 204) keeps today's signatures verifiable after ECDSA and RSA are broken.

Hardware-bound

Sybil-resistant by silicon

Miners attest with an NVIDIA-locked proof bound to an enrolled operator key. Cloning costs real money — the bond burns on forgery.

Throughput

Mesh, not a chain

Cells can have multiple parents. Submeshes route by fee and geotag. No single block interval throttles the network.

Energy

No PoW in consensus

PoE uses cryptographic linkage, not brute hashing. The GPU mining layer is additive and can halt with zero impact on chain liveness.

Non-AI

Deterministic governance

Rule-based quarantines, snapshot voting, manual submesh templates. Auditable, reproducible, AI-free.

Open

libp2p + WASM + REST

GossipSub transport, WebAssembly contracts, REST + Prometheus endpoints. Nothing proprietary at the seams.

Operable

Single binary · two platforms

One Go binary. Ubuntu 24.04+ and Windows 10+ today; macOS in development. Systemd + Caddy deploy in under an hour.

Auditable

Metrics + signed releases

Prometheus scrape, audit reports with severity gates, cosign-signed binaries + container images, SLSA-attested npm tarball.

Comparison

QSDM vs. traditional blockchains and DAGs.

Like-for-like against representative production systems. Values reflect each system's default mainnet configuration, not maximal lab setups.

Dimension	QSDM	Bitcoin · PoW	Ethereum · PoS	IOTA / Hedera · DAG
Data structure	Dynamic 2D/3D mesh, multi-parent cells	Linear chain	Linear chain	Directed acyclic graph
Consensus	PoE + BFT · CPU-only validators	Proof-of-Work	Proof-of-Stake (Gasper)	Tangle / Hashgraph
Mining / emission	Additive GPU track · NVIDIA-locked · never orders blocks	Mining is consensus	No mining; staking = consensus	No mining; DAG voting
Quantum-safe signatures	✓ ML-DSA-87 (FIPS 204, 256-bit)	✗ ECDSA (secp256k1)	✗ BLS12-381 / ECDSA	◐ varies; mostly classical
GPU-attested identity	✓ NVIDIA CC + HMAC, on-chain enrollment	✗	✗	✗
Self-custody wallet	✓ Browser WASM + CLI, no server custody	◐ via third-party	◐ via third-party	◐ via third-party
Energy profile	Low; CPU validators, GPU only for emission	Very high (hash mining)	Low (staking)	Low
Finality	PoE + finality gadget, reorg-bounded	Probabilistic (6 blocks)	Epoch-based (~12–15 min)	Varies; often probabilistic
AI/ML dependencies	None — rule-based governance	None	None (core); apps vary	Varies
Smart contracts	WASM (wallet, enrollment, slashing)	Script (non-Turing)	EVM	EVM (Hedera), limited (IOTA)
Deployment footprint	1 Go binary · Linux / Windows	Full node required	Execution + consensus client	Protocol-specific tooling

Figures shown are representative of default mainnet configurations. QSDM quantum-safe primitives are based on NIST FIPS 204 (ML-DSA), standardized in 2024.

Roadmap

Three phases shipped. One protocol live.

Each phase is deliverable on its own. All three product phases are in production today; the v2 NVIDIA-locked mining protocol and the self-custody wallet landed in 2026 H1.

2D Mesh launch

Stable 2D mesh, manual bootstrapping, Proof-of-Entanglement, ML-DSA-87, SQLite + Zstd.

libp2p + GossipSub networking
Batch signing (10–100× single-tx)
Operator dashboard · Caddy · UFW

Shipped

Scalability & SDKs

Dynamic submeshes, WASM contract SDK, ScyllaDB migration path, JavaScript + Go SDKs.

Fee + geotag submesh routing
WASM wallet & validator integration
SQLite → ScyllaDB migrate with dry-run

Shipped

3D Mesh & v2 mining

3D mesh validation, NVIDIA-locked mining, on-chain enrollment + slashing, reputation healing.

v2 attestation (CC + HMAC) end-to-end
On-chain enrollment + 2-of-3 slashers live
Self-custody wallet (browser + CLI)

Live

Current release: v0.3.1 — ML-DSA-87 consensus, v2 NVIDIA-locked mining with active forged-attestation and double-mining slashers, qsdm-sdk@0.3.0 on npm, GHCR container images at :0.3.1, and the self-custody wallet. Detail in RELEASE_NOTES_v0.3.0.md and on the GitHub releases page.

Under the hood

How the pieces fit.

A single Go binary terminates consensus, storage, and the public API. Caddy fronts TLS; libp2p is the peer transport. The browser wallet talks to the same REST surface as the SDKs.

Post-quantum distributed trust, NVIDIA GPU-attested by design.

Three ways to use it today.

Hold & sign with ML-DSA-87

Mine Cell on your GPU

Run a validator

Five ways in. One protocol.

JavaScript SDK · npm

Go SDK

Browser WASM Wallet

Public REST API

Container images · GHCR

Smart contracts · WASM

Post-quantum, hardware-bound, non-AI.

Harvest-now-decrypt-later safe

Sybil-resistant by silicon

Mesh, not a chain

No PoW in consensus

Deterministic governance

libp2p + WASM + REST

Single binary · two platforms

Metrics + signed releases

QSDM vs. traditional blockchains and DAGs.

Three phases shipped. One protocol live.

2D Mesh launch

Scalability & SDKs

3D Mesh & v2 mining

How the pieces fit.

Post-quantum distributed trust,
NVIDIA GPU-attested by design.