Trace the Diagnostic Event Stream to Find Which Contract in a Chain Actually Failed

[codeZe-us]

When a cross-contract call fails, the error surfaces at the top level with no indication of which contract in the call chain actually caused it. This analyzer traces the diagnostic event stream to pinpoint the origin.

Walk diagnostic events in order and detect the event where execution diverges from success
Identify the contract address and function name at the point of failure
Expectations: Prism correctly attributes a cross-contract failure to the specific contract and call that caused it, not just the top-level invoker.

Join the group: https://t.me/+sII7WPhll2liMGNk

[Awointa]

Hi, I’m interested in this issue. I have experience working with blockchain developer tooling, smart contract debugging systems, and transaction trace analysis, particularly within contract ecosystems where multi-contract execution paths make failure attribution difficult.

I can implement the analyzer to inspect diagnostic event streams, trace cross-contract execution step by step, and accurately identify the exact contract address and function where execution diverges from a successful path. Rather than reporting only the top-level invocation failure, I’ll ensure the analyzer pinpoints the true source of the error within nested contract calls, making debugging significantly more precise for developers.

I’ll focus on building a reliable tracing mechanism that preserves event ordering, detects failure boundaries accurately, and validates behavior with test cases covering nested cross-contract execution scenarios so Prism consistently attributes failures to the correct contract in the call chain.

[grantfox-oss]

🦊 GrantFox — @Awointa has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #246)
2. Your PR will be reviewed by the Toolbox-Lab maintainers

Good luck! Track your progress on GrantFox.