Repository navigation
Conversation
Contributor
|
I see you updated files related to
|
Contributor
|
✅ No conflicts with other open PRs targeting |
getCapabilities, getDONs and getNodes were each read as a single page of 1024 entries, so one eth_call's gas grows with the registry size. Read in fixed-size pages instead to stay well below RPC eth_call gas caps. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bolekk
force-pushed
the
cre-7121-registrysyncer-v2-pagination
branch
from
November 18, 2026 23:26
8e6080e to
893c003
Compare
bolekk
marked this pull request as ready for review
November 18, 2026 23:27
bolekk
force-pushed
the
cre-7121-registrysyncer-v2-pagination
branch
from
November 18, 2026 23:29
be02676 to
ee88e98
Compare
Records how many capabilities, DONs and nodes were read on-chain per sync, so read counts can be compared against on-chain totals. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bolekk
force-pushed
the
cre-7121-registrysyncer-v2-pagination
branch
from
November 18, 2026 23:38
ee88e98 to
37174b1
Compare
ilija42
approved these changes
Nov 19, 2026
This branch has not been 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.
The v2 registry syncer reads
getCapabilities,getDONsandgetNodesas a single 1024-entry page, so the gas used by eacheth_callgrows with the registry. On prod mainnet todaygetDONstakes ~5.75M gas for 13 DONs, and each single-capability "virtual DON" adds ~157k. With shard-1 and later shards, a NOP RPC with a loweredeth_callgas cap would start failing syncs, and that node would stop seeing registry updates.platform_registrysyncer_registry_entries{type=capabilities|dons|nodes}with the number of entries read per sync.Deployment Validation
platform_registrysyncer_registry_entriesmatches on-chain counts (getDONs/getNodes/getCapabilitieslengths) on every node,platform_registrysyncer_sync_failuresstays flat, andplatform_launcher_capability_hosting_donsis unchanged vs before the upgrade.🤖 Generated with Claude Code