EncrypiaBrief companion v0.2September 2026Public · Pre-testnet

07 · Research · Whitepaper

Security-posture note — status on every strong claim.

Treat this reading as a public security-posture note, not a paper. Encrypia coordinates Zeqron. Canonical brief v0.2. September 2026. Architecture · Pre-testnet. Every strong claim below carries a label: design, code, or unpublished. If a citation drops the label, it is no longer this note.

Below are two real monorepo excerpts: FinalityLevel (Included → FastFinal → OrderedFinal → Spendable → Settled) and ConformanceLevel (ZAXON agent conformance levels). Status: code · design · no public network measurement. Not a TPS figure — claim states and bounds.

Status · design and code: FIPS 203 (ML-KEM) names key encapsulation; FIPS 204 (ML-DSA) names primary signatures; FIPS 205 (SLH-DSA) names long-lived hash-based signatures. Each standard’s role in the public stack is declared. Status · unpublished: parameter sets, key sizes, and KAT vectors on this page.

Status · design (with code in the monorepo): proofs are STARK-class with transparent setup — no pairing-trusted ceremony as the long-term story; use configurable per zone. Status · unpublished: FRI query counts, field choice, hash-family widths, soundness-bit marketing tables.

Status · design hypothesis: consensus orders commitments on a DAG with a BFT-style committee and post-quantum signatures; the failure threshold discussed in design is the classical less-than-one-third. Named lineage: Mysticeti family (Babel et al., arXiv:2310.14821). Zeqron is a PQ adaptation with QronGraph — not unmodified upstream Mysticeti. Upstream guarantees, throughput, and latency do not transfer automatically to a Zeqron network. Status · unpublished here: a full Encrypia formal paper (reductions, games, lemmas).

What changes under a PQ adaptation — without pasting paper figures. ML-DSA signatures are much larger than Ed25519/BLS: the design must assume heavier blocks and certificates on the DAG, not the upstream paper’s WAN latency profile. QronGraph adds semantic ordering of commitments on top of that family; that is Encrypia work, not an arXiv copy-paste. Status: design hypothesis + family code · not a Zeqron network measurement.

Evidence classes, in prose — the brief’s table. (A) Observed network: published throughput/latency under real load. (B) Lab / POC / simulation: experiment under stated assumptions. (C) Theoretical ceiling: analytical bound. Zeqron has no public row (A) as of September 2026. That is why there is no Zeqron column beside Bitcoin/Ethereum “observed.” An internal experiment, if one exists, is not pasted here as an observed network.

How to cite this page: as Encrypia’s public posture aligned with brief v0.2, preserving claim-status labels, with the Mysticeti lineage labeled as a design reference. How not to cite it: as an Encrypia peer-reviewed paper; as a reproducible parameter appendix; as evidence of measured public-network performance; as proof that arXiv:2310.14821 lemmas hold unmodified for Zeqron.

PQ adaptation · design consequences

Hypothesis · no Zeqron network measurement

  1. 01

    Heavier signatures

    ML-DSA ≫ Ed25519/BLS in size. Design assumes costlier certificates and vertices on the DAG.

    Not — Do not paste upstream WAN latency from the paper.

  2. 02

    Costlier verification

    A BFT-style committee pays more CPU per signed message. Cost profile is not the classical paper’s.

    Not — Do not invent Zeqron TPS from the arXiv.

  3. 03

    QronGraph

    Semantic ordering of commitments on top of the DAG-BFT lineage. Encrypia work — not a paper copy-paste.

    Not — Do not assert upstream lemmas without adaptation.

  4. 04

    Evidence

    Today: design + family code. No public Zeqron observed row (class A).

    Not — Lab/POC ≠ observed network.

Citing Mysticeti (arXiv:2310.14821) names lineage. It does not transfer upstream throughput, latency, or lemmas to a Zeqron network.

Cryptographic stack · PQ from genesis

Public brief v0.2 §4 · NIST FIPS

FIPS 203ML-KEMKey exchange
FIPS 204ML-DSASignatures (hot path)
FIPS 205SLH-DSASignatures (cold / anchor)

Not a later migration plan. All three families are in the design from the start.

References · design lineage

Posture note · not a Zeqron paper

  1. [1]

    Babel, K. et al. Mysticeti: Reaching the Limits of Latency with Uncertified DAGs. arXiv:2310.14821, 2023/2024.

    DAG-BFT lineage (upstream). Status: design reference · not a Zeqron network measurement.

  2. [2]

    NIST. FIPS 203 (ML-KEM), FIPS 204 (ML-DSA), FIPS 205 (SLH-DSA).

    PQ primitives named in the public stack. Status: design and code · fine parameters unpublished here.

  3. [3]

    Encrypia. ZEQRON — Public Technical Brief v0.2. September 2026.

    Canonical public text. If this page and the brief diverge, the brief wins.

Citing the lineage does not transfer upstream throughput, latency, or lemmas to a Zeqron network. The PQ adaptation and QronGraph are Encrypia design; upstream paper guarantees are not assumed to transfer automatically.

Finality levels (excerpt)

zeqron-consensus · FinalityLevel · DRAFT §2 R20

code · DAG finality design · no public network measurement

rust
pub enum FinalityLevel {
    Included,      // in a vertex, proof verified
    FastFinal,     // fast path when no nullifier conflict
    OrderedFinal,  // causal order resolves a conflict
    Spendable,     // epoch sealed
    Settled,       // further epoch confirmation (zone-configurable)
}

Claim finality is not a TPS figure. These are design states on the DAG. Without a published network, none of these levels is a service measurement.

ZAXON conformance levels (names)

zeqron-zaxon · ConformanceLevel

code · framework · amounts unpublished

rust
pub enum ConformanceLevel {
    L0, // unconstrained — development / tests
    L1, // bounded — basic production agents
    L2, // attested — stronger controls
    L3, // certified — highest declared tier
}

Framework names only. Bonds, insurance, and discounts are not asserted as live market facts.

Claims with status

FIPS 203 / 204 / 205

Named role in the stack. Status: design and code. Concrete instantiation: unpublished.

STARK · transparent setup

Proof class and absence of trusted setup as the long story. Status: design and code. Reproducible parameters: unpublished.

DAG + BFT <1/3 · Mysticeti lineage

Ordering model and threshold. Reference: Babel et al., arXiv:2310.14821. PQ adaptation + QronGraph = Encrypia design. Status: design hypothesis (consensus-family code in the monorepo). Zeqron network measurement: none. Automatic transfer of upstream lemmas: no.

Evidence

No public observed-network row. Lab ≠ observed. Theoretical ≠ deployed. Upstream paper ≠ Zeqron network.

What citing the lineage changes

Useful for

Naming where the DAG-BFT family the design adapts comes from, and giving a reviewer a first paper to read.

Not useful for

Pasting 0.5s / 200k TPS or other paper figures next to Zeqron. That column would still be false even though the arXiv exists.

PQ adaptation (design)

ML-DSA enlarges signatures versus classical curves: the DAG must live with heavier certificates. QronGraph orders semantic commitments on top. Neither concrete signature sizes nor the paper’s WAN latency are asserted here as Zeqron network facts.

What this reading is not

  • A paper, or a substitute for peer review.
  • A latency or throughput table presented as Zeqron network fact.
  • The parameter appendix the brief leaves out on purpose.
  • A claim that Mysticeti lemmas hold unmodified for Zeqron.
Public brief v0.2ZEQRON-WHITEPAPER-PUBLIC-v0.2.md

See also

Companion reading to Public Technical Brief v0.2. If this page and the brief diverge, the brief wins. The long master stays internal. Not an instrument offering and not legal advice.