ENS Integration

HNS.ID domains can be integrated with ENS (Ethereum Name Service) through two different methods, allowing your domain records to be used across the Ethereum ecosystem. This integration enables resolution of addresses, text records, content hashes, and other ENS-compatible data.

Integration Methods

On-Chain ENS Aliasing

• Uses Ethereum blockchain transactions
• Requires ownership of an .eth domain
• Highest compatibility with dApps and services
• Requires gas fees for setup and changes
• Best for permanent integrations

Off-Chain ENS Aliasing

• Uses DNS TXT records
• No blockchain transactions required
• Free to set up and modify
• Works with any DNS domain
• Best for cost-sensitive implementations

How It Works

Both methods allow you to map your domain to resolve ENS-compatible data. For example:

• If you own example.com and link it to cool-tld/, then user.example.com will resolve to the same data as user.cool-tld
• If you own example.eth and link it to cool-tld/, then user.example.eth will resolve to the same data as user.cool-tld

Choosing an Integration Method

Consider these factors when choosing between on-chain and off-chain integration:

Getting Started

• Set up On-Chain ENS Integration
• Set up Off-Chain ENS Integration
• View Legacy Bridge Documentation
• Read FAQs