Willian Mitsuda
Willian Mitsuda
you just reminded me of a related improvement I'd like to do, I'll open a discussion for that. Maybe this one could be part of the solution.
https://github.com/otterscan/otterscan/discussions/1324
Probably will have to break down this issue into many smaller improvements because I see many possible refactorings here. One that I have in my mind is the error detection,...
assigning it to you @0xMimir , feel free to ask any questions.
totally up for it if you can figure out how to optimize/reorg the routing/rendering waterfall :)
Not for now, but I'm working on some indexes to do exactly what you are asking for. So, that'll be possible soon, but I'll required some extra disk space/sync time.
will leave this open to reference it when this feature gets released.
yes, it's very resource intensive. I'm almost releasing the first indexer prototype, but need to optimize the holder calculation, it's taking over 10-11 hours in my machine, I think it...
just for the record, looping through all token transfers on the fly doesn't scale well because (at least on erigon2) it requires reading logs from the disk, each log is...
yes, that's it. just giving you a heads up, I already implemented that for erigon 2. what the original issue asked is the inverse: giving a token, what are the...