mev-inspect collaboration

Given the limited capacity we have, it’s best to push mev-inspect-py and the dashboards depending on it to a contributor / community maintained work stream. We would like to give a grant for the grantee to complete the following tasks in the next 2-3 months (in order of priority):

• Debug and fix critical bugs that stop the listener from moving forward
  • Currently, we modified it (only in prod) to skip over blocks with errors as a hacky fix but ideally we fix issues that cause it to halt in the first place
• Ensure mev-inspect data <> dune export tool works
  • Currently, as long as the listener is running, it exports that data into dune’s s3 but like mentioned above, if it stops so does the export tool
  • Create a dashboard on Dune that looks similar to mev-explore as an example to showcase how the community can use the data to create dashboard. (we will deprecate mev-explore after this, and point any post-merge graphs to this Dune dashboard)
• Review and resolve existing https://github.com/flashbots/mev-inspect-py/issues
• Add extra DEXs (or any other useful protocol classifiers) to increase the types of mev it can track
• Update mev-inspect-py docs to GitHub readme file to improve instructions
• Make a non-kubernetes based version if you find a viable alternative architecture that is performant
  • For context, we chose kube after switching from mev-inspect-rs to mev-inspect-py because despite python being slow, we could spin up and wind down multiple pods (max db connections is ~100 so capped there) to get large backfill ranges done in days vs weeks