Technology

How QSDM works.

QSDM is the pilot network (pre-mainnet) for the CELL coin. Wallets, transactions, task actions and consensus votes are signed with ML-DSA-87, a post-quantum signature scheme. Every transfer names earlier committed transfers as its parents (Proof-of-Entanglement). Today one block producer runs the chain; independent validators are the next step. This page explains each part in plain words, with live values from the public API.

Live data: loading…

Key specs

Supply cap 90,000,000 CELL, fixed
Emitted — — of the cap
Block reward 3.56490987 CELL per block · epoch 0
Target block time 10 s protocol target
Next halving 12,623,041 block height
Chain tip — current block height

Source: GET /api/v1/status (tokenomics, consensus_auth, mining) · Network status

The parts

Each card says what the rule is, who it affects and where to check it.

Post-quantum signatures

QSDM signs with ML-DSA-87, the highest security level of the NIST FIPS 204 standard. ML-DSA is a lattice-based scheme designed to resist attacks by future quantum computers.

Wallets
ML-DSA-87 key pair
Transactions
ML-DSA-87
Task actions
ML-DSA-87
Consensus votes
ML-DSA-87
Address
SHA-256 of the public key

Keys are made and kept on your device. Hive and the web wallet send only signed messages.

Proof-of-Entanglement

Every CELL transfer must name a few earlier transfers that are already committed to the chain, its parent cells. This links each new transfer to recent history. A transfer that names no committed parents is refused (HTTP 422).

You do not pick parents yourself. Hive 1.4.22 and the web wallet ask GET /chain/parents just before signing.

Enforced from
block 816,600
Parents per transfer
2 to 10
Look-back window
8,640 blocks
Status
checking

Signed consensus

Since block 827,000 every consensus vote and message must carry a valid ML-DSA signature. Unsigned consensus traffic is refused. This protects block agreement from forged votes.

Today there is one block producer, so this rule is in force but not yet tested by many independent validators.

Enforced from
block 827,000
Unsigned traffic
refused
Status
checking

Mining model

Mining is NVIDIA GPU only. A miner proves its GPU with NVIDIA attestation, enrolls the node with a signed enrollment and posts a bond. Mining is open to enrolled QSDM Hive miners in 7-day canary windows (168 hours each), with caps per owner per 24-hour epoch.

Protocol
v2
Attestation
nvidia-cc-v1, nvidia-hmac-v1
Enrollment
qsdm/enroll/v2 (signed)
Bond
10 CELL per node, can be paid from rewards

Mining guide · Download Hive 1.4.22

Edge Pool: paid resource work

The Edge Pool pays for CPU, GPU and RAM tasks. It is in an operator-only test and is not yet open to other miners.

Since block 833,800 the paid edge tasks settle only through an authorized settlement relay (relay-only rule). The built-in system task IDs can only be registered by the project's owner key.

Relay-only from
block 833,800
Status
checking

Who makes the blocks

One block producer, the project's own node, makes every block. A backup node follows the chain. There are no independent validators yet. The design admits validators without a GPU; mining and block production are separate roles.

Producer role
—
Peers
—
Node release
—

Live status · Validators

Consensus rules in force

Rules switch on at a fixed block height. The status column is read live from consensus_auth in /status.

RuleActivation heightWent live (UTC)Status
Signed task actions (ML-DSA) 625,000 before October 2026 checking
Transaction content root 625,000 before October 2026 checking
Proof-of-Entanglement (transfers must name committed parent cells) 816,600 2026-10-11 13:18 checking
Signed consensus (unsigned votes and messages refused) 827,000 2026-10-12 18:11 checking
Relay-only paid edge tasks 833,800 2026-10-13 13:21 checking

What changed and what you need to do: Network upgrades.

Not done yet

QSDM is a pilot. These are the open items, stated plainly.

  • One block producerThe project's node produces every block. If it stops, the chain stops until it is back. A backup node follows the chain but does not produce blocks.
  • No independent validatorsIndependent validators are the next step. Onboarding has not started publicly.
  • Ed25519 retirement pendingRetiring the older Ed25519 signatures is planned, not done. The generic peer-to-peer transaction-gossip code still accepts Ed25519, but the producer runs without transaction gossip intake, so no Ed25519 transaction can reach the live chain today. Wallets, task actions and consensus use ML-DSA.
  • No external security auditNo independent firm has audited QSDM. The public audit page is a self-assessment checklist. There is no bug bounty programme; report security issues as described in security.txt.
  • Pilot dataTreat balances and history as pilot data until the genesis, multisig and independent-audit milestones are complete.