Protocol-Native Security: How It Works
We eliminate the custodian risk model. On the OCS Network, security is guaranteed by the protocol itself, where the PGTAIL Sequencer Logic enforces your rules before any transaction is ever included in a block.
1. Define Policy in Your Smart Account
Sovereign Control via Account Abstraction
Users first bridge assets from L1 (e.g., Ethereum) to the OCS Network L2. This process **natively creates a programmable Smart Account** that is owned exclusively by your L1 cold wallet. You then write your custom rules—like whitelists, velocity limits, and Multi-Sig requirements—directly into this on-chain contract.
This step removes the need for any external co-signer; your account is the sole source of truth.
2. PGTAIL Protocol Pre-Validation
Mandatory Check Before Block Inclusion
When you submit a transaction, the **OCS Sequencer** does not immediately execute it. Instead, it runs the **PGTAIL Protocol** check, which acts as a mandatory validation gate. The Sequencer combines your **Smart Account's rules** with real-time **Off-Chain Risk Scores** (E4) before attempting to finalize.
This check happens instantly and guarantees zero latency, making high-speed DEX trades safe.
3. Native Rejection (Fail-Closed)
Blocking Fraud Before It's Mined
If the transaction violates *any* policy (e.g., recipient not whitelisted, transaction exceeds velocity limit, or PGTAIL detects a high-risk scam), the OCS Sequencer is cryptoeconomically forced to **natively drop the transaction from the mempool**. The transaction is never included in a block.
This is the ultimate security guarantee: the network fails safe, actively preventing fraud based on your own law.