EncrypiaBrief companion v0.2September 2026Public · Pre-testnet
04 · Operators · Whitepaper
Decision today: no public enrollment.
Explicit decision, September 2026 — Encrypia / Architecture · Pre-testnet: there is no public operator enrollment. There is no validator set accepting open applications. Anyone operating today does so in an internal setting, not on a network with a published phase. If you came to sign up, the useful answer is: not yet. The rest of this reading is design substance for deciding what to do meanwhile — not a soft launch dressed as transparency.
PoSS, in the design documents, joins two things: stake posted, and an observable service. The service points at availability, capacity, and correctness of the work the operator claims to do. Participation is not solely locking capital. The exact relation among stake, rubric, reward, and penalty is not published as a formula: publishing a yield would invent the result of a network that is not open.
When a network exists with a phase, a measurement, and a name, the runbook should ship with that network. Chapter order the design anticipates — no hardware, ports, amounts, or commands: (1) Machine and network — environment and connectivity, without a shopping list; (2) Identity — how an operator is recognized under post-quantum credentials; (3) Stake — capital at risk as a participation condition; (4) Service — what work is observed and how it is evidenced; (5) Fault — what counts as breach and what consequence the design contemplates. Naming the order prepares the ground. It does not write the manual.
In the monorepo, design-level economics types include a fault / sanction-reason taxonomy at design-and-code level. That proves the model contemplates breach, not only the happy path. This page does not publish amounts, schedules, or a live-penalty timetable: without an open network, that table would be theater.
If you operate another network today, three honest decisions: wait for a named phase with a runbook; ignore Zeqron until that phase exists; or, when the phase is named, ask for an ops pack under NDA. There is no useful third path that is “enroll from this site.” Validator work, when it exists, will be understood against a DAG with a BFT-style committee and PQ signatures — a different ops intuition than a classical linear chain alone; it does not replace the still-unpublished procedure.
Future runbook · chapters (purpose)
Design · no named phase · no ports or amounts
- 01
Machine & network
What environment is expected (connectivity, node role).
Out today — SKUs, ports, commands, shopping list.
- 02
Identity
How an operator is recognized under post-quantum DID/VC.
Out today — Enrollment, configs, classical-only ops shortcut.
- 03
Stake
Capital at risk as a participation condition.
Out today — Amounts, schedules, yield.
- 04
Service
Observed work: availability, capacity, correctness.
Out today — Live rubric, rewards, public metrics panel.
- 05
Fault
What counts as breach and what consequence the design contemplates.
Out today — Live slashing schedule, slash amounts.
When a named, measured network exists, the manual should ship with it. Today: purpose of each chapter only.
Ops decision · three paths
September 2026 · no public enrollment
A
Wait
Named phase + runbook shipping with that network.
B
Ignore
Until a phase exists. Run other infra in the meantime.
C
Request NDA
When the phase is named: ops pack under agreement — not from this form.
No enrollment from this site. Inventing yield or hosting cost is a red flag.
Future runbook order (chapters with purpose)
Machine → Identity
Machine: what environment is expected, without SKUs or ports today. Identity: operator credentialing under the same FIPS primitives as any participant — no classical “nodes-only” shortcut in the long-term posture.
Stake → Service
Stake: capital at risk as a condition. Service: observable availability, capacity, and correctness. Exact rubric is internal; the public shape is not stake-only.
Fault
Define breach and consequence. A fault taxonomy exists in design/code; no amount table or variants published as a live slashing schedule.
What to decide now
Wait / ignore / request an NDA ops pack when a phase is named. Inventing a hosting cost or a yield from this page is a red flag for your own ops diligence.
This page does not publish
- A return percentage, daily or annual.
- Hardware, ports, commands, or configuration files.
- A hosting vendor or an economic break-even point.
- An enrollment form: public enrollment is not open.
- Stake amounts or a live sanction timetable.