Repository navigation
feat: Remove KAPI - #215
Open
vgorkavenko wants to merge 4 commits into
Open
vgorkavenko wants to merge 4 commits into
vgorkavenko wants to merge 4 commits into
Conversation
vgorkavenko
force-pushed
the
feat/remove-kapi
branch
from
October 30, 2026 12:09
b2edc97 to
d307d6e
Compare
vgorkavenko
marked this pull request as ready for review
October 30, 2026 12:48
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.
Why Multicall3 instead of JSON-RPC batch
aggregate3is oneeth_call: indexing all mainnet keys takes 26 calls instead of ~4,070.aggregate3succeeds or fails as a whole, so it is retried as one request, and all its calls run on one node at the pinned block.