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.
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
- 1Coordination protocol
- 2Post-quantum identity and sessions
- 3Agent policy and execution
- 4Native assets and provenance
- 5Selective 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
Long-lived systems are beginning migration planning as post-quantum standards move into deployment.
Autonomous services may increase transaction frequency, policy complexity, and machine-to-machine settlement requirements.
Globally shared execution can create contention as independent workloads compete for the same coordination surface.
Cryptography
PQ from the substrate
ML-DSA-87 signatures are native in the protocol libraries from the first version; the ML-KEM-1024 handshake is in the current libraries.
Hot-path signatures (ML-DSA-87) and the default handshake key exchange (ML-KEM-1024) use the NIST security category 5 parameter sets, informed by NSA CNSA 2.0 guidance; the cold-path hash-based signature is category 1. That is alignment, not a conformance or classified-product claim.
Hologram is designed to prove compliance attributes without exposing the underlying records; zero-knowledge is not implemented yet.
Coordination
Design target: high global throughput
Mysticeti BFT with ML-DSA batching is the path to horizontal scale across zones.
Sub-second finality is the design target for settlement-sensitive flows.
Bilateral / fair-ordering design reduces MEV surface. A mempool path exists in libraries — not a promise that MEV is impossible.
Agents & meaning
State agents can use
Semantic state stores typed meaning — not only opaque bytes — so agents and apps share a queryable model.
Agent identity and policy (ZAXON): primitives for identity, policy, and attestation in protocol libraries.
One fabric for people, agents, and industrial assets — without inventing a second token layer.
The protocol, part by part
Each part has its own page, with its maturity stated.
- TechnologyPost-quantum cryptography, DAG consensus and zonesInternal build · under validationOpen
- Native assetsZNA: provenance and attestations as protocol stateDesignedOpen
- Agents and privacyZAXON agent policy and Hologram selective disclosureInternal buildOpen
- EconomicsProof of Extraction, reputation-weighted staking, ZQN designSpecified · not implemented end to endOpen
- BuildUse cases and the builder surfaceInternal build · testnet pendingOpen
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.
01
Semantic Zone
A group of parties that share rules. Their agents act within policy limits, and each action leaves a signed record.
02
QronGraph
Each zone commits a hash of its records to a QronGraph. The contents stay with the parties; only the commitment is ordered.
03
QronMesh
QronGraphs exchange proofs as peers. The destination checks that a claim was included; no central chain sits above them.
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.
05
External interfaces
Chain-specific adapters connect other networks, each with an explicit trust boundary. Batch roots can be anchored on a QronGraph.
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
| System | Model | Account security | Execution | Maturity |
|---|---|---|---|---|
| Bitcoin | PoW chain | Classical signatures | Constrained scripting | Production |
| Ethereum | Global state | Classical signatures | EVM contracts | Production |
| Solana | Parallel state | Classical signatures | Parallel runtime | Production |
| Sui | Object model | Classical signatures | Move / objects | Production |
| Zeqron | DAG + zones | PQ as native design target | WASM contracts + native assets | Private pre-testnet |
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 Labs|Last 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.
Protocol gates
Progress is measured through explicit technical and security gates.
Estimates subject to governance. Mainnet is conditional on security and technical gates.
Documented internal exercises and library integration tests.
External validators and multi-region deployment in preparation.
Public client and documentation when readiness criteria are met.
Named external audit with published scope — pending.
Protocol freeze and genesis rehearsal.
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.
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.