MetaMask / MetaMask/metamask-extension
[UX Flow] Default Bridge Address Update
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
### What is this about?
When making a bridge transaction a certain EVM recipient address is added by default. If I want to change it, I need to click on the 'X' to add another EVM address in my wallet or to add a different address manually.
The 'X' does not feel very intuitive and one might think it will cancel the operation.
Should we replace it with a more explicit 'select another address' button?
### Scenario

### Design
_No response_
### Technical Details
_No response_
### Threat Modeling Framework
_No response_
### Acceptance Criteria
_No response_
### Stakeholder review needed before the work gets merged
- [x] Engineering (needed in most cases)
- [x] Design
- [x] Product
- [ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
- [ ] Security
- [ ] Legal
- [ ] Marketing
- [ ] Management (please specify)
- [ ] Other (please specify)
### References
_No response_
Contributor guide
Research direction
Start by reproducing the bridge transaction flow and locating the default EVM recipient address control in the extension. Confirm the intended replacement for the “X” with design and product, then update the control so users can select another address; done means the revised flow is clear and approved by the listed stakeholders.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100