Private pre-testnet

Current validation boundary

Semantic coordination protocol

The Semantic Coordination Network

Zeqron is a coordination protocol where people, organizations and autonomous agents — AI agents, software bots, industrial machines — keep their own state, agree directly, and anchor only the proof. The terms stay with the parties. Verifiable agent identity, native assets and selective disclosure are part of the protocol, on post-quantum signatures from the first version.

Read the whitepaperEvidence Pack →

30-minute technical briefing for protocol teams, researchers, infrastructure partners, and institutional reviewers.

Architecture, current scope, evidence, and validation roadmap.

Illustration · simulated data · no public network

Five parts

  1. Coordination protocol
  2. Post-quantum identity and sessions
  3. Agent policy and execution
  4. Native assets and provenance
  5. Selective disclosure (design)

Why this stack

Three shifts. One substrate.

Three shifts are happening at once. Cryptographic standards are changing. Autonomous systems are increasing transaction volume and policy complexity. Shared execution environments are becoming coordination bottlenecks. Zeqron is a shared coordination protocol designed for that overlap.

Pressure

What breaks first

01

Long-lived systems are beginning migration planning as post-quantum standards move into deployment.

02

Autonomous services may increase transaction frequency, policy complexity, and machine-to-machine settlement requirements.

03

Globally shared execution can create contention as independent workloads compete for the same coordination surface.

How Zeqron coordinates

The architecture in six chapters: a zone, a QronGraph, the QronMesh, agent interfaces, bridges and anchoring, and the whole. Conceptual architecture — not a live network.

  1. 01

    Semantic Zone

    A group of parties that share rules. Their agents act within policy limits, and each action leaves a signed record.

  2. 02

    QronGraph

    Each zone commits a hash of its records to a QronGraph. The contents stay with the parties; only the commitment is ordered.

  3. 03

    QronMesh

    QronGraphs exchange proofs as peers. The destination checks that a claim was included; no central chain sits above them.

  4. 04

    Agents and autonomous systems

    An external system sends a request and gets a receipt back. Authority and policy checks through ZAXON are optional, and orchestration stays outside the protocol.

  5. 05

    External interfaces

    Chain-specific adapters connect other networks, each with an explicit trust boundary. Batch roots can be anchored on a QronGraph.

  6. 06

    The whole

    Semantic Zones inside QronGraphs, and QronGraphs as sovereign peers in the QronMesh.

Trade-offsNot a production ranking

Architectural trade-offs

Design commitments across coordination models — not a generational scoreboard or production ranking.

Zeqron

Model
DAG + zones
Account security
PQ as native design target
Execution
WASM contracts + native assets
Maturity
Private pre-testnet
BitcoinPoW chain
Model
PoW chain
Account security
Classical signatures
Execution
Constrained scripting
Maturity
Production
EthereumGlobal state
Model
Global state
Account security
Classical signatures
Execution
EVM contracts
Maturity
Production
SolanaParallel state
Model
Parallel state
Account security
Classical signatures
Execution
Parallel runtime
Maturity
Production
SuiObject model
Model
Object model
Account security
Classical signatures
Execution
Move / objects
Maturity
Production

Public-chain rows summarize publicly documented designs (approx., 2026). Zeqron maturity is private pre-testnet with protocol libraries.

Post-Quantum Necessity

Gen 1–3 public chains generally rely on ECC, which is vulnerable to Shor's algorithm under a cryptographically relevant quantum computer. Zeqron's protocol libraries combine lattice and hash-based post-quantum primitives (ML-KEM / ML-DSA / SPHINCS+) as the design basis.

Zone scaling path

The two-layer design (L1 Mysticeti-derived ordering + L2 QronCord) targets sub-second finality as a design target. It has not been measured, and no methodology is published yet.

Protocol maturity

Evidence map

What exists in internal protocol libraries today, maturity label, and next control.

Owner of every row: Encrypia LabsLast reviewed: 15 Nov 2026

Internal build

NIST FIPS 203/204 (ML-KEM-1024, ML-DSA-87), SPHINCS+ and a hybrid KEM in protocol libraries · tests / RFCs

Method: Round-trip and size tests; known-answer tests pending

Next control: External cryptographic review

Under validation

Mysticeti-derived DAG BFT + EUTXO patterns across consensus crates · specs and tests

Method: Crate tests + RFCs

Next control: Formal analysis

Internal build

Plonky3-based proving path; transparent proofs, no trusted setup ceremony

Method: Plonky3 path + RFCs

Next control: Public parameters

Internal build

ZAXON: identity, policy, attestation, discovery, reputation, payments, escrow libraries

Method: Libraries + RFCs

Next control: Reproducible demo

Designed

ZNA primitives with experimental STARK circuits in libraries (lineage and aggregate consistency)

Method: Library primitives + RFCs

Next control: Pilot program (after the testnet)

Under validation

QronP2P post-quantum handshake in protocol libraries; QUIC transport with a hybrid key exchange is optional

Method: Integration tests + RFCs

Next control: External review

Public preview pending

Current scope: internal protocol libraries. Public testnet, reproducible benchmarks, and independent audits remain pending.

Method: Editorial boundary review

Next control: Named auditor + public benches

How to read the labels

Specified
: written in the specifications; not implemented end to end.
Designed
: the design is written and reviewed internally; code is partial or absent.
Internal build
: implemented in the protocol libraries and exercised by their own tests.
Under validation
: an internal build being tested internally.

None of these labels means audited, benchmarked or running on a public network.

Readiness gates

Protocol gates

Progress is measured through explicit technical and security gates.

Estimates subject to governance. Mainnet is conditional on security and technical gates.

Internal devnetIn progress

Documented internal exercises and library integration tests.

Closed testnetIn preparation

External validators and multi-region deployment in preparation.

Public testnetPlanned

Public client and documentation when readiness criteria are met.

Security reviewPlanned

Named external audit with published scope — pending.

Release candidatePlanned

Protocol freeze and genesis rehearsal.

MainnetConditional

Only after technical and security gates complete.

Private pre-testnet

Review the protocol

Review the evidence, request a briefing, or follow public milestones. Participation in the network opens later.

Planned for after the testnet

These depend on a public testnet. None of them is open yet.

  • Partner pilots
  • Contributor programme
  • Discord for developers

Stewardship

Juan Tapia

Protocol architect

Protocol architect and distributed-systems engineer with more than three decades building secure coordination systems.

Encrypia Labs (Argentina) develops Zeqron. The Zeqron Foundation, in formation, is intended to govern the protocol.

info@encrypia.comLinkedIn

Coverage areas

Named public owners per area are not published yet. Until then, treat these as coverage labels — not a permanent roster.

  • Protocol engineering
  • Cryptography
  • Zero-knowledge research
  • Developer tooling
  • Security review
  • Legal entity & governance status

Stay in the loop

Protocol updates, roadmap milestones, and ecosystem news.

We use your email only to send protocol updates; write to info@encrypia.com to be removed. Privacy policy

Technical docs (zeqron.io)