Remove tx trace generation & storage from ingestion engine

[m-Peter]

Currently, as part of the EVM event ingestion engine, we replay each transaction and we also generate a basic set of traces, which are stored in a dedicated storage index. This does add some overhead to the ingestion engine, and it seems that the traces we generate, are also not used very frequently.
We could drop this part entirely, to increase the throughput of the ingestion engine.

Tx trace generation & storage: https://github.com/onflow/flow-evm-gateway/blob/main/services/ingestion/engine.go#L296-L308 .

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Related Issues

• Investigate feasibility of storing EVM registers on transaction level #729
• Track time taken to fully ingest EVM blocks #751
• Add metric to count the number of queued single-tx EOAs #851

🔗 Related PRs

#281 - Ingest and index transaction traces [merged]
#465 - Optimize traces engine to handle empty blocks [merged]
#615 - Add traces backfill option [merged]

👤 Suggested Assignees

• m-Peter
• devbugging
• peterargue

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!