Pre-testnet development preview

Public network, benchmarks and independent audit not yet available.

MaturityPrivate previewNo public networkNot auditedStatus

STANDARD_WORKSPACE

MATURITY: PRIVATE PREVIEW
NETWORK: NO PUBLIC NETWORK
IMPLEMENTATION: INTERNAL
VALIDATION: IN PROGRESS
AUDIT: NOT COMPLETED
LAST REVIEWED: 2026-09-07

What this page claims

Describes intended protocol architecture and builder-facing procedures for a pre-testnet Layer 1.
References NIST PQC standards (FIPS 203/204/205) as algorithm families — not product certifications.
Points to portal surfaces (security profile, status, explore) for maturity detail.

What this page does not claim

Does not claim a live public network, mainnet, or audited production release.
Does not claim NIST/FIPS product validation or completed independent security audit.
Does not publish reproducible public TPS benchmarks on this portal.

Technical_Record_v4.2

ID: 0xGHOST-

Consensus Overview

Post-quantum BlockDAG consensus — Mysticeti adaptation, not stock Mysticeti. Multi-zone scaling via QronMesh.

Zeqron does not run unmodified upstream Mysticeti. Consensus is a post-quantum adaptation of Mysticeti-style uncertified DAG BFT, specified in RFC-CONSENSUS-001 (ML-DSA-87 signatures instead of BLS12-381 aggregation).

Stack (honest naming)

| Layer | Name | Role | Status | | :--- | :--- | :--- | :--- | | Ordering / BFT | Mysticeti PQ adaptation | BlockDAG commit path without classical BLS aggregates | Internal validation | | Zone / multi-graph scaling | QronMesh | Split load across zones / graphs beyond a single validator set ceiling | Architecture + internal crates | | Related RFC names | QronCord / zone graphs | Protocol parameters and zone operation (see RFC-CONSENSUS-002) | Spec / implementation in progress |

Older site copy used the label “Ghost-Sync”. That name is not the protocol’s canonical designation in masters/RFCs and should not be treated as a separate consensus product.

What builders should understand

::Foundation: DAG BFT inspired by Mysticeti, modified for PQ signatures and Zeqron integration.
::Not a claim of identity: Saying “Mysticeti” alone would overstate upstream equivalence.
::Scale story: Single-zone limits are addressed by QronMesh, not by inventing infinite TPS on one graph.
::Public network: Pre-testnet — no live public finality metrics on this portal.

Further reading

::Protocol RFCs in the repository (RFC-CONSENSUS-001, RFC-CONSENSUS-002)
::Crypto profile: ML-DSA-87 (sign) · ML-KEM-1024 (KEM) · optional SLH-DSA

Documentation // Development preview — naming aligned to RFCs

Was this directive helpful?

Feedback controls are a preview and do not submit data yet.

PREVIOUS_HANDBOOKSDK NEXT_DIRECTIVEBlockDAG ordering