EncrypiaBrief companion v0.2September 2026Public · Pre-testnet
03 · Developers · Whitepaper
What is specified — and what you can read as code.
Encrypia coordinates Zeqron. Four responsibilities, not a five-minute tutorial. Application: domain rules in semantic zones. Coordination: contract lifecycle and, when a zone asks, a proof. Consensus: ordering commitments on a DAG with a BFT-style committee (Mysticeti-family lineage adapted for PQ signatures — see Research). Identity: who may act, with which post-quantum credential.
There is software. It lives in a Rust monorepo with automated tests and RFC-driven design. Below these paragraphs are four real excerpts: ContractState (the agreement’s state machine), ContractPhase (high-level phases that group states), AgentIdentity (code digest, operator, capabilities), and FinalityLevel (DAG finality design states). Status of all four: code · no public network endpoint.
ContractState is not a marketing diagram. Idle → Proposed → Negotiating → Committing → Committed → Executing → Executed → Anchored is the object’s path. ContractPhase groups that path into Negotiation → Commitment → Execution → Anchoring. Anchored is the QronGraph anchor. Disputed and Aborted exist because the design contemplates failure, not only the happy path.
Software families the public text can name without inventing a server: contract types (e.g. zeqron-contract-types); consensus / DAG (zeqron-consensus family and QronGraph); identity and ZAXON (DID/VC and AgentIdentity); PQ crypto aligned to FIPS 203/204/205; execution and STARK-class proofs in the design. Naming a family does not publish an RPC, a port, or discovery.
There is no published public network to point a client at. Without a named phase, a published address, and a stable public wire format, a hello-world against the network would be fiction. Today the public act is reading the design and, under repository rules, the code.
FRI, Poseidon, field sizes, validator ceilings, and a full crate inventory stay in internal specifications. Copying them here would publish the appendix the brief omits on purpose.
Cryptographic stack · PQ from genesis
Public brief v0.2 §4 · NIST FIPS
| FIPS 203 | ML-KEM | Key exchange |
|---|---|---|
| FIPS 204 | ML-DSA | Signatures (hot path) |
| FIPS 205 | SLH-DSA | Signatures (cold / anchor) |
Not a later migration plan. All three families are in the design from the start.
Contract lifecycle
zeqron-contract-types · RFC-CONTRACT-001 §10.2
code · no public network endpoint
pub enum ContractState {
Idle,
Proposed,
Negotiating,
Rejected,
Committing,
Committed,
Executing,
Executed,
Aborted,
Anchored, // onto QronGraph
Disputed,
}The agreement is a state machine between parties before it is a row in a global book. Anchored is the order step — not a token transfer.
Contract phases (grouping)
zeqron-contract-types · ContractPhase
code · groups ContractState · no endpoint
pub enum ContractPhase {
Negotiation, // proposal & negotiation
Commitment, // commitment & proof exchange
Execution, // local execution
Anchoring, // global anchoring
Terminal, // aborted / disputed / done
}Phases group enum states. Useful to read the cycle without inventing a port or wire.
Agent identity (excerpt)
zeqron-zaxon · AgentIdentity
code · ZAXON design surface
pub struct AgentIdentity {
pub code_hash: [u8; 32], // digest of agent code
pub operator_did: String, // who is accountable
pub capabilities: Vec<String>, // declared bounds
// version, conformance, chain fields omitted here
}Changing the code changes the identity. A wallet address alone does not describe this bound.
Finality levels (excerpt)
zeqron-consensus · FinalityLevel · DRAFT §2 R20
code · DAG finality design · no public network measurement
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.
Lifecycle · happy path
zeqron-contract-types · ContractState · code
- Proposed
- Negotiating
- Committing
- Committed
- Executing
- Executed
- Anchored
Off path
- Rejected
- Aborted
- Disputed
Anchored is order on QronGraph, not a transfer. Rejected / Aborted / Disputed sit off the happy path.
How to read the excerpts
ContractState / ContractPhase
The contract is a state machine between parties. ContractPhase groups Negotiation, Commitment, Execution, and Anchoring. Both enums live in zeqron-contract-types under RFC-CONTRACT-001. Neither is an RPC nor a published wire schema.
AgentIdentity
code_hash + operator_did + capabilities is the public surface of the ZAXON concept. Changing the code changes the identity. Version, conformance, and chain fields omitted from the excerpt exist in the crate; they are not required to understand the bound.
FinalityLevel
Included → FastFinal → OrderedFinal → Spendable → Settled are claim states on the DAG. Finality-design code · no public network measurement · no TPS row.
Families, not endpoints
If diligence asks “is there code?”, the public answer is: yes, in the named families above, with CI tests. If it asks “where do I connect?”, the public answer is: there is still no published phase.
What would be needed to program against a network
A published phase with date and scope; an address or discovery; a stable wire format. None of the three is part of this publication. The excerpts prove code substance, not a live network.
Not on this page
- An endpoint, an explorer, or a public RPC.
- Circuit parameters or hash families in reproducible detail.
- A timed guide that pretends a production result is minutes away.
- The full crate graph or the internal master dump.