Web3 Domain Wallet Compatibility: Evidence and Checks

A domain is compatible with a wallet only for a particular action, network and client. The matrix below records what official documentation supports. It distinguishes a documented integration from a transaction we have personally tested.

Wallet and app compatibility evidence

What “supported” needs to specify

Keep four questions separate: can you connect a wallet to buy or manage the name; can you enter the name as a payment recipient; can an address display it as a primary identity; and can a browser open its website content? An integration can answer one question without answering the others.

For example, an NFT collection view proves the wallet is displaying an asset. It does not prove that the send field resolves the name. A browser gateway proves an access route for hosted content, but does not establish payment support.

Use a verification record

For each important workflow, record the complete name, provider product, wallet client and version, network, intended action, resolved address and date. Mark the result as documented, observed in a read-only lookup, or confirmed by your own transaction. Those labels prevent a marketing claim from quietly becoming an assertion of hands-on testing.

Our practical acceptance rule is simple: the intended app must return the intended destination for the exact name. If the lookup is unavailable or ambiguous, treat the workflow as unverified. Check the full address through an independent channel before using the name in payment instructions.

Primary-name display troubleshooting

For ENS, compare the address record on the name with the primary-name record on the wallet. Then check whether the app reads the appropriate Default or Network record. Use our setup walkthrough and the diagnostic checklist to isolate the failing layer.

A change appearing in the official management app can precede a cached third-party view. Record the time instead of repeatedly changing correct settings. Basenames have their own management controls, while SNS needs particular attention to suffix and activation status during migration.

Add-ons and website access

The two MetaMask Snap listings above describe optional integrations, not an endorsement or an instruction to install them. Review the developer, requested permissions and current supported client yourself. Namespace Guide did not install either add-on as part of this research.

For websites, ENS documentation describes content hosting and browser or gateway support. That is a separate project from a wallet alias. Plan a normal clickable link for readers whose browsers do not handle the chosen name directly.

What this matrix does not establish

This is a bounded evidence matrix, not an exhaustive compatibility certification. No transfer was signed, no payout was tested and no claim is made about every current mobile or desktop wallet. A newer app release, different network or newly introduced extension needs a fresh check against its official documentation.