🏷️

ENS Integration Demo

Human-Readable Names for Ethereum

Instead of sending to 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045, just use vitalik.eth

Try It Yourself

Enter any ENS name (e.g., vitalik.eth) or Ethereum address to see the full profile:

ENS Name → Address (Forward Resolution)

ENS names resolve to Ethereum addresses, along with rich profile data:

V

vitalik.eth

ENS
Resolved via ENS ProtocolView on ENS
N

nick.eth

ENS
Resolved via ENS ProtocolView on ENS
B

brantly.eth

ENS
Resolved via ENS ProtocolView on ENS
J

jefflau.eth

ENS
Resolved via ENS ProtocolView on ENS

Address → ENS Name (Reverse Resolution)

Addresses with ENS names automatically show their human-readable name:

Lookup: 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045
?
0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045
Resolved via ENS ProtocolView on ENS
Lookup: 0xb8c2C29ee19D8307cb7255e1Cd9CbDE883A267d5
?
0xb8c2C29ee19D8307cb7255e1Cd9CbDE883A267d5
Resolved via ENS ProtocolView on ENS

TradeX ENS Features

📝

Automatic Resolution

Type any ENS name in the recipient field and it's automatically resolved to an Ethereum address

👤

Rich Profiles

View avatars, social media links, descriptions, and more for any ENS name

✓

Verified Identity

ENS provides cryptographic proof of ownership, ensuring you're sending to the right person

🔗

Social Integration

Connect with recipients via their Twitter, GitHub, email, and website directly from ENS

Technical Implementation

Wagmi Hooks: Uses useEnsName, useEnsAddress, useEnsAvatar
Text Records: Custom hook fetches social media, description, website, email via publicClient.getEnsText()
Chain ID: All ENS resolution happens on Ethereum Mainnet (chainId: 1), regardless of user's connected chain
Real-time: No hard-coded values - all data fetched live from ENS contracts
Powered by ENS Protocol • Learn more at ens.domains
View ENS on GitHub →