Avoid casting to determine confirmation state when mapping staking transactions #1872
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.
Summary
When determining the confirmation state of native deposit transacitons, we currently cast a transaction that can be either a
MultisigTransaction
orModuleTransaction
toMultisigTransaction
. It is still theoretically possible to deposit via a module, meaning that this cast is not safe.This avoids casting and instead checks for the existence of the
confirmations
property in the transaction in question, inherently meaning that it is aMultisigTransaction
.Changes
confirmations
property instead of casting