MetaMask / MetaMask/metamask-extension
[Feature Request] Support Solana Addresses in MetaMask Address Book
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
## Issue Description:
The current MetaMask Address Book functionality does not allow users to save Solana addresses. Attempting to add a Solana address produces an error ("No resolution for domain provided"), preventing users from storing Solana contacts.
### Current Behavior:
* When users attempt to save a valid Solana address, an error message is displayed.
* Users cannot currently save Solana addresses to the built-in address book.
### Expected Behavior:
* Users should be able to store Solana addresses seamlessly, just as Ethereum addresses.
* No error message should be displayed when entering a valid Solana address.
### Steps to Reproduce:
1. Open MetaMask Extension and navigate to the Address Book.
2. Click on "New Contact."
3. Enter a valid Solana public address into the Ethereum public address field.
4. Observe the displayed error and the inability to save the contact.
### Environment:
* MetaMask Extension version: 13.0
* Browser: Observed on Chrome, Firefox, and Brave browsers.
### Screenshots:
### Suggested Solution:
* Extend Address Book support to recognize and validate Solana addresses, ensuring cross-chain compatibility and user convenience.
### Additional Context:
* Flagged during recent UAT sessions, significantly impacting Solana support and usability.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the MetaMask Extension Address Book and New Contact flow described in the issue, then trace validation of the Ethereum public address field. Verify that valid Solana public addresses can be saved without the “No resolution for domain provided” error while preserving existing Ethereum behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100