feat: tx-ctrl add excludeNativeTokenForFee param

[maxime-oe]

Explanation

Context:

With upcoming phase 1 for Tempo support, the initial approach will leverage EIP-7702 mechanics and UX.

1. One difference vs. other chains is that Tempo doesn't have a concept of native token.
   --> This means that some current logic when we "fall back" to the native token for gas fee when user has enough native balance won't work. excludeNativeTokenForFee is a new parameter for signaling that native token should not be an option when set to true and when gasFeeToken is provided.

2. Since the client dApps will trigger a call addTransactionBatch for some Tempo transactions - was only called internally until now - we add the actionId so such transactions appear on the Activity tab (transaction history). Otherwise such transactions still made it to the state but those without actionId don't appear in the activity tab.

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

---

Note

Medium Risk
Changes transaction creation metadata and fee-token fallback behavior when gasFeeToken is provided, which can affect how gas payment is selected for batched/EIP-7702 flows. Impact is gated behind new optional params but touches core transaction creation paths.

Overview
Adds an optional excludeNativeTokenForFee flag to TransactionMeta, AddTransactionOptions, and TransactionBatchRequest to force use of gasFeeToken even when the user has native balance.

Updates addTransaction so isGasFeeTokenIgnoredIfBalance becomes false when excludeNativeTokenForFee is set, and persists excludeNativeTokenForFee on the transaction only when explicitly provided. Batch/EIP-7702 submission now also forwards optional actionId (for Activity visibility) and excludeNativeTokenForFee into addTransaction, with new unit tests covering both default and opt-in behaviors.

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

[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]

New parameters lost in hook fallback path

Medium Severity

actionId and excludeNativeTokenForFee are only passed through in the addTransactionBatchWith7702 path. If 7702 fails (e.g., chain doesn't support it) and the code falls back to addTransactionBatchWithHook, these parameters are silently dropped. The processTransactionWithHook function's call to addTransaction does not include actionId or excludeNativeTokenForFee, meaning transactions won't appear in the Activity tab and native token exclusion won't apply in the fallback path.

Additional Locations (1)

• packages/transaction-controller/src/utils/batch.ts#L712-L725

 

[maxime-oe]

The intent of this is to have the minimum change possible to existing flows. Tempo first iteration of the implementation will only support 7702 flow, hence the parameters are only being added for this context and the intent is for the behavior to remain unchanged for the other flows.