OCS Network Architecture Overview
Protocol-Level Policy Enforcement and the Smart Account Model
1. L2 Architecture Model
The OCS Network functions as a sovereign, application-specific Layer 2 (App-Chain). It inherits ultimate security from the L1 (Ethereum) while providing custom, policy-enforced execution on the L2.
| Layer | Component | Function | Trust/Security Role |
|---|---|---|---|
| L1 | Ethereum | Settlement and Consensus Layer | Provides finality and cryptographic security for the L2 state roots. |
| L2 | OCS Network | Execution Layer | Where all transactions and policy checks occur. |
| Core Logic | PGTAIL Protocol | Native Validator/Sequencer Logic | The Mandatory Gate: Checks transactions against policy before block inclusion. |
| User Control | L2 Smart Account (AA) | User Asset Holder and Policy Vault | Controlled exclusively by the user's L1 cold wallet, holds policy rules. |
2. New Transaction Flow: Native Enforcement
The flow is designed for speed and security. It eliminates external API calls and co-signing by making validation a prerequisite for execution on the L2.
- Onboarding & Bridging: User deposits assets from L1 (e.g., Ethereum) to the OCS Network bridge contract. This creates their Smart Account on the L2.
- Policy Setup: User defines rules (whitelists, limits) which are written to the Smart Account's immutable storage.
- Transaction Initiation: User submits a transfer/order to an OCS Sequencer.
- Native Validation (PGTAIL): The Sequencer runs a mandatory pre-validation check against the user's policy and the real-time risk score from the PGTAIL Engine.
- Execution or Rejection: If valid, the TX is executed instantly. If invalid, the Sequencer is cryptoeconomically forced to drop the transaction (Native Rejection).
3. Security Features & Mitigation
The architecture provides explicit mitigation against the systemic failures of the centralized model.
Custodian/Insider Access
Mitigated by: Total Removal of Custodial Intermediary. Assets are held in user-controlled L2 Smart Accounts (non-custodial).
API Bypass / Policy Override
Mitigated by: Protocol-Native Enforcement. PGTAIL is the Sequencer's primary validation function; bypassing it results in Sequencer slashing.
Malicious Sequencer
Mitigated by: OCS Token Slashing and L1 Fraud Proofs. Dishonesty is cryptoeconomically penalized and proven on Ethereum.
Social Engineering / Key Delegation
Mitigated by: Account Abstraction delegation (limited 'session keys') enforced by L2 policy (Velocity Limits, Whitelists).
The OCS Network shifts security from an external service to a native protocol feature. Policy enforcement is a fundamental requirement for block finality.