Skip to content
This repository was archived by the owner on Dec 22, 2025. It is now read-only.

Commit e2f165d

Browse files
author
Bloxster
committed
added op-node
1 parent 964f2d3 commit e2f165d

File tree

2 files changed

+14
-0
lines changed

2 files changed

+14
-0
lines changed

src/SUMMARY.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -40,6 +40,7 @@
4040
- [TxPool](advanced/txpool.md)
4141
- [Sentry](advanced/sentry.md)
4242
- [Downloader](advanced/downloader.md)
43+
- [Running an Op-node](op-node.md)
4344
- [TLS Authentication](advanced/tls-authentication.md)
4445
- [Perfomance Tricks](advanced/performance.md)
4546

src/op-node.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
# Running an Op-Node Alongside Erigon
2+
3+
To run an op-node alongside Erigon, follow these steps:
4+
5+
1. **Start Erigon with Caplin Enabled**:
6+
If Caplin is running as the consensus layer (CL), use the `--caplin.blobs-immediate-backfill` flag to ensure the last 18 days of blobs are backfilled, which is critical for proper synchronization with the op-node, assuming you start from a snapshot.
7+
```bash
8+
./build/bin/erigon --caplin.blobs-immediate-backfill
9+
```
10+
2. **Run the Op-Node**:
11+
Configure the op-node with the `--l1.trustrpc` flag to trust the Erigon RPC layer as the L1 node. This setup ensures smooth communication and synchronization.
12+
13+
This configuration enables the op-node to function effectively with Erigon serving as both the L1 node and the CL.

0 commit comments

Comments
 (0)