Description

This pull request enhances the useInsufficientNativeReserveError hook to support Bitcoin (BTC) native reserve logic, ensuring accurate handling of minimum reserve requirements and quote-aware calculations for BTC swaps. It also improves test coverage for these scenarios and refactors related code for better clarity and extensibility.

BTC Native Reserve Support and Logic Improvements:

• Added BTC mainnet support to the minimum native reserve calculation, introducing a specific reserve threshold for BTC and handling BTC chain IDs using CAIP format. The hook now accounts for BTC-specific requirements when determining if a swap would violate the minimum reserve.

Testing Enhancements:

• Added comprehensive test cases for BTC reserve logic, including scenarios for reserve breaches, quote-aware calculations, and edge cases where reserve or fees restrict swaps. Introduced BTC token and quote mocks for robust test coverage.

Refactoring and Type Improvements:

• Refactored types and utility functions to support both EVM and non-EVM (CAIP) chain IDs, improving maintainability and future extensibility.

Integration Updates:

• Updated BridgeViewContent and SwapsConfirmButton components to pass the activeQuote prop to the hook, enabling quote-aware reserve checks in the UI flow.

Changelog

CHANGELOG entry: added BTC swap reserve enforcement with quote-aware fee handling

Related issues

Fixes: Bridging BTC is failing at the transaction crafting in certain cases

Manual testing steps

BTC max amount / reserve validation

1. Use a BTC account with a small balance.
2. Select BTC as source and ETH as destination.
3. Enter an amount that would leave less than 0.00003 BTC after the swap.
4. Confirm the warning banner says Minimum BTC reserve balance is required.
5. Confirm the message displays a reserve of 0.00003 BTC.
6. Confirm the CTA shows Insufficient funds.
7. Click Use max allowed.
8. Confirm the input is reduced to the max amount shown in the banner.

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.

Performance checks (if applicable)

• I've tested on Android
  • Ideally on a mid-range device; emulator is acceptable
• I've tested with a power user scenario
  • Use these power-user SRPs to import wallets with many accounts and tokens
• I've instrumented key operations with Sentry traces for production performance metrics
  • See trace() for usage and addToken for an example

For performance guidelines and tooling, see the Performance Guide.

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.