feat: tempo transactions poc utils approach

[maxime-oe]

Description

Meant to be used along with MetaMask/core#8052
Mobile twin of MetaMask/metamask-extension#40449

Changelog

CHANGELOG entry: adds Tempo transactions (partial) support on Mobile.

Related issues

Fixes:

Manual testing steps

Feature: my feature name

  Scenario: user [verb for user action]
    Given [describe expected initial app state]

    When user [verb for user action]
    Then [describe expected outcome]

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I've included tests if applicable
• I've documented my code using JSDoc format if applicable
• I've applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

---

Note

High Risk
High risk because it changes transaction submission paths (addTransaction, wallet_sendCalls) and fee-token selection/alerts using new excludeNativeTokenForFee behavior, which could affect signing, batching, and gas fee UX on supported chains.

Overview
Adds Tempo chain (no native token) support by introducing tempo-tx-utils and routing Tempo transactions through a new addTempoTransaction path: non-Tempo-style txs get default fee-token options, while Tempo type: 0x76 requests are validated and converted into addTransactionBatch calls.

Updates confirmations gas-fee UI and hooks to respect excludeNativeTokenForFee: hides the native token option in the modal, disables the selector when there’s only one non-native choice, falls back to chain-configured fee token symbol/address when no native exists, and adjusts insufficient-balance messaging to display the configured symbol.

Extends BackgroundBridge EIP-5792 wallet_sendCalls handling to inject Tempo extra options when the account supports EIP-7702, adds Tempo chain IDs/symbol mapping, and bumps related controller dependencies; includes new/updated unit tests around Tempo utils and selection behavior.

^{Written by Cursor Bugbot for commit 5f80de6. This will update automatically on new commits. Configure here.}

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​@​metamask/​assets-controller@​3.2.1 ⏵ 3.3.0	+1		+1	+1
	npm/​@​metamask/​assets-controllers@​103.0.0 ⏵ 103.1.1	+1		+1	+1
	npm/​@​metamask/​controller-utils@​11.19.0 ⏵ 11.20.0			+1	+5
	npm/​@​metamask/​delegation-deployments@​0.15.0 ⏵ 1.0.0			+3	+2

View full report

[github-actions]

✅ E2E Fixture Validation — Schema is up to date
18 value mismatches detected (expected — fixture represents an existing user).
View details

[sonarqubecloud]

Quality Gate failed

Failed conditions
70.7% Coverage on New Code (required ≥ 80%)
C Reliability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

[github-actions]

🔍 Smart E2E Test Selection

• Selected E2E tags: SmokeAccounts, SmokeConfirmations, SmokeIdentity, SmokeNetworkAbstractions, SmokeNetworkExpansion, SmokeTrade, SmokeWalletPlatform, SmokeCard, SmokePerps, SmokeRamps, SmokeMultiChainAPI, SmokePredictions, FlaskBuildTests
• Selected Performance tags: @PerformanceAccountList, @PerformanceOnboarding, @PerformanceLogin, @PerformanceSwaps, @PerformanceLaunch, @PerformanceAssetLoading, @PerformancePredict, @PerformancePreps
• Risk Level: high
• AI Confidence: 100%

click to see 🤖 AI reasoning details

E2E Test Selection:
Hard rule (controller-version-update): @MetaMask controller package version updated in package.json: @metamask/assets-controller, @metamask/assets-controllers, @metamask/transaction-controller. Running all tests.

Performance Test Selection:
Hard rule (controller-version-update): @MetaMask controller package version updated in package.json: @metamask/assets-controller, @metamask/assets-controllers, @metamask/transaction-controller. Running all tests.

View GitHub Actions results

[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.}

[cursor]

Missing Tempo chain guard causes spurious warnings on all chains

Medium Severity

getChainExtraParamsForWalletSendCalls calls accountSupports7702 for every wallet_sendCalls on any chain and logs a misleading "Tempo chain but wallet does not support 7702" warning when the account doesn't support 7702, even on Ethereum mainnet. The equivalent logic in index.ts correctly gates on isTempoChain(chainId) before performing the 7702 check. This function is missing the same guard, causing unnecessary async overhead and noisy/misleading warnings for all non-7702 accounts on every chain.