Repository navigation
Conversation
Contributor
Author
|
ethereum parity done too. my own wallet backfilled from genesis, rotki with only the nest in the indexer order decoded the same events as rotki with etherscan, every field identical. same check on gnosis against blockscout and etherscan matched as well. |
This was referenced Oct 15, 2026
Open
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #13375 +/- ##
========================================
Coverage 81.49% 81.50%
========================================
Files 3702 3703 +1
Lines 155772 155751 -21
Branches 23905 23905
========================================
- Hits 126953 126943 -10
+ Misses 22082 22076 -6
+ Partials 6737 6732 -5
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
cargopete
force-pushed
the
pete/nuthatch-transactions
branch
2 times, most recently
from
October 27, 2026 09:25
783c61f to
6b1f826
Compare
Contributor
Author
|
@LefterisJP small nudge on this one, it's the transactions only adapter we talked about, nothing in eth2. the validators PR can wait if you'd rather take this first. anything you'd want changed before you go through it? |
…anding all of it to the next indexer
… no block of its side
cargopete
force-pushed
the
pete/nuthatch-transactions
branch
from
November 11, 2026 20:25
ae694c3 to
5158c1d
Compare
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.
I closed #13342 after @LefterisJP suggested a smaller first step, and this is that step. It adds a self-hosted nuthatch nest as an EVM indexer for transactions only: normal, internal and token transactions, plus the block lookups the sync already makes. It is built on the existing EtherscanLikeApi the way Routescan is, offered on every EVM chain, and asked only where a chain's indexer order names it.
A nest answers only what it has fully indexed and refuses everything else by name. Every refusal falls through to the next indexer for that query, and the nest is never dropped from a chain. The one change outside the adapter is two lines in node_inquirer.py, so a nest that cannot look up blocks by timestamp is not treated as stale for that chain's transactions. rotki registers the accounts it tracks with the nest in the background; it does not unwatch removed ones yet.
Against a real nest with Nuthatch alone for Gnosis, rotki produced the same 82 history events as with Blockscout and Etherscan.
Validators, withdrawals, unwatching and the general range fixes are left out on purpose. #13372 sketches the indexer abstraction; if you take it, I will move this onto it.