System Architecture
4.1 Offline Execution Domain (𝓓)
The Offline Execution Domain (𝓓) is where transaction execution occurs. Devices transact directly with one another using local or short-range communication mechanisms such as Bluetooth, Wi-Fi Direct, or local mesh networks. Transactions are validated at the time of execution using cryptographic signatures and value conservation rules, without interaction with global infrastructure.
No global coordination is required during execution. Transactions are not broadcast, routed through public networks, or submitted to shared ledgers at the moment value is transferred. As a result, execution does not generate continuous network-level metadata and is resistant to global surveillance.
The offline domain is designed to be permissive with respect to connectivity and environment. Devices may operate in fully offline settings, intermittently connected settings, or constrained network environments. Execution correctness is enforced locally, while global correctness is deferred.
4.2 KnoxNet Layer 1 Ledger (𝓛₁)
The KnoxNet Layer 1 Ledger (𝓛₁) is a custom blockchain optimized for encrypted verification and economic enforcement, rather than for replaying every transaction in plaintext. It serves as the system's global coordination and enforcement layer.
The Layer 1 ledger is responsible for:
Escrowing value and issuing offline spendable units
Registering and enforcing uniqueness of notes or value identifiers
Verifying reconciliation submissions
Detecting contradictions such as double-spends through deterministic fraud proofs
Applying penalties and slashing when misbehavior is detected
Enforcing global supply and issuance invariants
Unlike conventional blockchains, 𝓛₁ does not process full transaction histories or observe execution in real time. Its primary role is to verify that system-wide constraints have been preserved once offline activity is reconciled. To minimize information leakage, the ledger is designed to validate encrypted settlement constraints rather than plaintext transaction flows.
4.3 Reconciliation Layer (ℛ)
The Reconciliation Layer (ℛ) connects the offline execution domain with the KnoxNet Layer 1 ledger. It is responsible for transforming offline transaction histories into settlement updates that can be verified by the ledger.
When connectivity is available, devices submit reconciliation payloads derived from offline activity. These payloads do not reveal full transaction histories. Instead, they encode the information necessary to:
Demonstrate value conservation
Update ownership state
Prove uniqueness of consumed value units
Expose contradictions if conflicting histories exist
The reconciliation layer enforces correctness by ensuring that all submitted updates satisfy global invariants. If contradictions are detected—such as the same value unit appearing in multiple histories—fraud proofs are generated deterministically and penalties are applied by the Layer 1 ledger.
By separating reconciliation from both execution and ledger enforcement, KnoxNet avoids forcing offline activity into immediate global visibility while still guaranteeing eventual correctness and accountability.