fix

Author: tac0turtle

README.md

@@ -11,6 +11,7 @@ Ev-node is the basis of the Evolve Stack. For more in-depth information about Ev
 ## Using Evolve
 
 Evolve supports multiple sync modes:
+
 - **Hybrid sync**: Sync from both DA layer and P2P network (default when peers are configured)
 - **DA-only sync**: Sync exclusively from DA layer by leaving P2P peers empty (see [Configuration Guide](docs/learn/config.md#da-only-sync-mode))
 - **P2P-priority sync**: Prioritize P2P with DA as fallback

block/CLAUDE.md

@@ -9,6 +9,7 @@ The block package is the core of ev-node's block management system. It handles b
 ## Core Components
 
 ### Manager (`manager.go`)
+
 - **Purpose**: Central orchestrator for all block operations
 - **Key Responsibilities**:
   - Transaction aggregation into blocks
@@ -18,6 +19,7 @@ The block package is the core of ev-node's block management system. It handles b
   - P2P block/header gossiping
 
 ### Aggregation (`aggregation.go`, `lazy_aggregation_test.go`)
+
 - **Purpose**: Collects transactions from mempool and creates blocks
 - **Modes**:
   - **Normal Mode**: Produces blocks at regular intervals (BlockTime)
@@ -28,6 +30,7 @@ The block package is the core of ev-node's block management system. It handles b
   - `normalAggregationLoop`: Regular block production
 
 ### Synchronization (`sync.go`, `sync_test.go`)
+
 - **Purpose**: Keeps the node synchronized with the network
 - **Key Functions**:
   - `SyncLoop`: Main synchronization loop
@@ -36,6 +39,7 @@ The block package is the core of ev-node's block management system. It handles b
   - Handles header and data caching
 
 ### Data Availability (`da_includer.go`, `submitter.go`, `retriever.go`)
+
 - **DA Includer**: Manages DA blob inclusion proofs and validation
 - **Submitter**: Handles block submission to the DA layer with retry logic
 - **Retriever**: Fetches blocks from the DA layer
@@ -45,6 +49,7 @@ The block package is the core of ev-node's block management system. It handles b
   - Batch submission optimization
 
 ### Storage (`store.go`, `store_test.go`)
+
 - **Purpose**: Persistent storage for blocks and state
 - **Key Features**:
   - Block height tracking
@@ -53,6 +58,7 @@ The block package is the core of ev-node's block management system. It handles b
   - Migration support for namespace changes
 
 ### Pending Blocks (`pending_base.go`, `pending_headers.go`, `pending_data.go`)
+
 - **Purpose**: Manages blocks awaiting DA inclusion or validation
 - **Components**:
   - **PendingBase**: Base structure for pending blocks
@@ -64,6 +70,7 @@ The block package is the core of ev-node's block management system. It handles b
   - Memory-efficient caching
 
 ### Metrics (`metrics.go`, `metrics_helpers.go`)
+
 - **Purpose**: Performance monitoring and observability
 - **Key Metrics**:
   - Block production times
@@ -74,20 +81,23 @@ The block package is the core of ev-node's block management system. It handles b
 ## Key Workflows
 
 ### Block Production Flow
+
 1. Transactions collected from mempool
 2. Block created with proper header and data
 3. Block executed through executor
 4. Block submitted to DA layer
 5. Block gossiped to P2P network
 
 ### Synchronization Flow
+
 1. Headers received from P2P network
 2. Headers validated and cached
 3. Block data retrieved from DA layer
 4. Blocks applied to state
 5. Sync progress updated
 
 ### DA Submission Flow
+
 1. Block prepared for submission
 2. Blob created with block data
 3. Submission attempted with retries
@@ -97,47 +107,55 @@ The block package is the core of ev-node's block management system. It handles b
 ## Configuration
 
 ### Time Parameters
+
 - `BlockTime`: Target time between blocks (default: 1s)
 - `DABlockTime`: DA layer block time (default: 6s)
 - `LazyBlockTime`: Max time between blocks in lazy mode (default: 60s)
 
 ### Limits
+
 - `maxSubmitAttempts`: Max DA submission retries (30)
 - `defaultMempoolTTL`: Blocks until tx dropped (25)
 
 ## Testing Strategy
 
 ### Unit Tests
+
 - Test individual components in isolation
 - Mock external dependencies (DA, executor, sequencer)
 - Focus on edge cases and error conditions
 
 ### Integration Tests
+
 - Test component interactions
 - Verify block flow from creation to storage
 - Test synchronization scenarios
 
 ### Performance Tests (`da_speed_test.go`)
+
 - Measure DA submission performance
 - Test batch processing efficiency
 - Validate metrics accuracy
 
 ## Common Development Tasks
 
 ### Adding a New DA Feature
+
 1. Update DA interfaces in `core/da`
 2. Modify `da_includer.go` for inclusion logic
 3. Update `submitter.go` for submission flow
 4. Add retrieval logic in `retriever.go`
 5. Update tests and metrics
 
 ### Modifying Block Production
+
 1. Update aggregation logic in `aggregation.go`
 2. Adjust timing in Manager configuration
 3. Update metrics collection
 4. Test both normal and lazy modes
 
 ### Implementing New Sync Strategy
+
 1. Modify `SyncLoop` in `sync.go`
 2. Update pending block handling
 3. Adjust cache strategies
@@ -182,4 +200,4 @@ The block package is the core of ev-node's block management system. It handles b
 - Log with structured fields
 - Return errors with context
 - Use metrics for observability
-- Test error conditions thoroughly
+- Test error conditions thoroughly

block/submitter.go

@@ -329,10 +329,10 @@ func handleSuccessfulSubmission[T any](
 	remLen := len(remaining)
 	allSubmitted := res.SubmittedCount == uint64(remLen)
 
-		// Record submission in DA visualization server
-		if daVisualizationServer := server.GetDAVisualizationServer(); daVisualizationServer != nil {
-			daVisualizationServer.RecordSubmission(&res, gasPrice, len(currMarshaled))
-		}
+	// Record submission in DA visualization server
+	if daVisualizationServer := server.GetDAVisualizationServer(); daVisualizationServer != nil {
+		daVisualizationServer.RecordSubmission(res, retryStrategy.gasPrice, res.SubmittedCount)
+	}
 
 	m.logger.Info().Str("itemType", itemType).Float64("gasPrice", retryStrategy.gasPrice).Uint64("count", res.SubmittedCount).Msg("successfully submitted items to DA layer")
 

docs/learn/config.md

@@ -63,12 +63,14 @@ Evolve supports running nodes that sync exclusively from the Data Availability (
 **To enable DA-only sync mode:**
 
 1. **Leave P2P peers empty** (default behavior):
+
    ```yaml
    p2p:
      peers: ""  # Empty or omit this field entirely
    ```
-   
+
 2. **Configure DA connection** (required):
+
    ```yaml
    da:
      address: "your-da-service:port"
@@ -79,6 +81,7 @@ Evolve supports running nodes that sync exclusively from the Data Availability (
 3. **Optional**: You can still configure P2P listen address for potential future connections, but without peers, no P2P networking will occur.
 
 When running in DA-only mode, the node will:
+
 - ✅ Sync blocks and headers from the DA layer
 - ✅ Validate transactions and maintain state
 - ✅ Serve RPC requests

docs/learn/specs/block-manager.md

@@ -267,23 +267,23 @@ flowchart TD
     B -->|Mempool/Not Included| E[Mempool Backoff Strategy]
     B -->|Context Canceled| F[Stop Submission]
     B -->|Other Error| G[Exponential Backoff]
-    
+
     D -->|Yes| H[Recursive Batch Splitting]
     D -->|No| I[Skip Single Item - Cannot Split]
-    
+
     E --> J[Set Backoff = MempoolTTL * BlockTime]
     E --> K[Multiply Gas Price by GasMultiplier]
-    
+
     G --> L[Double Backoff Time]
     G --> M[Cap at MaxBackoff - BlockTime]
-    
+
     H --> N[Split into Two Halves]
     N --> O[Submit First Half]
     O --> P[Submit Second Half]
     P --> Q{Both Halves Processed?}
     Q -->|Yes| R[Combine Results]
     Q -->|No| S[Handle Partial Success]
-    
+
     C --> T[Update Pending Queues]
     T --> U[Post-Submit Actions]
 ```
@@ -295,7 +295,7 @@ flowchart TD
   * Exponential backoff for general failures (doubles each attempt, capped at `BlockTime`)
   * Mempool-specific backoff (waits `MempoolTTL * BlockTime` for stuck transactions)
   * Success-based backoff reset with gas price reduction
-* **Gas Price Management**: 
+* **Gas Price Management**:
   * Increases gas price by `GasMultiplier` on mempool failures
   * Decreases gas price after successful submissions (bounded by initial price)
   * Supports automatic gas price detection (`-1` value)

pkg/rpc/server/da_visualization.go

@@ -23,7 +23,7 @@ type DASubmissionInfo struct {
 	GasPrice   float64   `json:"gas_price"`
 	StatusCode string    `json:"status_code"`
 	Message    string    `json:"message,omitempty"`
-	NumBlobs   int       `json:"num_blobs"`
+	NumBlobs   uint64    `json:"num_blobs"`
 	BlobIDs    []string  `json:"blob_ids,omitempty"`
 }
 
@@ -48,7 +48,7 @@ func NewDAVisualizationServer(da coreda.DA, logger zerolog.Logger, isAggregator
 
 // RecordSubmission records a DA submission for visualization
 // Only keeps the last 100 submissions in memory for the dashboard display
-func (s *DAVisualizationServer) RecordSubmission(result *coreda.ResultSubmit, gasPrice float64, numBlobs int) {
+func (s *DAVisualizationServer) RecordSubmission(result *coreda.ResultSubmit, gasPrice float64, numBlobs uint64) {
 	s.mutex.Lock()
 	defer s.mutex.Unlock()