op-reth: --trusted-peers from client_staticpeers; katana official EL peer (5 composes) #101
Open
claude
wants to merge 1 commits from
katana-el-trusted-peer into main
pull from: katana-el-trusted-peer
merge into: :main
:main
:katana-el-trusted-peer
:vupd/5488-tacchaind-v1.6.4
:vupd/5474-reth-v2.6.0
:issue-5365
:issue-5358
:issue-5360
:fix/linea-validate-gas-price-optout
:vupd/5309-plasma-trusted-peers-object-shape
:bump-morph-to-0-6-3
:fix/plasma-mainnet-observer-p2p
:issue-5201
:wedge-cronos-mainnet-2026-09-23
:issue-5049
:vupd-avalanche-state-sync
:issue-4590
:issue-4519
:issue-4104
:zircuit-conduit-mainnet
:issue-3492
:zerog-init-guard-config-volume
:zerog-tarball-layout-tolerant
:issue-2834
:fix-zerog-release-tag-resolution
:issue-3182
:issue-3181
:issue-3162
:issue-3056
:issue-2833
:issue-2952
:issue-2909
:issue-2880
:issue-2851
:issue-2776
:issue-2692
:issue-2615
:issue-2155
:issue-2048
:issue-1940
:maru-version-observability
:issue-1124
:edge-prefix-sg-177-54-154
:982
:969
:issue-923
:issue-898
:issue-848
:issue-502
:issue-136
:issue-63
:vibe
:jules_wip_13535632906362438955
:blast-ethereum-archive-proxy
:eth_proxy
:erigon-polygon
:harmony-validator
:bsc
:deprecated-main
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Generated assets for vibe-node PR
katana-el-trusted-peer(follow-up to #100 / vibe-node #5771).--trusted-peers=enode://eac04d7f…@35.197.34.76:30303— Conduit's official replica EL peer (katana-network/network-configsmainnet/op-reth/katana-op-reth.sh). Canary de-25 sat at 0 EL peers for 30 min after #5771 because custom-genesis chains have no built-in op-reth bootnodes.client_staticpeersnow reach op-reth (previously silently dropped by the template).🤖 Generated with Claude Code
https://claude.ai/code/session_01RzxemENdcZBCxdGrzXiFvS
merge-bot (del-018): NOT merging - this PR edits generated compose files; the next deploy-compose-repo regeneration would revert it. Re-land the change in vibe-node (context.yml / templates). Classification: edits generated compose file(s) ['op/reth/hashkeychain-mainnet-op-reth-pruned-trace--kona.yml', 'op/reth/hashkeychain-mainnet-op-reth-pruned-trace.yml'] - belongs in vibe-node
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.