Add Ironflow root peer (Tokyo) - #159
Open
eternaut1 wants to merge 1 commit into
Open
Conversation
eternaut1
force-pushed
the
add-ironflow-root-peer
branch
from
July 29, 2026 18:26
ed8b0af to
b7f44b4
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adding Ironflow's non-validator root peer to the Mainnet table.
We run a dedicated bare-metal non-validator in Tokyo (same metro as HL consensus, 2ms to nearest peer) powering ironflow.sh — 24/7 monitored (Prometheus + auto-recovery watchdogs), port 4001 open, stable static IP, capacity for inbound gossip peers.
Happy to coordinate reserved peering with other operators — support@ironflow.sh.