Fix nested calls status #205
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📝 Description
This PR improves how nested extrinsics are evaluated by accurately determining the actual execution result of wrapped and batched calls.
In Substrate, wrapper extrinsics (such as
Utility::batch*,Proxy::*,Multisig::*, andSudo::*) may succeed at the outer level while the real success or failure is determined by their inner calls. This change introduces proper detection and traversal of such nested calls to derive the correct success value.What this PR does
Why this matters
Without this logic, wrapped extrinsics could be incorrectly marked as successful even when an inner call fails. This fix ensures accurate indexing, analytics, and downstream consumers that rely on correct extrinsic success status.