Add detailed pages on stage 2 and based rollup characteristics of Surge (#36)

* add two additional pages

* remove images temporarily

Author: jmadibekov

docs/About/architecture.md

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 1
+sidebar_position: 3
 ---
 
 # Surge Architecture

docs/About/based-rollups.md

@@ -0,0 +1,33 @@
+---
+sidebar_position: 1
+title: Based Rollups
+---
+
+# Based Rollups
+
+## What Are Based Rollups, and Why Do They Matter?
+
+Based rollups are an approach to Layer 2 scaling where the **centralized sequencer** is removed entirely. Instead of a single entity controlling transaction ordering, Ethereum’s own Layer 1 block-building process handles the job. This design is closely tied to [Proposer-Builder Separation (PBS)](https://ethereum.org/en/roadmap/pbs/), a concept in Ethereum’s roadmap that aims to keep block-building open and permissionless.
+
+### The Problem with Conventional Rollups
+Traditional rollups often rely on a centralized sequencer. Although this setup reduces latency and can lower transaction costs, it also:
+- Introduces a single point of failure.
+- Exposes users to potential censorship and transaction reordering.
+- Consolidates power in the hands of the sequencer.
+
+### How Based Rollups Address This
+By tying L2 transaction ordering directly to Ethereum’s decentralized block builders, based rollups inherit Ethereum’s own security and censorship-resistance guarantees:
+- **No Central Authority**: The L1 block-building process takes responsibility for ordering transactions, eliminating the centralized sequencer.
+- **Censorship Resistance**: If Ethereum itself is censorship-resistant, the L2 automatically gains that protection.
+- **Better Alignment With Ethereum**: Validators, builders, and searchers collectively maintain both L1 and L2 transaction inclusion, strengthening decentralization.
+
+### Why Surge Uses a Based Rollup Model
+Surge fully embraces this model for its rollup architecture. By integrating with Ethereum’s existing infrastructure:
+- L2 transactions enter the **same permissionless block-building pipeline** as L1.
+- No single entity can reorder, censor, or halt transactions.
+- Surge becomes **as decentralized as Ethereum itself**, preserving user trust and security.
+
+## Comparing Based and Non-Based Rollups
+
+- **Based Rollups**: Transaction ordering is done by Ethereum’s decentralized validators and block builders, leveraging PBS to maintain fairness and trustlessness.
+- **Conventional Rollups**: A centralized sequencer has the final say on transaction order before batches go to L1, introducing potential risks of manipulation or censorship.

docs/About/stage-2.md

@@ -0,0 +1,32 @@
+---
+sidebar_position: 2
+title: Stage 2
+---
+
+# Stage 2
+
+Surge stands out by embracing a Stage 2 governance model from the very beginning, referencing the [L2Beat’s “Stages” framework](https://medium.com/l2beat/introducing-stages-a-framework-to-evaluate-rollups-maturity-d290bb22befe) that evaluates rollup maturity. By focusing on immutability and self-executing code, Surge mitigates governance risks commonly seen in other rollups where multi-sigs or admin keys can push upgrades before users can fully withdraw their funds.
+
+## Key Governance-Free Design Decisions
+
+### Multi-Sig for Upgrades Only
+- A Nethermind-controlled multi-sig is responsible solely for **queuing** upgrades.
+- If the multi-sig holders become inactive, chain progression remains uninterrupted.
+
+### No Security Council
+- No single entity can enforce upgrades with immediate effect.
+- Ensures no unilateral power to modify or halt the protocol.
+
+### 45-Day Exit Window
+- Users have a minimum of **30 days**, plus additional buffer, to exit prior to any upgrade taking effect.
+- This ensures user safety by preventing sudden changes.
+
+### Trust Code, Not Governance
+- No governance tokens or DAOs influence protocol decisions.
+- Minimizes centralized authority and fosters a trustless environment.
+
+## Why Does This Matter?
+
+Modern rollups often retain centralized elements, which can linger far longer than planned, posing systemic risk. By removing the typical emergency upgrade loopholes, Surge guarantees its users the ability to exit under predictable conditions, reinforcing Ethereum’s principles of decentralization and self-sovereignty.
+
+Surge’s Stage 2 design means **you** have full control of your assets in the face of potential governance failures—no last-minute changes, no rushed exits, and no hidden centralized powers.

docs/intro.md

@@ -4,40 +4,40 @@ sidebar_position: 1
 
 # Introduction to Surge
 
-Surge is a maximally aligned, high-performance Ethereum rollup built on modified Taiko technology. It inherits Ethereum's security while providing enhanced performance and composability
+Surge is a maximally aligned, high-performance Ethereum rollup built on modified Taiko technology. It inherits Ethereum’s security while providing enhanced performance and composability.
 
 ## What is Surge?
 
-Surge is a high-performance, and censorship-resistant Ethereum rollup template meant as a technical showcase that is designed to be:
+Surge is a high-performance and censorship-resistant Ethereum rollup template, meant as a technical showcase that is designed to be:
 
-- based with maximum Ethereum alignment
+- Maximally Ethereum-aligned
 - Stage 2 from launch
 - Provide Gigagas performance
-- Censorship resistant
+- Censorship-resistant
 - Optimized for user experience with low transaction costs and confirmation times
 - Focused on cross-layer composability
 - Built on proven Taiko technology, modified to remove token dependencies
 
 ## Architecture
 
-Learn about the [Surge Architecture](./About/architecture)
+Learn about the [Surge Architecture](./About/architecture).
 
-## Deploying your DApp on surge
+## Deploying Your DApp on Surge
 
-Follow our [DApp Deployment Guideline](./Guides/deploy-dapps/deploy-on-surge)
+Follow our [DApp Deployment Guidelines](./Guides/deploy-dapps/deploy-on-surge).
 
-## Running your Surge rollup
+## Running Your Surge Rollup
 
-Follow the [Running Surge](./Guides/running-surge) guide
+Follow the [Running Surge](./Guides/running-surge) guide.
 
 ## Key Features
 
 - Uses ETH as a gas token
-- Gigagas Per Second gas throughput
+- Gigagas per second gas throughput
 - ZK proving system with multiple proving options
-- Cross-layer composability support (Coming soon)
-- Open source & Maximally Ethereum Aligned
-- Owner multisig have a 45 days timelock on any action to allow users ample time to exit with their funds.
+- Cross-layer composability support (coming soon)
+- Open source & maximally Ethereum-aligned
+- The owner multisig has a 45-day timelock on any action to allow users ample time to exit with their funds.
 
 ## Goals