Skip to content

Update Lisk Sepolia bootnode + static-peer values (PLAT-702) #136

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sameersubudhi merged 2 commits into from
Jul 30, 2026
Merged

Update Lisk Sepolia bootnode + static-peer values (PLAT-702) #136

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b274649
Update Lisk Sepolia bootnode + static-peer values (PLAT-702)
sameersubudhi Jul 30, 2026
9189c67
Drop --l1.rpckind from op-node source-run example
sameersubudhi Jul 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions .env.sepolia
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,11 +23,11 @@ OP_NODE_METRICS_ENABLED=true
OP_NODE_METRICS_PORT=7300
OP_NODE_NETWORK=lisk-sepolia
# OP_NODE_P2P_AGENT=lisk
OP_NODE_P2P_BOOTNODES=enr:-Iu4QI5BdaTmfMhNKXd-vSniNRSCXk-a3m3nQbe9TCV3puGtCr6FvX6-Vr0Uvx4tYVilGCIYdQNf6fK8O2MKxVqjYJ8BgmlkgnY0gmlwhCKN6PiJc2VjcDI1NmsxoQLBQIaRwlvNxrRKcGtxKmh4JS_orkawS44D4KIORICoi4N0Y3CCIyuDdWRwgiMr
OP_NODE_P2P_BOOTNODES=enr:-Iu4QH2cj2VS7A3p8v8VUj7YYOOD2hHSZR8wKZs9JXEjJuNFYzJLXYoQa_oRp0lAbkg81Zmu4Fw2OkywCpXz6TrcaH4BgmlkgnY0gmlwhCIH63CJc2VjcDI1NmsxoQLBQIaRwlvNxrRKcGtxKmh4JS_orkawS44D4KIORICoi4N0Y3CCIyuDdWRwgiMs
OP_NODE_P2P_LISTEN_IP=0.0.0.0
OP_NODE_P2P_LISTEN_TCP_PORT=9222
OP_NODE_P2P_LISTEN_UDP_PORT=9222
OP_NODE_P2P_STATIC=/ip4/34.34.122.138/tcp/9003/p2p/16Uiu2HAmS3JEmKYY3Wwift6FJKZxYDDnZtCjfryyeJBYT1DWH82T,/ip4/34.147.94.25/tcp/9003/p2p/16Uiu2HAmJBA5XJiHRnreCBDdt3KZusQXG7ECRYoLCBxTdokp236w,/ip4/34.34.117.160/tcp/9003/p2p/16Uiu2HAkythtCa4TQvDbKFCXY2ZxKDsPNBNbiXbapzb1EZYw717Q
OP_NODE_P2P_STATIC=/ip4/34.141.227.187/tcp/9003/p2p/16Uiu2HAmScxYL55DumTayA9n3jN1Sg1DVs4wAhFJ18za5DZqgL9z
OP_NODE_RPC_ADDR=0.0.0.0
OP_NODE_RPC_PORT=9545
OP_NODE_SNAPSHOT_LOG=/tmp/op-node-snapshot-log
Expand All @@ -43,5 +43,5 @@ OP_NODE_ROLLUP_LOAD_PROTOCOL_VERSIONS=true
# NOTE: Snap sync requires reachable peers via the discovery protocol. If no bootnodes/peers are available, sync may stall or fail to start. We recommend running a full or archive node for production.
# To enable snap sync, uncomment and set the env vars below:
# OP_NODE_SYNCMODE=execution-layer
# OP_RETH_BOOTNODES=enode://c1408691c25bcdc6b44a706b712a6878252fe8ae46b04b8e03e0a20e4480a88b4e36035cfeb598bba4bd8a15862a7b36888dc7152d98c1c8bb6bd0d956fb08f6@34.141.232.248:9004
# OP_RETH_TRUSTED_PEERS=enode://4ca62aca0ee190bd489656eaab3b2bafcf620585fba868c021faa8e6283f4bcb002e43cec05cb137276548e8398b2c9bc010fefc93f539f1b8a1c538edfaf40a@34.34.28.137:30303,enode://577e069d969479802b27cb436715db9487841b789b898a1c56e07be84ee5ce7e2d10c03c17d675713c79b20254c5b74d0459de409f22835aedb4d75f4653067d@34.34.28.137:30304,enode://9ba49c519d8d3536aeb1d6c00bda9b94b91ed1579fc07bb64b8327669a3fdc076509229de07bba22f1836bf25d239f1bc3c17f9e4cffe6a115579a3c930df639@34.34.28.137:30403,enode://301d86365a63e833509dc0ef7381fdbf81556555c7bdd1fc29e9e6f852df2264ab287ecc7556d8b1ae39959027cd578401c8657e289f86ae56b0a0e695c00e53@34.34.28.137:30404
# OP_RETH_BOOTNODES=enode://c1408691c25bcdc6b44a706b712a6878252fe8ae46b04b8e03e0a20e4480a88b4e36035cfeb598bba4bd8a15862a7b36888dc7152d98c1c8bb6bd0d956fb08f6@34.7.235.112:9004
# OP_RETH_TRUSTED_PEERS=enode://97fe34b40180d4a47e6b7b0ad3185f8947ae67e2c52ba5cae579009a652d496cc30dabea09569cfc2f2fa37e24c6ea5604349d1959b044e0ce8852aa0202d65b@34.7.94.39:30403,enode://b34efc23b694e673bc621a853faba30fc119c86a6d9eff3d4a4ec994e37c3b09d98f21c9ae56b5e98cb8efcb28e7ce6800ca8624f29c1daea73da6eb711c5487@34.7.94.39:30404,enode://08085e3a833d33ae9eb01c88aae0a351f2b34e1f479d7a97fc120405f6e643c90ae429280a3173f7b65ef0962799a793d5007fbfe20d8d464cbdce3d54f67ccc@34.7.94.39:30303,enode://0981c0ee022fc91ce48cb36b4ed96cb35122e4bb35a67b6c173a5e115c66e9f102ef043db13d94e72b00a82d0c066d55fb1dee61ed36084f507ae662e3197963@34.7.94.39:30304
6 changes: 3 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ We recommend you the following hardware configuration to run a Lisk L2 node:
- a minimum of 16 GB RAM (32 GB recommended)
- a locally attached NVMe SSD drive
- adequate storage capacity to accommodate both the snapshot restoration process (if restoring from snapshot) and chain data, ensuring a minimum of (2 \* current_chain_size) + snapshot_size + 20%\_buffer
- if running with docker, please install Docker Engine version [27.0.1](https://docs.docker.com/engine/release-notes/27.0/) or higher
- if running with docker, please install Docker Engine version [27.0.1](https://docs.docker.com/engine/release-notes/27/) or higher

**Note:** If utilizing Amazon Elastic Block Store (EBS), ensure timing buffered disk reads are fast enough to avoid latency issues alongside the rate of new blocks added to Lisk during the initial synchronization process; `io2 Block Express` is recommended.

Expand Down Expand Up @@ -157,7 +157,6 @@ Refer to the `reth` configuration [documentation](https://reth.rs/cli/reth/node)
./bin/op-node \
--network=$OP_NODE_NETWORK \
--l1=$OP_NODE_L1_ETH_RPC \
--l1.rpckind=$OP_NODE_L1_RPC_KIND \
--l1.beacon=$OP_NODE_L1_BEACON \
--l2=ws://localhost:8551 \
--l2.jwt-secret=PATH_TO_JWT_TEXT_FILE
Expand Down Expand Up @@ -232,7 +231,8 @@ Please follow the steps below:
By default, the Lisk node runs in full sync mode. To enable snap sync (faster initial sync by fetching state from peers), uncomment the snap-sync block in your `.env.*` file:

- `OP_NODE_SYNCMODE=execution-layer` — instructs `op-node` to defer block sync to the execution client.
- `OP_RETH_BOOTNODES` — comma-separated enode URLs used to bootstrap peer discovery. Snap sync needs P2P connectivity beyond the sequencer, so at least one working bootnode is required.
- `OP_RETH_BOOTNODES` — comma-separated enode URLs that seed `op-reth` peer discovery (`--bootnodes`; the Lisk Sepolia EL bootnode requires discv5). Snap sync needs P2P connectivity beyond the sequencer, so at least one working bootnode is required.
- `OP_RETH_TRUSTED_PEERS` — comma-separated enode URLs added as static peers (`op-reth --trusted-peers`) and dialed directly, independent of the discovery protocol.

> **Note**:
> For `op-reth`, the docker entrypoint normally runs with `--disable-discovery`, which disables the discovery protocols (discv4/discv5/DNS) so the node won't automatically find peers. When `OP_RETH_BOOTNODES` is set, the entrypoint automatically drops `--disable-discovery` because reth's bootnodes only take effect via the discovery protocol — they are no-ops when discovery is turned off. If you build and run `op-reth` from source instead of via docker, remove `--disable-discovery` from your command line when passing `--bootnodes`.
Expand Down
Loading