Update Lisk Mainnet OP_RETH_TRUSTED_PEERS (PLAT-735)

[sameersubudhi]

Summary

The op-reth trusted-peer node keys for Lisk Mainnet were rotated. Updates the git-tracked values so operators using snap sync dial the new peers. Mainnet only — .env.sepolia untouched.

• Linear: PLAT-735

.env.mainnet

#	Key	Change
1	# OP_RETH_TRUSTED_PEERS	four new node keys; IPs/ports unchanged (34.147.89.221:30303/30304/30403/30404); stays commented (snap-sync example)

No README change — --trusted-peers is already documented in the Snap sync section.

🤖 Generated with Claude Code

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 41d84d6c-a538-416d-9181-669514ac8376

📥 Commits

Reviewing files that changed from the base of the PR and between 5c67607 and 8827b8c.

📒 Files selected for processing (1)

• .env.mainnet

Included review availability: 3 reviews are currently available. Based on recent review activity, included reviews refill at 5 per hour.

---

📝 Walkthrough

Walkthrough

The commented mainnet snap-sync configuration updates OP_RETH_TRUSTED_PEERS with four new enode peer URLs.

Changes

Mainnet configuration

Layer / File(s)	Summary
Update trusted-peer configuration .env.mainnet	The commented OP_RETH_TRUSTED_PEERS value now contains four updated enode URLs.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 8827b

This PR makes a localized update to the commented Mainnet trusted-peer example, with no actionable merge-blocking risk remaining beyond normal checks and review.

Suggested reviewers: nazgolze

Poem

I’m a rabbit with peers in a row,
Four fresh enodes ready to go.
Snap-sync hops with a confident cheer,
Through mainnet paths, crisp and clear.
🐇✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description explains the implementation but omits the required problem and testing sections from the repository template.	Add the required “What was the problem?” and “How was it tested?” sections, including issue resolution and test details.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly identifies the main change and includes the relevant tracking identifier.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch plat-735-lisk-node-update-lisk-mainnet-op_reth_trusted_peers-gelato

---

_{Comment @coderabbitai help to get the list of available commands.}