feat: make max-outbound-peers configurable via MAX_OUTBOUND_PEERS env var

[erhnysr]

Summary

Makes the Reth --max-outbound-peers flag configurable via a MAX_OUTBOUND_PEERS environment variable instead of being hardcoded to 100.

Problem

Operators experiencing persistent Send Queue full gossipsub warnings (#1063) need to increase the outbound peer limit to resolve the issue. However, --max-outbound-peers=100 was hardcoded in reth-entrypoint with no way to override it without modifying the entrypoint script directly.

Changes

• reth/reth-entrypoint: Replace hardcoded --max-outbound-peers=100 with $MAX_OUTBOUND_PEERS (default: 100, preserving existing behaviour)
• .env.mainnet and .env.sepolia: Document MAX_OUTBOUND_PEERS with usage guidance and reference to v0.15.5 Persistent "Send Queue full" in gossipsub despite low peer count and idle bandwidth #1063

Behaviour

No change for existing operators — default remains 100. Operators who need more peers can now set:

MAX_OUTBOUND_PEERS=250 docker compose up

Closes #1063 (partially)

[cb-heimdall]

🟡 Heimdall Review Status

Requirement	Status	More Info
Reviews	🟡 0/1	Denominator calculation Show calculation 1 if user is bot 0 1 if user is external 0 2 if repo is sensitive 0 From .codeflow.yml 1 Additional review requirements Show calculation Max 0 0 From CODEOWNERS 0 Global minimum 0 Max 1 1 1 if commit is unverified 0 Sum 1

[erhnysr]

Rebased on latest main (post #1090)

This PR has been rebased onto the current main branch. The changes target the new unified execution-entrypoint (which replaced reth/reth-entrypoint in #1090).

What changed:

File	Change
execution-entrypoint	MAX_OUTBOUND_PEERS="${MAX_OUTBOUND_PEERS:-100}" added to var block; --max-outbound-peers=100 → --max-outbound-peers="$MAX_OUTBOUND_PEERS"
.env.mainnet / .env.sepolia	New PEER LIMITS section documents the variable with a link to #1063

Default behaviour is unchanged — operators who don't set MAX_OUTBOUND_PEERS get 100 as before. Those hitting the Send Queue full issue can now simply add MAX_OUTBOUND_PEERS=250 to their .env file.

Happy to address any review feedback.

[erhnysr]

Still relevant and up to date. Happy to rebase if needed.

[erhnysr]

Hi! Checking in on this PR — makes max-outbound-peers configurable via MAX_OUTBOUND_PEERS env var, useful for operators tuning peer connectivity. Happy to adjust based on feedback.

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.