chore: update README and docs

README.md

@@ -10,8 +10,9 @@ Summit is a high-performance consensus client designed to drive EVM-based blockc
 - **Responsive Consensus**: Powered by the [Simplex consensus protocol](https://eprint.iacr.org/2023/463), enabling sub-second block times
 - **High Throughput**: Significantly higher TPS than Ethereum
 - **EVM Compatible**: Works with any execution client supporting the Engine API
-- **BLS12-381 Cryptography**: Secure validator key management
+- **BLS12-381 & Ed25519 Cryptography**: Secure validator key management
 - **Built with Commonware**: Leverages primitives from the [Commonware library](https://commonware.xyz)
+- **Dynamic Validator Set**: Supports validator deposits (EIP-6110) and withdrawals (EIP-7002)
 
 Summit uses the Simplex protocol, a responsive consensus mechanism that adapts to network conditions rather than waiting for predetermined timeouts. This allows the network to move as fast as conditions permit, achieving sub-second block times in most cases.
 
@@ -85,9 +86,6 @@ Summit acts as the consensus layer, communicating with EVM execution clients thr
 - Network communication
 
 ## Next steps / Future Roadmap
-- Dynamic Validator sets and staking through the Ethereum staking contract
-  - Currently Summit just uses a static validator set at Genesis
-  - We will leverage EVMs staking contract and add and remove validators in a similar fashion as Ethereum
 - Deeper benchmarks
 - More optimizations (potentially DKG threshold signatures to improve throughput)
 - Full Audit and completeness Q4 2025

docs/actor-system.md

@@ -30,6 +30,16 @@ Summit's architecture follows the actor model with these key principles:
 
 ### 1. Application Actor (`application/src/actor.rs`)
 
+**Purpose**: Handles block production, validation, and finalization
+
+**Key Responsibilities:**
+- Propose blocks when selected as leader
+- Validate blocks received from network
+- Coordinate with execution client via Engine API
+- Maintain block cache for pending/finalized blocks
+
+### 2. Finalizer Actor (`finalizer/src/actor.rs`)
+
 **Purpose**: Manages consensus state, validator set, and staking logic
 
 **Key Responsibilities:**
@@ -39,17 +49,6 @@ Summit's architecture follows the actor model with these key principles:
 - Handle withdrawal processing
 - Create and verify checkpoints
 
-### 2. Finalizer Actor (`finalizer/src/actor.rs`)
-
-**Purpose**: Handles block production, validation, and finalization
-
-**Key Responsibilities:**
-- Propose blocks when selected as leader
-- Validate blocks received from network
-- Coordinate with execution client via Engine API
-- Process consensus finalization messages
-- Maintain block cache for pending/finalized blocks
-
 ### 3. Syncer Actor (`syncer/src/actor.rs`)
 
 **Purpose**: Manages block synchronization, caching, and network state
@@ -60,17 +59,17 @@ Summit's architecture follows the actor model with these key principles:
 - Broadcast verified blocks to peers
 - Maintain local block cache
 - Coordinate synchronization with peers
+- Push notarized and finalized blocks to the Finalizer Actor
 
 ### 4. Orchestrator Actor (`orchestrator/src/actor.rs`)
 
 **Purpose**: Coordinates consensus protocol execution and activity management
 
 **Key Responsibilities:**
-- Execute Simplex consensus protocol
-- Coordinate consensus rounds and view changes
-- Broadcast and receive consensus activities
-- Manage consensus timeouts
-- Interface with Commonware consensus primitives
+- Epoch transition management
+- Simplex engine lifecycle management
+- Network channel multiplexing
+- Epoch boundary block synchronization
 
 ## Actor Supervision and Error Handling