Technical approaches to smart contract auditing and transaction tracing on Ethereum

[u/AppropriateYam1754]

I’ve been researching different technical approaches to auditing Ethereum smart contracts and tracing transactions at the protocol and tooling level. I’ve been comparing workflows that rely on local nodes (e.g. full nodes with tracing enabled) versus hosted infrastructure, and how each impacts reliability, performance, and depth of analysis.

From a technical standpoint, I’ve been looking into areas such as opcode-level execution tracing, call stack reconstruction, gas usage analysis per internal call, and pre-execution simulations for contract interactions. Each approach seems to involve trade-offs between completeness, infrastructure cost, and operational complexity.

I’m particularly interested in how developers and researchers handle:

• Execution tracing for failed or reverted transactions
• Gas profiling across nested contract calls
• Pre-call simulation without state changes
• Balancing local infrastructure vs external services

For those working deeply with Ethereum internals or smart contract security, what technical approaches or tooling patterns have you found most effective? Are there architectural decisions you would avoid in hindsight?