Description

Adds the on-chain transaction layer for Money Account crypto deposits and withdrawals (MUSD-593).

What changed:

• Added buildMoneyAccountDepositBatch and buildMoneyAccountWithdraw utility functions (moneyAccountTransactions.ts) that encode the approve + deposit / withdraw calldata against the Veda vault contracts (Teller, Accountant, Lens).
• Added useMoneyAccountDeposit and useMoneyAccountWithdrawal hooks (useMoneyAccount.ts) that read vault configuration from remote feature flags, derive the provider from the active network client, and submit the transactions via addTransactionBatch / addTransaction.
• Added selectMoneyAccountVaultConfig selector and the moneyAccountDepositConfig remote feature flag registry entry, which holds chain ID and contract addresses for the vault.
• Temporarily wired the "Add" button in MoneyHomeView to initiateDeposit with a hardcoded amount as a dev integration test; this will be replaced once the amount entry UI is built.

Deposit flow: approve(boringVault, amount) + deposit(asset, amount, minimumMint, 0x0) submitted as an atomic batch. A 0.1% slippage tolerance is applied to the previewDeposit quote.

Withdrawal flow: getRate → convert asset amount to vault shares → withdraw(asset, shares, minimumAssets, to).

Changelog

CHANGELOG entry: null

TODO

Note that the code has 2 todos that should be address seperatly:

• adding hook to get amount from MM pay
• updating addresses for mUSD and veda vault once we have a testing one ready on monad

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.