CONF-1943: Persist chain-agnostic Solana Pay intents - #10272
Draft
pedronfigueiredo wants to merge 2 commits into
Draft
pedronfigueiredo wants to merge 2 commits into
pedronfigueiredo wants to merge 2 commits into
Conversation
This was referenced Sep 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
TransactionMeta.metamaskPayrecordHexfieldssetPaySourcecontroller action and preserve source metadata when compatibility metrics are refreshedDesign scope
The original dual-store, versioned intent model was broader than CONF-1943 requires. Solana Pay needs CAIP-compatible source metadata because its source submission is not represented by a local EVM transaction, but that metadata now has one durable owner: the target transaction's existing
metamaskPayrecord.At-most-once source execution, request correlation, and recovery checkpoints will be introduced only in stacked #10273, where they have their first safety consumer. This PR contains no retry or resubmission behavior.
Validation
yarn workspace @metamask/transaction-pay-controller run jest --no-coverage src/TransactionPayController.test.tsyarn workspace @metamask/transaction-pay-controller run jest --no-coverage src/utils/quotes.test.tsyarn workspace @metamask/transaction-pay-controller run testyarn workspace @metamask/transaction-controller run test --runInBandyarn workspace @metamask/transaction-controller run buildyarn workspace @metamask/transaction-pay-controller run buildyarn workspace @metamask/transaction-pay-controller run messenger-action-types:checkyarn changelog:validateSolana Pay ticket and PR index
CONF-1943 — Persist the Solana Pay intent model in TransactionPayController
mainCONF-1944 — Run the one-attempt Solana source path and recovery loop in Core
CONF-1945 — Ship the Solana Pay source picker and confirmation flow in Extension
mainCONF-1946 — Ship the Solana Pay source picker and confirmation flow in Mobile
mainCONF-1947 — Wire rollout flags, analytics, and support diagnostics for Solana Pay