docs(protocol): update intro and add security model section (#867)

Updates introduction and adds security model section to protocol docs

task: none

docs/site/docs/learn/building.md

@@ -31,8 +31,8 @@ For detailed information on how the native token is utilized for gas abstraction
 
 ## Restaking ETH
 
-The Omni Network consists of validators who restake **\$ETH** and monitor the state of rollups. These validators relay state updates from one domain to others and provide crypto-economic assurance of validity. Read more about economic security in the [Omni Security Model section](../protocol/restaking/architecture.md).
+The Omni Network consists of validators who restake **\$ETH** and monitor the state of rollups. These validators relay state updates from one domain to others and provide crypto-economic assurance of validity. Read more about economic security in the [Omni Security Model section](../protocol/security/implementation.md).
 
 This means that the Omni Network is going to be the first platform that provides developers with a global view of state from all rollups, making cross-rollup application development extremely simple. All of this is made possible through the unique insight to use Ethereum's validator set to aggregate a global perspective of Ethereum's L2 ecosystem.
 
-Read on how to delegate restaked **\$ETH** to Omni with EigenLayer in the [Delegating ETH](./delegate.md) section and read more on how Omni handles restaking in the [Restaking](../protocol/restaking/restaking.md) protocol section.
+Read on how to delegate restaked **\$ETH** to Omni with EigenLayer in the [Delegating ETH](./delegate.md) section and read more on how Omni handles restaking in the [Restaking](../protocol/security/restaking.md) protocol section.

docs/site/docs/protocol/introduction/components.md

@@ -4,12 +4,15 @@ sidebar_position: 2
 
 # Component Overview
 
+The Omni protocol is composed of five primary components: **rollup networks**, **the Omni Network**, **EigenLayer restaking contracts**, **Omni Portal contracts**, and **relayers**.
+
 <figure>
   <img src="/img/components.png" alt="Components" />
   <figcaption>*Overview of the Components of the Network*</figcaption>
 </figure>
 
-- It consists of two internal chains, a consensus layer and an execution layer, similar to post-merge Ethereum.
+- A **rollup network** is any Ethereum rollup that performs off-chain transaction execution before settling to Ethereum L1.
+- The **Omni Network** is a layer 1 blockchain that connects rollup VMs. Similar to Ethereum, Omni nodes are separated into distinct execution and consensus layers. It consists of two internal chains, a consensus layer and an execution layer, similar to post-merge Ethereum.
     - Similar to Ethereum, Omni nodes are separated into distinct execution and consensus environments
         - The **execution layer** is implemented by standard Ethereum execution clients. like  **`geth`**, **`erigon`**, etc, to provide the Omni EVM.
         - The **consensus** layer is implemented by the Omni consensus client, halo, and uses CometBFT for consensus on XMsgs and Omni EVM blocks.

docs/site/docs/protocol/introduction/introduction.md

@@ -7,20 +7,6 @@ id: introduction
 
 Omni implements a novel protocol architecture that establishes a new precedent for secure, performant, and globally compatible interoperability across the Ethereum ecosystem. This section breaks down the mechanisms and design choices that underpin the protocol.
 
-## Omni's Dual Role
-
-The Omni chain is engineered to perform two critical functions within the blockchain ecosystem:
-
-### Integrated Consensus
-
-#### Cross-Rollup Message Consensus
-
-Omni serves as a bridge between various rollups, enabling them to communicate seamlessly. This functionality is vital for maintaining coherence and interoperability in the increasingly fragmented blockchain landscape.
-
-#### Omni EVM Operation Consensus
-
-The Omni EVM is a parallel execution environment that operates under the same consensus umbrella as the cross-rollup messages. It empowers developers to build and deploy decentralized applications that can interact with different blockchain networks, all within the Omni ecosystem.
-
 ## Security
 
 Previous attempts to secure externally verified interoperability networks relied on native assets for cryptoeconomic security. Under this approach, the scale of the protocol’s security is directly tied to the demand for the protcol’s native asset, introducing reflexive dynamics that result in unstable security guarantees.
@@ -36,7 +22,29 @@ The security of the Omni chain is upheld by a dual-staking mechanism:
 - **Restaked \$ETH**: Omni leverages the existing security of Ethereum by allowing participants to restake their Ethereum holdings, contributing to the Omni network's overall security.
 - **Staked \$OMNI**: Alongside **\$ETH**, Omni's native token, **\$OMNI**, is staked as a commitment to the network's integrity, aligning incentives and enhancing security.
 
-### Simplified Yet Powerful
+## Performance
+
+Omni’s novel protocol architecture is optimized for verification speed to minimize `XMsg` latency. At the heart of the network’s design is a new framework for combining the EVM with CometBFT consensus. This uses the Engine API and ABCI++ to create a clear separation between a node’s execution and consensus environments, thereby isolating the components that bottleneck performance in alternative frameworks. This enables a system capable of sub-second consensus for both `XMsg`s and Omni EVM transactions.
+
+### Omni's Dual Role
+
+The Omni chain is engineered to perform two critical functions within the blockchain ecosystem:
+
+#### Cross-Rollup Message Consensus
+
+Omni serves as a bridge between various rollups, enabling them to communicate seamlessly. This functionality is vital for maintaining coherence and interoperability in the increasingly fragmented blockchain landscape.
+
+#### Omni EVM Operation Consensus
+
+The Omni EVM is a parallel execution environment that operates under the same consensus umbrella as the cross-rollup messages. It empowers developers to build and deploy decentralized applications that can interact with different blockchain networks, all within the Omni ecosystem.
+
+## Global Compatibility
+
+Omni enables any application to become Turing complete across all rollup environments. The protocol is engineered with minimal integration requirements to ensure compatibility with any rollup architecture. To support a diverse range of rollup architectures, Omni implements a universal gas marketplace that is capable of handling gas payments in diverse assets. Building on these foundational features, the protocol is designed to offer backward compatibility with existing rollup applications. Specifically, applications can integrate Omni using modified frontend instructions rather than altering their existing contracts.
+
+While Omni is designed with existing rollup applications in mind, the growing diversity within the rollup ecosystem is increasing the complexity associated with managing these application deployments across rollups. The Omni EVM provides a global orchestration layer for managing local application instances between rollups. Developers can leverage the Omni EVM to build Natively Global Applications (NGAs), a new category of applications that dynamically propagate contracts and interfaces to any rollup, allowing them to access all of Ethereum’s liquidity and users by default.
+
+## Simplified Yet Powerful
 
 While Omni's infrastructure is complex and performant, our goal is to present the information in a digestible format. Throughout the Protocol section, you will find detailed yet accessible content that breaks down how Omni achieves its vision of a universally connected and secure blockchain ecosystem.
 

docs/site/docs/protocol/security/implementation.md

@@ -0,0 +1,14 @@
+---
+sidebar_position: 3
+---
+
+# Implementation
+
+<figure>
+  <img src="/img/staking.png" alt="Staking" />
+  <figcaption>*Restaking ETH in Omni and Ethereum using EigenLayer AVS*</figcaption>
+</figure>
+
+The Omni staking contract is implemented on the Omni EVM. It tracks each validator’s stake and delegations, facilitates rewards distribution, and handles slashing events. The Omni AVS contract is implemented on Ethereum. It registers Omni as an application with the EigenLayer protocol and allows operators to opt-in to providing validation services to the Omni blockchain. Finally, Omni Portal contracts are implemented on the Omni EVM and all connected rollup VMs. These contracts maintain a copy of the Omni validator set’s stake, delegations, and voting power.
+
+To communicate staking events, Omni leverages its own `XMsg` format. Validators monitor the Omni staking contract on the Omni EVM for stake changes and the Omni AVS contract on Ethereum for delegation changes. These changes alert the Omni validator set to update its voting power details and pass the updates to Omni Portal contracts on every connected rollup VM. Finally, rewards and slashing events are initiated by the Omni validator set and are delivered to the Omni staking contract for execution.

docs/site/docs/protocol/security/reinforced.md

@@ -0,0 +1,24 @@
+---
+sidebar_position: 2
+---
+
+# Reinforced Security
+
+Omni achieves stronger and more stable security guarantees than existing interoperability protocols by deriving its cryptoeconomic security from restaked **\$ETH**. Omni extends its security model further by incorporating staked **\$OMNI** using a dual staking model. Effectively, the total cryptoeconomic security of Omni is determined by the combined value of restaked **\$ETH** and staked **\$OMNI**.
+
+Using this dual staking model, the total cryptoeconomic security $\textit{C}$ of the system is given by the formula:
+
+<br/>
+<div style={{ textAlign: 'center', fontSize: '1.7em' }}>
+$C = \frac{2}{3} \sum_{a=0}^{m} \sum_{v=0}^{n} P_a(S_{a,v})$
+</div>
+<br/>
+
+where:
+
+- $S_{a,v}$ is the amount staked by validator $v$ for asset $a$
+- $P_a$ is the function mapping the amount of asset $a$ staked to validator power
+- $n$ is the total number of validators
+- $m$ is the total number of unique staked asset types
+
+Omni uses this reinforced staking model to scale its security across two dimensions. Restaked **\$ETH** anchors Omni’s security to Ethereum L1, enabling it to grow in line with Ethereum’s own security budget. The addition of staked **\$OMNI** builds upon this base, expanding Omni’s security alongside its own network activity. Collectively, these two complementary mechanisms provide robust and dynamic security guarantees for Omni, setting a new standard for secure interoperability for the Ethereum ecosystem.

docs/site/docs/protocol/security/restaking.md

@@ -0,0 +1,14 @@
+---
+sidebar_position: 1
+---
+
+# Restaking
+
+<figure>
+  <img src="/img/restaking-security.png" alt="Security Model" />
+  <figcaption>*Omni derives cryptoeconomic security from restaked $ETH*</figcaption>
+</figure>
+
+Omni validators are responsible for verifying the authenticity of cross-rollup messages (`XMsgs`) and transactions on the Omni EVM. Using restaked **\$ETH** via EigenLayer, Omni leverages the cryptoeconomic security of Ethereum L1 for its own validator set. With more than $100 billion securing Ethereum L1, Ethereum’s security budget is an order of magnitude larger than any other Proof-of-Stake network.
+
+By leveraging restaked **\$ETH**, a highly liquid, low volatility asset, Omni’s security achieves significantly greater stability than its predecessors. Moreover, by deriving security from Ethereum, Omni aligns its security base with the rollups it connects, facilitating a security model that grows in tandem with Ethereum’s modular ecosystem. By implementing a cryptoeconomic security model using restaked **\$ETH**, Omni establishes a new paradigm for secure and reliable interoperability across the entire industry.

docs/site/sidebars.ts

@@ -88,6 +88,22 @@ const sidebars: SidebarsConfig = {
       type: "html",
       value: "<div class='sidebar-separator'></div>",
     },
+    {
+      type: "category",
+      label: "Security Model",
+      className: "sidebar-title",
+      collapsible: false,
+      items: [
+        {
+          type: "autogenerated",
+          dirName: "protocol/security",
+        }
+      ]
+    },
+    {
+      type: "html",
+      value: "<div class='sidebar-separator'></div>",
+    },
     {
       type: "category",
       label: "Cross-Rollup Messages",
@@ -141,22 +157,6 @@ const sidebars: SidebarsConfig = {
       type: "html",
       value: "<div class='sidebar-separator'></div>",
     },
-    {
-      type: "category",
-      label: "Restaking",
-      className: "sidebar-title",
-      collapsible: false,
-      items: [
-        {
-          type: "autogenerated",
-          dirName: "protocol/restaking",
-        }
-      ]
-    },
-    {
-      type: "html",
-      value: "<div class='sidebar-separator'></div>",
-    },
     "protocol/audits",
     "protocol/future"
   ],