Open kevinfaveri opened 6 days ago
This is a great idea something I would love to add alongside as if executed well you can in turn track tons of stuff this way. I also want to add factory contract monitoring.
The first thing I would like to define here is the rindexer.yaml and how it would look this allows us to see how people will set it up! Is your pure usecase just doing native transactions or have you other thoughts? Asking as I can imagine this being useful for address filtering, gas based filtering, internal transactions, contract creations, state variable updates and well tons more but I defo only want to add the most important things first due to scope creep lol
The core thing rindexer does well is do everything for you so do want to make sure we get the interface spot on. In your case though you would want to write the handler yourself using the rindexer rust project right?
In essence, I want to be able to have a block listener handler that uses
debug_traceBlockByNumber
or something else so I can track in / outs of balances. I'm happy to help sponsor the work.For reference, this implements this and account listeners: https://github.com/ponder-sh/ponder/pull/1210/files I woulndt go that far, as long as it indexes blocks using debug_traceBlockByNumber and send it to a handler, on the handler a logic to track in / out of ETH native balance changes in the block can be written
The reasoning is that would allow rindexer to fully index tokens and native transfers, a feature it is lacking at the moment.