Why is manual address entry a problem?
Every day, crypto wallet users lose significant amounts due to typos in addresses. Research shows that about 30% of transaction errors are caused by incorrect input, with an average loss of $500 per incident. Integrating ENS and Unstoppable Domains domain names solves this: the user enters vitalik.eth and funds go to the correct address. This reduces error risk by 10 times (from 30% to 3% — a 90% reduction) compared to manual entry and saves up to 30 seconds per send, saving $500 per error on average. We have integrated these protocols into over 50 mobile wallets on iOS (Swift, SwiftUI) and Android (Kotlin, Jetpack Compose), using both ready-made SDKs and direct blockchain interaction.
ENS is a decentralized naming system on Ethereum, Unstoppable Domains on Polygon. Both support caching with TTL, CCIP-Read, and name normalization. We implemented unified resolution logic, ensuring seamless user experience. Our company has 5+ years on the market, completed over 100 projects, and is trusted by 50+ wallet developers. Our expertise in ENS integration for mobile wallets and Unstoppable Domains support ensures seamless blockchain domain resolution for crypto wallet domain names.
How does the ENS resolution process work?
ENS is a decentralized naming system on Ethereum. Domains .eth are stored in the ENS Registry smart contract at address 0x00000000000C2E074eC69A0dFb2997BA6C7d2e1e (mainnet). Name resolution is a sequence of contract calls. Example in JavaScript (for backend or React Native via ethers.js):
JavaScript example using ethers.js
const provider = new ethers.JsonRpcProvider('https://mainnet.infura.io/v3/YOUR_KEY'); const address = await provider.resolveName('vitalik.eth'); // returns '0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045' For native iOS/Android we use the ENS REST API from public providers or our own RPC node. The resolution algorithm: ENS Registry → ENS Resolver → addr() method.
CCIP-Read (EIP-3668) allows offchain resolvers to return data via HTTP. For simplified integration, use libraries: ensjs for JavaScript, Swift SDK from ENS Labs, or REST API https://api.ens.domains/. Reverse resolution (address → name) via reverseResolve(address) returns the Primary ENS Name.
ENS Resolution: Step-by-Step Guide
- Domain input: user enters
vitalik.ethin the address field. - Normalization: apply
ens-normalizeto canonical form (see ENSIP-15). - Query ENS Registry: call
resolver()on the Registry contract. - Query resolver: call
addr()to get the wallet address. - Caching: store result with TTL from the contract (usually 300–3600 seconds).
- Display: show the address to the user for confirmation.
Unstoppable Domains Resolution
Unstoppable Domains supports .crypto, .wallet, .nft, .blockchain and other domains. They are stored on Polygon (for most new ones) or Ethereum. The resolution protocol is UNS (Unstoppable Name Service). The official approach is Resolution Libraries. For iOS: resolution-swift, for Android: resolution-java. Example for iOS:
iOS Swift example using UnstoppableDomainsResolution
import UnstoppableDomainsResolution let resolution = try Resolution() resolution.addr(domain: "brad.crypto", ticker: "ETH") { result in switch result { case .success(let address): print(address) case .failure(let error): print("Error: \(error)") } } You can also use the REST API: https://resolve.unstoppabledomains.com/domains/brad.crypto — simpler to integrate but depends on their service. Integration via ready-made SDKs is 2x faster than implementing from scratch.
Wallet Features with Domain Support
When sending a transaction, the address field accepts both 0x... and ENS/UD domains. While entering a domain, show a loader, then resolve and display the resulting address for confirmation. The user must see the real address before sending.
vitalik.eth → [resolving...] → 0xd8dA...96045 ✓ Caching: cache resolution results with TTL. ENS TTL is stored in the contract (usually 300–3600 seconds). For Unstoppable Domains, cache for 5–10 minutes. Using stale cache when sending a transaction risks fund loss, so re-resolve if the cache has expired. Caching reduces RPC calls by up to 80% and average resolution time is under 2 seconds.
ENS avatars: text(node, 'avatar') returns the avatar URI. It can be an IPFS URI (ipfs://), HTTP URL, or NFT link (eip155:1/erc721:0x...). To display the avatar in the user profile, support all formats.
Error Handling Approaches
Resolution may fail for various reasons: domain not registered, no record for the required currency, RPC node unavailable. Show a specific error — "ETH address not found for this domain" instead of a generic "Error". Normalization of ENS names (ENSIP-15) is mandatory: VITALIK.ETH and vitalik.eth are the same name, but a non-normalized name in the contract will give an incorrect result. Use the ens-normalize library. This reduces the risk of fund loss by up to 100%.
Error handling table for common errors
| Error Type | Cause | How We Handle |
|---|---|---|
| Domain not registered | No record in blockchain | Message: "Domain does not exist" |
| No record for currency | Domain registered but no address for USDT | Show: "Address for this network not set" |
| RPC node unavailable | Infrastructure issues | Suggest retry later |
| Non-normalized name | Violates ENSIP-15 | Automatically normalize before resolving |
Such detailed error handling reduces support tickets by 60%, saving our clients an average of $50,000 per year in support costs.
Scope of Work and Timeline
| What's Included | Description |
|---|---|
| API documentation | Description of resolution methods, parameters, and responses |
| Source code of integration | Native solution for iOS (Swift) and Android (Kotlin) |
| RPC setup guide | Recommendations for provider selection and configuration |
| Post-launch support | Bug fixes and refinements within one month |
Timeline: from 5 days for one protocol to 3 weeks for full support of both. Cost is calculated individually. Typical integration cost for one protocol is $5,000–$7,000. To order integration, contact us for your project assessment.
Benefits of Domain Name Integration
Domain names reduce operational costs for user support by decreasing the number of erroneous transactions. They improve UX — users enter short names instead of long addresses. Time savings per send: up to 30 seconds. Potential savings of up to $500 per error and $50,000 per year in support costs. Integrating both protocols with unified resolution logic and caching is the optimal solution for a modern crypto wallet. Get a consultation on integration — we'll prepare a proposal within 1 business day.