[taran-a]

Explanation

Aligns the Solana snap's transaction confirmation with the shared transaction warning contract (Stellar/EVM reference behaviour / warn path), adopting the new shared components from snap-networks-utils:

• Malicious verdicts — confirm button swaps to alert "Confirm", opening an acknowledgement screen with a risk checkbox; confirmable only after explicit acknowledgement (never hard-blocked)
• Background re-scans — no longer show the "checking" state or disable confirm; only the initial scan does
• Warning verdicts — soft "This request may be risky" copy instead of malicious-request copy
• Preference gating — verdict banners require useSecurityAlerts; scan-failure banners stay active while any scan preference is on
• Re-scans — run with the same preference-selected scan options as the initial scan (previously always requested simulation+validation) and also run when only security alerts are enabled

References

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've communicated my changes to consumers by updating changelogs for packages I've changed
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

[mikesposito]

Have you considered implementing this in @metamask/snap-networks-utils (or all the function we can share at least) instead of the Solana Snap, so we can reuse them 1:1 for other Snaps?

[mikesposito]

Why are we adding EN messages to non-EN locales? 🤔

[taran-a]

in solana when there is a missing key in locale we return that key as a message.

I actually have just removed my changes to unused locales - we use only en, es no.

but for es I thought its our approach that we add en as I found several already were there.

[taran-a]

Have you considered implementing this in @metamask/snap-networks-utils (or all the function we can share at least) instead of the Solana Snap, so we can reuse them 1:1 for other Snaps?

I have another PR in this stack with some UI components, maybe later I will see some candidates to move into the shared lib, but not it hard to decide

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud