docs: add specialized op-node topology notice#20192
Merged
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
jelias2
reviewed
Apr 21, 2026
jelias2
reviewed
Apr 21, 2026
Recommend migrating from homogeneous op-node fleets to a specialized topology where a small deriver tier (behind a consensus-aware proxyd) serves the safe chain to a scalable pool of light op-node instances via --l2.follow.source. Covers the benefits (L1 utilization reduction, performance specialization, asymmetric scaling, lower cost for future rollouts like interop), a recommended HA three-tier layout, and guidance for node and chain operators (including sequencers). Made-with: Cursor
Co-authored-by: Jacob Elias <19310318+jelias2@users.noreply.github.com>
ZakAyesh
force-pushed
the
docs/specialized-node-topology-notice
branch
from
47b46fd to
bf627bd
Compare
Wazabie
approved these changes
Apr 22, 2026
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
5 participants
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.
Recommend migrating from homogeneous op-node fleets to a specialized topology where a small deriver tier (behind a consensus-aware proxyd) serves the safe chain to a scalable pool of light op-node instances via --l2.follow.source. Covers the benefits (L1 utilization reduction, performance specialization, asymmetric scaling, lower cost for future rollouts like interop), a recommended HA three-tier layout, and guidance for node and chain operators (including sequencers).