Conceptual public-receipt ledger. Not a running network or accounting service.
PUBLIC NETWORK / NOT LIVEWORKSTREAM / FUTUREACCOUNT TARGET / PUBLICLIVE FUND / NONE
01 / SYSTEM BRIEF
Privacy rule, inverted.
Private value for people. Public accounting for machines. OPEN explores that opposite trust boundary.
01
THE INVERSION
Public by protocol target.
OPEN is designed as the inverse of its siblings: public accounts and auditable payments for machine activity. That is a future protocol design, not a description of a running ledger or a guarantee that every machine payment will be verifiable.
02
THE RECEIPT
Activity meant to be checked.
The design target makes accounts, payments, and the maintenance fund public by protocol rule. It must still be implemented, reviewed, threat-modeled, and tested.
03
THE RESTRAINT
Keep machinery out at first.
The current design would keep markets, arbitration, and other complex machinery out of an initial release. Any later feature would need explicit activation conditions, implementation, independent review, and public evidence.
02 / ACCOUNTABILITY INSPECTION
Account. Receipt. Control.
These layers describe the intended boundary. They are not a product demo, live fund display, or guarantee of machine accountability.
OPN::RECEIPT_STACKSTATIC DESIGN INSPECTION
LAYER 01 / PUBLIC ACCOUNT MODEL
Attributed by design target.
OPEN explores public accounts for machine activity so payments can be inspected, attributed, and reconciled. The account model is not a public release artifact and remains incomplete.
A public account does not automatically prove that the machine or actor behind it behaved correctly.
LAYER 02 / PUBLIC PAYMENT RECORD
The ledger should show its work.
The target makes accounts, payments, and maintenance funding public by protocol rule. OPEN is not a running ledger, and there is no guarantee today that any machine payment can be verified through it.
The implementation, registry, threat model, testnet, and final whitepaper are not public release artifacts.
LAYER 03 / ENDOWMENT + GOVERNANCE
Transparent does not mean settled.
The current economic design starts at zero and assigns a protocol-limited share of emission to a transparent maintenance endowment. The allocation, controls, accounting, governance, and legal treatment are not final, and no live fund exists.
Markets, arbitration, and complex machinery remain outside the intended initial release.
03 / SPECIFICATION + STATE
A design, not a ledger.
OPEN is materially earlier than DAARX and L10N. Its provisional parameters describe a workstream, not a launch-ready network.
OPN::FUTURE_DESIGNSNAPSHOT / 2026.07.15
Block target
27 seconds — provisional design parameter
Security target
Merged mining — not launch-integrated
Accounts
Public by design — implementation incomplete
Endowment
Transparent maintenance design — allocation and controls not final
Initial restraint
Markets, arbitration, and complex machinery intended to remain out
Current status
Future protocol; no public network or mining
Launch boundary
Status — July 15, 2026: OPEN remains a future protocol workstream. Its account model, endowment, registry, threat model, implementation, testnet, and whitepaper are not public release artifacts, and no release date is promised.
PUBLIC RELEASE STATEFUTURE WORKNO PUBLIC NETWORK / NO DATE PROMISED
04 / NEXT ROUTE
Public by rule, if built.
The goal is to let a compatible DAARX miner contribute work to OPEN without a separate proof-of-work run. That path is not release-ready, and no rig can mine a public OPEN network today.