Skip to content

fix: disable scan for unsupported transactions#186

Draft
mikesposito wants to merge 3 commits intomainfrom
mikesposito/fix/disable-scan-for-unsupported-txs
Draft

fix: disable scan for unsupported transactions#186
mikesposito wants to merge 3 commits intomainfrom
mikesposito/fix/disable-scan-for-unsupported-txs

Conversation

@mikesposito
Copy link
Member

@mikesposito mikesposito commented Feb 3, 2026

The transaction simulation is being disabled for unsupported transactions to prevent unreliable estimates and potential errors during processing, that may confuse users.

Fixes https://consensyssoftware.atlassian.net/browse/NEB-386

@mikesposito mikesposito requested a review from a team as a code owner February 3, 2026 13:53
@mikesposito mikesposito marked this pull request as draft February 3, 2026 13:53
@mikesposito
Copy link
Member Author

@metamaskbot publish-preview

@github-actions
Copy link
Contributor

github-actions bot commented Feb 3, 2026

Preview builds have been published. See these instructions for more information about preview builds.

Expand for full list of packages and versions.
{
  "@metamask-previews/tron-wallet-snap": "1.20.0-preview-2895dbc"
}

Comment on lines 186 to 188
accountAddress: account.address,
parameters: {
from: context.scanParameters?.from ?? undefined,
to: context.scanParameters?.to ?? undefined,
data: context.scanParameters?.data ?? undefined,
value: context.scanParameters?.value ?? undefined,
},
transactionRawData: rawData,
origin,
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I felt like the expected shape of the scan parameters is a Blockaid detail, and should be handled internally by the SecurityAlertsApiClient, rather than api consumers around the snap codebase.

SecurityAlertsApiClient and TransactionScanService now accept a transactionRawData parameter instead of parameters for scan request.

@ulissesferreira
Copy link
Contributor

Note to continue: we just pass the data in, the client does what it needs to do regarding, checking if the simulation is supported, transforming the fields to correctly call it, throwing an error if unsupported

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants