RE Polygon: “The main reason we sourced this data from another party is that,
due to Polygon’s block size and rate, simulating and tracing transactions can
be executed at only slightly faster than the network speed, making this a very
expensive process (note: event-based tracing significantly improves this process,
but it still remains expensive).” This could be resolved by having multiple servers doing different sequences of blocks couldn’t it @Quintus?
RE Arbtrium: “Unfortunately, at this time, Arbitrum does not provide tracing of transactions.” I think they now do, it would be interesting to use the mev-inspect-py fork there to conduct some research.