feat(eventindexer): Timeseries data indexing + refactor to taiko-client/relayer CLI approach and architecture

[cyberhorsey]

This PR refactors eventindexer similarly to the relayer and taiko-client architectures, and adds a new subcommand, generator, which runs as a Cronjob to generate time-series chart data from the indexed database data.

deployed to internal testnet already, working on blockscout-frontend to integrate changes into displayable time-series charts in next PR.

Missing some tests for new code, will also add in next PR or assign to Roger to get familiar with this repo.

time-series data indexed:
ACCOUNTS

1. accounts growth
2. new accounts per day

PROPOSING

1. total unique proposers
2. unique proposers per day
3. proposeBlock tx per day
4. total proposeBlock tx per day

PROVING

1. total unique provers
2. unique provers per day
3. proveBlock tx per day
4. total proveBlock tx -

TRANSACTIONS

1. total transactions
2. transactions per day

BLOCKS

1. total blocks
2. blocks per day

CONTRACTS

1. total deployed contracts
2. deployed contracts per day

BRIDGE

1. bridge messages sent per day
2. total bridge messages sent

This should be good enough for the first batch of charts, and we can add more later.

All charts are available via the format https://eventindexer.*.taiko.xyz/chart/chartByTask?task=total-transactions&start=2023-08-07&end=2023-09-09

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

2 Ignored Deployments

Name	Status	Preview	Comments	Updated (UTC)
bridge-ui-v2	⬜️ Ignored (Inspect)	Visit Preview		Sep 10, 2023 5:50am
bridge-ui-v2-internal	⬜️ Ignored (Inspect)	Visit Preview		Sep 10, 2023 5:50am

[openzeppelin-code]

feat(eventindexer): Timeseries data indexing + refactor to taiko-client/relayer CLI approach and architecture

Generated at commit: 2d0ea581de95fa1f8d7b9943e2348cfcf2844b19

🚨 Vulnerabilities Summary

Process	Issues	Results
Contract Inspector	note low critical Total	23 5 1 29
Dependency Checker	Total	0

---

For more details view the full report in OpenZeppelin Code

[dantaik]

Jeff, when this PR is ready, could you please briefly describe what you are trying to build?

[cyberhorsey]

Jeff, when this PR is ready, could you please briefly describe what you are trying to build?

I added some comments. This is essentially indexing data for displaying time-series statistics via charts instead of our primitive status page, for the blockscout-frontend repo to display, as well as a generator Cron job subtask that will take this indexed data and produce meaningful, easy-to-plot chart data, which is served via http.