Merge branch 'main' into mm-builderhub-mock-proxy

Author: MoeMahhouk

.github/workflows/docker-utils-release.yaml

@@ -7,6 +7,12 @@ on:
   push:
     branches:
       - main
+    paths:
+      - 'cl-proxy/**'
+      - 'mev-boost-relay/**'
+      - 'go.mod'
+      - 'go.sum'
+      - 'Dockerfile'
 
 jobs:
   docker:

examples/op-stack-rollup-boost.md

@@ -2,13 +2,13 @@
 
 This example shows how to deploy an Op Stack with rollup-boost with an external block builder (op-reth).
 
-First, download the op-reth binary:
+First, download the `op-reth` binary:
 
 ```bash
 $ go run main.go artifacts op-reth
 ```
 
-This will download the op-reth binary and save it under `$HOME/.playground/op-reth-v1.3.1`.
+This will download the op-reth binary and save it under `$HOME/.playground/op-reth-v1.3.12`.
 
 Second, we can deploy the Op Stack with rollup-boost:
 
@@ -35,7 +35,10 @@ The `--external-builder` flag is used to specify the URL of the external block b
 Third, we can start the `op-reth` binary as the external block builder:
 
 ```bash
-$ $HOME/.playground/op-reth-v1.3.1 node --authrpc.port 4444 --authrpc.jwtsecret ./output/jwtsecret --chain ./output/l2-genesis.json --datadir /tmp/builder --disable-discovery --port 30333 --trusted-peers enode://3479db4d9217fb5d7a8ed4d61ac36e120b05d36c2eefb795dc42ff2e971f251a2315f5649ea1833271e020b9adc98d5db9973c7ed92d6b2f1f2223088c3d852f@127.0.0.1:30304
+$ $HOME/.playground/op-reth-v1.3.12 node --http --http.port 2222 \
+    --authrpc.addr 0.0.0.0 --authrpc.port 4444 --authrpc.jwtsecret $HOME/.playground/devnet/jwtsecret \
+    --chain $HOME/.playground/devnet/l2-genesis.json --datadir /tmp/builder --disable-discovery --port 30333 \
+    --trusted-peers enode://3479db4d9217fb5d7a8ed4d61ac36e120b05d36c2eefb795dc42ff2e971f251a2315f5649ea1833271e020b9adc98d5db9973c7ed92d6b2f1f2223088c3d852f@127.0.0.1:30304
 ```
 
 The command above starts op-reth as an external block builder with the following key parameters:
@@ -44,7 +47,7 @@ The command above starts op-reth as an external block builder with the following
 - `--authrpc.jwtsecret`: Uses the JWT secret generated during Op Stack deployment
 - `--trusted-peers`: Connects to our Op Stack's EL node using the deterministic enode address
 
-Once op-reth is running, it will connect to the Op Stack and begin participating in block building. You can verify it's working by checking the logs of both the sequencer and op-reth for successful block proposals.
+Once `op-reth` is running, it will connect to the Op Stack and begin participating in block building. You can verify it's working by checking the logs of both the sequencer and op-reth for successful block proposals.
 
 ## Internal block builder
 

internal/components.go

@@ -542,7 +542,7 @@ func (o *OpReth) ReleaseArtifact() *release {
 		Name:    "op-reth",
 		Repo:    "reth",
 		Org:     "paradigmxyz",
-		Version: "v1.3.4",
+		Version: "v1.3.12",
 		Arch: func(goos, goarch string) string {
 			if goos == "linux" {
 				return "x86_64-unknown-linux-gnu"