September 2026 · EncrypiaPublic Technical Brief v0.2 · Architecture · Pre-testnet

Whitepaper

Zeqron
whitepaper.

This site is the companion to the public technical brief: a semantic coordination protocol, post-quantum from genesis, with agents (ZAXON) and industrial assets (ZNA) in the design. It is not another token L1. It does not report a measured public network.

The Markdown v0.2 file is canonical. If a reading on this site and the brief diverge, the brief wins. The long master stays internal.

Architecture · four layers

Public brief v0.2 §3 · design

  1. AApplicationSemantic Zones, domain modules, oracles
  2. BCoordinationContracts, STARK proofs, semantic bridges
  3. CConsensusQronGraph (DAG) + BFT-style committee
  4. DIdentityPQ DIDs, verifiable credentials, reputation

One job per layer. Conceptual flow: Applications → Coordination → Consensus; Identity authenticates throughout.

Claim labels

Brief v0.2 · companion

  • design

    Specified as protocol intent.

    E.g. — PoSS = stake + observable service.

  • code

    A type or family exists in the monorepo.

    E.g. — ContractState, AgentIdentity, FinalityLevel.

  • unpublished

    Withheld on purpose (NDA / phase).

    E.g. — FRI, wire, yield, ports, jurisdiction.

If a citation drops the label, it is no longer this publication. Inventing a metric without a phase is a different class of error.

Whitepaper readings

Seven entries into the same protocol. Each opens as a summary, a detail, and a longer argument — prose, not a title index. The Markdown brief is the text that governs.

  1. 00Canonical briefThe Markdown that governs: thesis, status, Appendix B, anti-claim.
  2. 01PrimerThe problem, a walked agreement, and what this publication does not assert.
  3. 02InvestorsCapital thesis, what diligence can inspect today, and what this publication refuses to say.
  4. 03DevelopersLayers, the path of an agreement, and which software families exist without a public network.
  5. 04OperatorsPoSS as design, the no-public-onboarding decision, and the future order of a runbook.
  6. 05EnterpriseInstitutional fit, when not to choose Zeqron, and what to discuss under agreement.
  7. 06LegalAuthor, document hierarchy, and scope: not advice and not an offering.
  8. 07ResearchFIPS, STARK, and the consensus failure model — with a status on each claim.