You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: include BDK cause in PSBT build error message — surfaces the underlying BDK root cause (e.g. InsufficientFunds, OutputBelowDustLimit) in PSBT build error messages so they appear in Sentry/Mixpanel instead of being lost at the RPC boundary.
Changelog
CHANGELOG entry: Fixed Bitcoin PSBT build errors now include the underlying cause for better diagnostics
Related issues
Fixes:
Manual testing steps
Create a Bitcoin account
Trigger a PSBT build failure (e.g. insufficient funds swap)
Verify the error message in Sentry/Mixpanel includes the BDK cause
Selected Performance tags: None (no tests recommended)
Risk Level: low
AI Confidence: 90%
click to see 🤖 AI reasoning details
E2E Test Selection:
The only change in this PR is a patch version bump of @metamask/bitcoin-wallet-snap from 1.10.0 to 1.10.1. This is a preinstalled snap used for Bitcoin wallet functionality, conditionally compiled only in builds with the bitcoin feature flag (BEGIN:ONLY_INCLUDE_IF(bitcoin)).
Key findings:
No E2E tests in the test suite directly test Bitcoin wallet snap functionality (searched across all test directories)
The Bitcoin wallet snap is a preinstalled snap, not a Flask snap — FlaskBuildTests covers snap lifecycle for Flask builds, not this preinstalled Bitcoin snap
The change is purely a dependency version bump with no app code changes
No shared components (navigation, confirmations, modals, etc.) are affected
The snap is only active in Bitcoin-enabled builds, not in standard or Flask builds tested by E2E
Since there are no existing E2E tests that exercise Bitcoin wallet snap functionality, and this is a low-risk patch bump with no app code changes, no E2E test tags need to be run.
Performance Test Selection:
A patch version bump of the bitcoin-wallet-snap dependency has no measurable performance impact on app rendering, data loading, or critical user flows. No performance tests are warranted.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Bumps
@metamask/bitcoin-wallet-snapfrom^1.10.0to^1.10.1.Release PR: MetaMask/snap-bitcoin-wallet#595
Notable change:
InsufficientFunds,OutputBelowDustLimit) in PSBT build error messages so they appear in Sentry/Mixpanel instead of being lost at the RPC boundary.Changelog
CHANGELOG entry: Fixed Bitcoin PSBT build errors now include the underlying cause for better diagnostics
Related issues
Fixes:
Manual testing steps
Pre-merge author checklist
Note
Low Risk
Low risk dependency-only bump with no application code changes; any impact is limited to behavior changes inside the updated snap package.
Overview
Bumps the Bitcoin snap dependency by updating
@metamask/bitcoin-wallet-snapfrom^1.10.0to^1.10.1inpackage.json.Updates
yarn.lockto resolve and checksum the new1.10.1release.Written by Cursor Bugbot for commit d858417. This will update automatically on new commits. Configure here.