Skip to content
Basis Desk
Tech & Protocols · 8 min read Last reviewed November 20, 2026

Blockchain Naming Systems, Explained: ENS and SNS Human-Readable Addresses

Blockchain naming systems map unwieldy hexadecimal public keys to readable domains like .eth and .sol. Understanding how registry contracts, resolvers, recurring renewal fees, and squatting dynamics work is essential to avoiding costly transfer mistakes.

Editorial oversight: Julian Mercer, Chief Editor
Neutral
Blockchain Naming Systems, Explained: ENS and SNS Human-Readable Addresses

Key points

  • Blockchain naming protocols use registry contracts for domain records and separate resolver contracts to translate names into multi-chain addresses.
  • Namehashing algorithmically condenses variable-length domains into fixed 256-bit cryptographic nodes to optimize onchain smart contract execution.
  • Recurring renewal fees prevent permanent squatting, while post-grace-period dutch auctions disincentivize automated bot frontrunning.
  • Address-confusion and homoglyph attacks exploit character spoofing, requiring protocol-level Unicode normalization and dual reverse-record checks.
  • Holding a domain's ownership NFT does not automatically change where the resolver directs assets until records are explicitly updated onchain.

Public blockchain networks identify participants through public keys and derived cryptographic hashes, producing strings of characters such as 42-character hexadecimal Ethereum addresses or base58-encoded Solana addresses. Blockchain naming systems replace these machine-oriented strings with human-readable identifiers such as alice.eth or bob.sol. Rather than relying on centralized domain registries, these decentralized naming services operate through programmable smart contracts to link domains directly to addresses, metadata, and decentralized content hashes.

While readable names drastically simplify consumer interactions across decentralized applications, they introduce their own distinct failure modes. The technical architecture relies on onchain lookups through resolvers, ongoing maintenance via recurring renewal fees, and secondary marketplaces prone to name squatting and address-confusion attacks.

The Architecture of Onchain Registries and Resolvers

The Domain Name System (DNS) underpinning the traditional internet translates hostnames into numeric IP addresses via recursive resolvers and root authority servers operated by organizations like ICANN. Decentralized systems mirror this design using smart contracts, most notably demonstrated by the Ethereum Name Service (ENS) on the Ethereum network and the Solana Name Service (SNS) on Solana.

In systems like ENS, domain lookup is divided across two principal components: a registry smart contract and one or more resolver contracts. The registry contract serves as an immutable database tracking domain ownership, administrators, and the specific resolver assigned to each name. The registry does not store individual destination addresses, external text records, or content hashes directly. Instead, it delegates those translation tasks to designated resolvers.

When a user enters a readable domain into a compatible wallet or application, the software executes a two-step query. First, the client queries the registry contract for the hash of the domain name to retrieve its authorized resolver address. Second, the client queries that specific resolver contract to fetch the associated cryptographic address for the requested network. Resolvers can store multi-chain addresses, allowing a single .eth name to resolve to an Ethereum address, a Bitcoin address, or a Solana address depending on the query parameters. SNS operates on an analogous framework, leveraging Solana's account model to store domain records within dedicated program accounts that bind domain hashes to public keys.

Forward Resolution, Reverse Records, and Namehashing

To manage alphanumeric strings efficiently inside smart contracts, naming protocols do not store plain-text strings in state. Instead, they process domain strings through a recursive cryptographic hashing algorithm called namehash. This process standardizes variable-length domain components into fixed 256-bit cryptographic node identifiers, preserving hierarchical subdomains while optimizing onchain gas consumption.

Resolving an address operates in two directions. Forward resolution takes a readable name (such as treasury.eth) and returns a specific payment address or text record. Conversely, reverse resolution takes an alphanumeric address and queries a dedicated reverse registry to verify which primary human-readable name the account owner claims. To establish valid reverse resolution, the account owner must explicitly publish a primary reverse record pointing to their chosen name, and the name's resolver must confirm that the owner actually controls the target name. Without this dual verification, bad actors could deceptively display high-profile domains alongside arbitrary addresses.

Modern decentralized applications rely heavily on these reverse records to populate user interfaces, display community participant names, and facilitate account tracking. For applications interacting with smart contract wallets via Account Abstraction, primary reverse records allow programmatic wallets to surface intuitive identifiers across multi-signature and automated transaction environments.

Renewal Economics and Expiration Squatting

Unlike traditional public goods, naming registries require financial and economic mechanisms to deter arbitrary resource monopolization. If names could be registered indefinitely for a negligible one-time fee, early participants could register entire dictionaries, effectively locking subsequent users out of useful namespaces.

ENS and SNS address this problem through dynamic registration and recurring renewal fee models, though their implementations differ. ENS charges recurring renewal fees based on the character length of the primary label, priced in US dollars but settled in $ETH. Shorter names, which are structurally scarcer and more prone to speculation, carry higher annual fees than longer names. If a registrant fails to pay renewal fees before domain expiration, the name enters an explicit grace period. During this window, resolution records are disabled, but the original owner retains the exclusive right to renew.

Once the grace period concludes, expired domains enter a public dutch auction mechanism rather than returning to the pool at baseline registration pricing. The registration fee starts at an elevated temporary premium that decays exponentially over a fixed window (typically 21 days) until it reaches baseline pricing. This auction mechanism limits the profitability of automated capture scripts and frontrunning bots that seek to re-register expired valuable names at basic rates. SNS on Solana historically utilized non-expiring one-time registration fees for certain primary records, although evolving iterations and sub-registries frequently incorporate rental charges or bidding protocols to balance storage rent and domain hoarding.

Worked Example: The Cost of Multi-Year Expiration

Consider an enterprise securing a 4-character domain name on ENS. Under the standard protocol tiering mechanism, shorter 4-character names cost significantly more per year than labels of 5 or more characters.

Assume the protocol base fee for a 4-character name is set at an ongoing rate equivalent to $160 per year in ether, while a 5-character name costs $5 per year. If the enterprise purchases a 4-character name for a 5-year duration, the registration commitment requires $800 in base protocol fees ($160 multiplied by 5 years), plus the transactional network gas fees incurred to execute the commitment and registration smart contract calls. If the enterprise permits the registration to lapse, the domain remains inactive throughout a 90-day grace period. If unrenewed by day 91, it enters the temporary premium auction, starting with an added price premium of $100,000 that steadily decays toward zero over 21 days. A secondary buyer securing the domain halfway through the decay schedule must pay the decayed premium balance on top of the regular annual base fee, demonstrating the steep financial penalty of missing renewal schedules.

Address-Confusion Attacks and Homoglyph Risks

While human-readable domains reduce simple transcription errors, they introduce social engineering and interface-level spoofing vectors. The most prominent attack classes stem from homoglyphs and address confusion.

Homoglyph attacks exploit character similarities across distinct alphabetic scripts. For instance, the Latin letter "a" (U+0061) is visually indistinguishable on standard screens from the Cyrillic small letter "а" (U+0430). If a decentralized registry allows unconstrained Unicode inputs, an attacker could register an identical-looking mirror of a prominent exchange, treasury, or decentralized finance interface. Users attempting to send funds manually to the visual representation of that name would instead route capital directly to the malicious actor's resolver address.

Modern naming protocols mitigate this threat through algorithmic input normalization. ENS applies normalization standards based on the Unicode Consortium's technical reports, stripping unsupported scripts, standardizing lower-case characters, and blacklisting confusable characters that do not belong to restricted character sets. Despite protocol-level sanitization, visual spoofing remains possible using subtle character substitutions, prefixes, and punctuation variants.

Address confusion also occurs when users confuse domain ownership with resolved records. An individual may hold an NFT representing a domain name in their personal wallet, but if the resolver configuration is pointed to an outdated or compromised address, funds directed to the name will not reach the current holder's active signer. Software integrations must rigorously confirm that both ownership and active resolution vectors align before dispatching high-value transactions.

Regulatory and Intellectual Property Realities

Decentralized naming systems operate at an uneasy boundary with traditional intellectual property frameworks. In the legacy internet ecosystem, trademark owners can settle domain disputes through the Uniform Domain-Name Dispute-Resolution Policy (UDRP) governed by ICANN, enabling legal authorities to reassign or cancel infringing domains.

Decentralized protocols deployed on permissionless blockchains have no centralized administrative root capable of unilaterally revoking or transferring domains registered on immutable contracts. If an entity registers a trademarked brand as a .eth or .sol domain, the trademark holder cannot simply issue a standard takedown demand to a centralized registrar. Resolving such disputes requires either direct negotiation, acquiring the private keys of the owner, or pursuing national court orders targeting the natural person behind the controlling address under standard trademark infringement laws.

Furthermore, government regulators such as the US Treasury Department's Office of Foreign Assets Control (OFAC) have added specific ENS domains to economic sanctions lists. While the underlying smart contracts continue to process state transitions mechanically without human discretion, regulated entities, hosted wallets, centralized exchanges, and node operators routinely integrate compliance software that blocks queries and transfers bound to sanctioned domain identifiers.

Common Misconceptions

  • Holding the domain NFT automatically updates the resolution destination. In protocols like ENS, the tokenized ownership record and the resolver mapping are technically separated. Purchasing a domain NFT on a secondary marketplace transfers the registry record to the buyer's wallet, but the resolver often continues directing transfers to the previous owner's address until the new owner issues a transaction to update the resolver records.
  • Decentralized domains are completely immune to censorship or freezing. While the protocol contract itself cannot be turned off arbitrarily, web applications, remote procedure call (RPC) providers, and centralized wallet frontends maintain the technical ability to blacklist domains from resolving inside their proprietary graphical interfaces.
  • All top-level domains are natively recognized by traditional web browsers. Domain extensions like .eth and .sol operate primarily on decentralized state machines and are not part of the traditional ICANN root zone. Standard browsers cannot resolve them natively without secondary software plugins, specialized DNS gateways, or alternative DNS-over-HTTPS configurations.

How This Connects to the Market

Blockchain naming systems have evolved from niche experimental utilities into foundational identity layers across the digital asset industry. Institutional custody providers, over-the-counter settlement desks, and retail wallets have adopted reverse resolution to mitigate the operational risk of routing transfers to erroneous addresses. As enterprise participation across cross-chain architectures deepens, naming services function as aggregated address books bridging multiple ledger environments through unified profiles.

Market infrastructure continues to trend toward integrated identity systems where a single readable domain maps not only to settlement addresses across Ethereum and Solana, but also to data endpoints, verifiable credentials, and decentralized communications. Monitoring protocol governance votes on fee adjustments, normalization standard upgrades, and legal developments surrounding offchain trademark enforcement remains critical for teams building identity infrastructure across onchain markets.

Questions this story raises

What happens to assets sent to an expired domain name?
Once a domain passes its expiration date and enters its grace period, active resolution records are disabled. Most modern wallets reject transactions targeting non-resolving names, preventing the transmission of assets. However, if an un-updated client routes a transfer using a cached address, the funds will go to whatever address was historically configured in the resolver.
Can two different users own the same .eth or .sol name?
No. Blockchain registry contracts enforce uniqueness at the protocol level. Because each domain maps to a single cryptographic hash derived through namehash algorithms, only one account can be recorded as the active owner of a specific domain string on that network at any given time.
How does reverse resolution differ from forward resolution?
Forward resolution translates a readable domain into a public blockchain address for payments. Reverse resolution performs the opposite lookup, taking an alphanumeric public key and verifying that the target account has explicitly set that domain as its public, primary identifier.
Can trademarks be legally seized from a decentralized naming service?
Because decentralized registry contracts lack administrative backdoors or centralized registry managers, courts cannot directly compel the smart contract to transfer ownership. Legal recourse typically requires court actions against the private key holder or blacklisting of the domain within commercial, centralized frontends and wallet applications.

References

  1. [1] Solana Documentation: Account Model and Program Architecture — Solana Foundation
  2. [2] EIP-137: Ethereum Name Service - Specification — Ethereum Improvement Proposals
  3. [3] ENS Documentation: Resolution and Architecture — Ethereum Name Service
  4. [4] EIP-181: ENS Support for Reverse Resolution of Ethereum Addresses — Ethereum Improvement Proposals
  5. [5] Unicode Technical Standard #39: Unicode Security Mechanisms — Unicode Consortium

Evergreen explainer written by Basis Desk's system and checked by an independent model pass for factual errors and advice language. Figures, fees and rules change — the references above are where to verify current specifics. Market figures marked "at the time of writing" come from live exchange data. Report an error: corrections@basisdesk.news · corrections policy.

The Daily Brief, in your inbox at 07:00 ET

Five stories, the numbers that moved, what to watch. Three minutes. No hype, no advice, unsubscribe in one click.

Not financial advice. Basis Desk publishes information, not recommendations. Crypto assets are volatile and you can lose what you invest.