Repository navigation
feat(scaling): categorize limits and scale the ladder to its largest value - #220
Merged
Merged
Conversation
…value Split each What breaks first limit into a category (DA, Execution, Disk, RPC) and the limit itself. Show sequencer, validators and proof node as separate execution rows instead of merging them, and split TEE proving (Execution) from RPC under sync (RPC). End the shared ladder and table scale at the largest value shown, so ceilings above the gas limit, such as DA swaps and the full-node disk, draw past its line instead of clipping at it. The gray proven band now stops at the proven mark, and the axis-end label is dropped because a labeled point always ends the bar.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Collaborator
✅ Heimdall Review Status
|
wlawt
approved these changes
Nov 2, 2026
This branch was successfully deployed
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
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.
Summary
Makes the Scaling page's limits easier to scan and fixes ceilings that were drawn at the gas limit when they sit above it.
What breaks first
DA · Payments (B20)andDisk · full node.corematching in the subsystem cards, which now follow the table order.Scale
The ladder and the table share one scale, which now ends at the largest value shown instead of
max(proven, gas limit). When proven equalled the 200 Mgas/s gas limit, every higher ceiling (DA · swaps at 238, full-node disk at ~537) was pinned to the right edge of the ladder and clipped at the gas-limit line in the table.The gray proven band stops at the proven mark, so the bar past it no longer reads as proven.
The axis-end label is dropped: the bar now always ends at a labeled point.
The ladder and the table share one scale, which now ends at the largest value shown instead of
max(proven, gas limit). When proven equalled the gas limit, every higher ceiling (for example DA · swaps or the full-node disk) was pinned to the right edge of the ladder and clipped at the gas-limit line in the table.Synthetic snapshot without bench data, not live network data. Without bench data the gas limit is the largest value, so the bar ends there.
Test plan
npm test: 72 files, 563 tests passed.npm run typecheckand ESLint onapp/scaling: passed./scalinglocally against live bench results: every ceiling gets a tick, ceilings above the gas limit draw past its line, and the categories render as above.