Skip to content

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

@codeZe-us

Description

@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

Metadata

Metadata

Assignees

No one assigned

    Labels

    GrantFox OSSIssue tracked in GrantFox OSSMaybe RewardedIssue may be eligible for a GrantFox rewardOfficial CampaignCampaign: Official Campaignhelp wantedExtra attention is needed

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions