Rename the builder containers to shadow-builder

Author: niran

README.md

@@ -38,19 +38,21 @@ A Reth-based execution client that:
 - Syncs from production sequencer via an op-node instance (simulator-cl)
 - Used by the block builder stack to throttle transactions based on resource consumption
 
-## 🏗️ Block Builder Stack
+## 🏗️ Shadow Builder Stack
 
-The block builder stack enables production-ready block building with TIPS bundle integration. It consists of:
+The shadow builder stack enables production-ready block building with TIPS bundle integration. It consists of:
 
-**builder-cl**: An op-node instance running in sequencer mode that:
+**shadow-builder-cl**: An op-node instance running in sequencer mode that:
 - Syncs from production sequencer via P2P
 - Drives block building through Engine API calls
+- Uses a placeholder sequencer key so built blocks will be rejected by the network
 - Does not submit blocks to L1 (shadow sequencer mode)
 
-**builder**: A modified op-rbuilder instance that:
-- Receives Engine API calls from builder-cl
+**shadow-builder**: A modified op-rbuilder instance that:
+- Receives Engine API calls from shadow-builder-cl
 - Queries TIPS datastore for bundles with resource usage estimates from the simulator
 - Builds blocks including eligible bundles while respecting resource constraints
+- Runs in parallel with the production builder for testing and validation
 
 **Prerequisites**:
 - [builder-playground](https://github.com/flashbots/builder-playground) running locally with the `niran:authorize-signers` branch
@@ -61,8 +63,8 @@ The block builder stack enables production-ready block building with TIPS bundle
 # Build op-rbuilder (optionally from a specific branch)
 just build-rbuilder
 
-# Start the builder stack (requires builder-playground running)
+# Start the shadow builder stack (requires builder-playground running)
 just start-builder
 ```
 
-The builder-cl syncs from the production sequencer via P2P while op-rbuilder builds blocks with TIPS bundles. Built blocks are not submitted to L1, making this safe for testing and development.
+The shadow-builder-cl syncs from the production sequencer via P2P while shadow-builder builds blocks with TIPS bundles in parallel with the production builder. The shadow builder's blocks are never broadcast to the network due to the invalid sequencer key, and there is no batcher service to submit them to L1, making this safe for testing and validation without affecting production.

docker-compose.yml

@@ -112,11 +112,11 @@ services:
       # ENGINE CONFIGURATION (simulator-specific)
       OP_NODE_L2_ENGINE_RPC: http://simulator:4444
 
-  builder-cl:
+  shadow-builder-cl:
     image: us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:v1.13.7
-    container_name: tips-builder-cl
+    container_name: tips-shadow-builder-cl
     depends_on:
-      builder:
+      shadow-builder:
         condition: service_started
     profiles:
       - builder
@@ -130,18 +130,18 @@ services:
     env_file:
       - .env.docker
     environment:
-      # ENGINE CONFIGURATION (builder-specific, playground mode uses 4444)
-      OP_NODE_L2_ENGINE_RPC: http://builder:4444
-      # Enable sequencer mode so builder-cl generates payload attributes
+      # ENGINE CONFIGURATION (shadow-builder-specific, playground mode uses 4444)
+      OP_NODE_L2_ENGINE_RPC: http://shadow-builder:4444
+      # Enable sequencer mode so shadow-builder-cl generates payload attributes
       # Using placeholder key so shadow builder blocks will be rejected by network
       OP_NODE_SEQUENCER_ENABLED: "true"
       OP_NODE_SEQUENCER_L1_CONFS: "0"
       OP_NODE_VERIFIER_L1_CONFS: "0"
       OP_NODE_P2P_SEQUENCER_KEY: "0000000000000000000000000000000000000000000000000000000000000001"
 
-  builder:
-    image: tips-builder:latest
-    container_name: tips-builder
+  shadow-builder:
+    image: op-rbuilder:latest
+    container_name: tips-shadow-builder
     depends_on:
       postgres:
         condition: service_healthy
@@ -154,7 +154,7 @@ services:
       - ~/.playground/devnet/jwtsecret:/data/jwtsecret:ro
       - ~/.playground/devnet/rollup.json:/data/rollup.json:ro
       - ~/.playground/devnet:/playground
-    command: ["node", "--datadir", "/playground/tips-builder"]
+    command: ["node", "--datadir", "/playground/tips-shadow-builder"]
     env_file:
       - .env.docker
     extra_hosts:

justfile

@@ -159,7 +159,7 @@ playground-env: sync-env
 
     echo "✓ Builder Playground environment configured successfully"
 
-# Start builder stack (builder-cl + builder, simulator-cl + simulator)
+# Start shadow builder stack (shadow-builder-cl + shadow-builder, simulator-cl + simulator)
 start-builder: playground-env (start-all "builder")
 
 ### BUILDER COMMANDS ###
@@ -290,13 +290,13 @@ _build-rbuilder-common temp_dir tag revision:
     rm -f /tmp/tips-workspace-deps.txt
 
     echo "Building docker image (revision: $REVISION)..."
-    docker build -t "tips-builder:$TAG" .
-    
+    docker build -t "op-rbuilder:$TAG" .
+
     # Tag with git revision
-    docker tag "tips-builder:$TAG" "tips-builder:$REVISION"
-    
+    docker tag "op-rbuilder:$TAG" "op-rbuilder:$REVISION"
+
     # Tag as latest for convenience
-    docker tag "tips-builder:$TAG" tips-builder:latest
-    
-    echo "✓ Built tips-builder:$TAG (revision: $REVISION)"
-    docker images | grep tips-builder
+    docker tag "op-rbuilder:$TAG" op-rbuilder:latest
+
+    echo "✓ Built op-rbuilder:$TAG (revision: $REVISION)"
+    docker images | grep op-rbuilder