feat: add accountOverride to override default recipient or delegator for MM Pay transactions

[jpuri]

Explanation

Add accountOverride in transaction config to override default recipient or delegator for MM Pay transactions

References

Fixes: https://consensyssoftware.atlassian.net/browse/CONF-1188
Fixes: https://consensyssoftware.atlassian.net/browse/CONF-1204

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

---

Note

Medium Risk
Changes which account is used for balance checks and transaction/delegation signing, so incorrect wiring could cause quotes to be computed for the wrong account or submissions to be signed with an unexpected from.

Overview
Adds a new per-transaction accountOverride config/state field that overrides the default from address used across MM Pay flows.

When accountOverride changes, the controller now re-runs source amount/quote updates and clears any selected paymentToken; quote building, payment-token balance lookups, Relay execute delegation (txParams.from), and HyperLiquid withdraw signing now all use the overridden address. Tests and changelog are updated accordingly.

^{Reviewed by Cursor Bugbot for commit 2383954. Bugbot is set up for automated code reviews on this repo. Configure here.}

[matthewwalsh0]

For the fully gasless flow, do we need to update submitViaRelayExecute in relay-submit to use the accountOverride also since it would be providing the funds?

[jpuri]

This should also already work as from is now updated in quote.

[matthewwalsh0]

This flow just uses the transaction and not from so I think we need to fix this manually.

[jpuri]

PR is updated to address this

[matthewwalsh0]

Can do in a separate PR if easier, but for the withdraw flows, if we have a accountOverride, then we want that to sign the withdraw transaction rather than the original from.

So do we need to convert the withdraw transaction data to delegations on line 353 of relay-submit.ts?

[jpuri]

This should also already work since from is quote is updated.

[matthewwalsh0]

This is also a special case as while the data is currently using the original from via transaction which is what we want, we now need to convert it to delegations with getDelegationTransaction so our accountOverride can submit it.

[jpuri]

PR is updated to address this

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 1b7f538. Configure here.}

[matthewwalsh0]

Slightly ambigious as the delegation is still done on behalf of the original from and not accountOverride. Plus this also still applies when isPostQuote is true.

[jpuri]

Valid point, I updated the PR

[matthewwalsh0]

This flow just uses the transaction and not from so I think we need to fix this manually.

[matthewwalsh0]

This is also a special case as while the data is currently using the original from via transaction which is what we want, we now need to convert it to delegations with getDelegationTransaction so our accountOverride can submit it.

[jpuri]

This is also a special case as while the data is currently using the original from via transaction which is what we want, we now need to convert it to delegations with getDelegationTransaction so our accountOverride can submit it.

@matthewwalsh0 : PR is updated to address this.

[matthewwalsh0]

@metamaskbot publish-preview