HL Names has announced the launch of .hl.hn, connecting Hyperliquid names to Ethereum Name Service infrastructure. The integration lets supported apps and wallets resolve an existing .hl name through its .hl.hn equivalent, while the original name remains on Hyperliquid.
What .hl.hn Means for Hyperliquid Users
Someone who owns alice.hl can use alice.hl.hn to look up their address on Etherscan or send funds through supported wallets, including Rabby and MetaMask.
The key change is where the name can be recognized. A .hl identity stays on Hyperliquid, while the additional .hn suffix makes it accessible through ENS resolution.
For readers unfamiliar with the technology, Ethereum Name Service connects readable names with blockchain addresses and other records. This integration extends that naming infrastructure to existing .hl identities.
How the ENS Integration Works
HL Names says the integration uses two standards: ENSIP-10, known as Wildcard Resolution, and ERC-3668, known as CCIP Read.
Wildcard Resolution allows one resolver to handle names across the .hl.hn namespace. According to the announcement, this means existing .hl names work automatically through their corresponding .hl.hn names.
CCIP Read allows the resolver to fetch the address associated with a .hl name when an application requests its .hl.hn equivalent. Together, the standards connect Hyperliquid’s naming system with applications that support this ENS resolution flow.
A Wider Reach for .hl Names
The launch gives .hl holders a way to reuse their identity across more of the ENS ecosystem without moving the underlying name away from Hyperliquid.
Support remains application-dependent: the announcement refers to compatible apps and wallets, rather than universal availability. For users, the practical change is straightforward—a familiar .hl name can now serve as an address lookup through its .hl.hn equivalent in supported services.
