How onchain names and domains are paid for and transferred
A client wants to acquire a premium onchain name. Maybe it’s a four-character .eth, a clean brand handle on a Web3 naming protocol, or a high-value .crypto tied to a major vertical. They’ve agreed on price. Now comes the part that actually matters to you: who pays what, to whom, in what form, and how does ownership actually move hands without either party taking on unnecessary risk. The mechanics of onchain name transactions are meaningfully different from anything in traditional domain brokerage, and those differences determine whether a deal closes cleanly or stalls in a confusion of wallets, gas estimates, and competing expectations.
What an onchain name actually is — and why it changes everything
Before you can manage a transaction, you have to understand what is changing hands. The Ethereum Name Service (ENS) is a decentralized protocol that lets users create simple, human-readable domain names for crypto wallets and other blockchain-based resources like decentralized applications, smart contracts, and websites. But the deeper point, the one that matters operationally, is that an onchain name is not a database record in someone else’s server. NFT domains are ERC-721 tokens owned by individual addresses. The ownership isn’t a license. It’s a token sitting in a wallet — and when it moves, the blockchain records it permanently.
The ENS uses a smart contract-based data repository called the registry to process and record ownership data for the network’s domains. To translate human-readable domains into machine-friendly crypto addresses, ENS uses a smart contract technology called resolvers, which function similarly to servers in the DNS model. The combination of a smart contract registry and resolvers allows ENS to operate securely on the Ethereum blockchain without centralized entities. There is no registrar that can pull a domain, no renewal department to call, no administrative hold placed by a third party. The implication for any professional facilitating these transactions is significant: the deal is exactly as clean as the transfer mechanics you set up, and exactly as irreversible once executed.
Domains are tokenized into Non-Fungible Tokens that can be traded, sold, or purchased, just like any other digital asset, enabling a fluid and robust marketplace for domain names. “Fluid” is accurate. “Robust” requires a professional who understands the specific settlement risks that don’t apply to traditional domain transactions, because here the payment and the transfer are two distinct events that must be choreographed.
The primary market: registration mechanics and first-ownership
Not every deal you touch will be a secondary market acquisition. Some clients want to register a name fresh — either because the name has never been claimed, or because it recently lapsed. Understanding the primary registration flow lets you advise on realistic timelines and costs from day one.
For ENS, the process involves two on-chain transactions separated by a minimum waiting period. Registering a name is nearly instant in concept, but users submit two transactions: first committing to registering the name, then actually registering it. In order to prevent front-running, these two transactions must be mined at least one minute apart. That anti-front-running mechanism exists because, on a public blockchain, anyone watching the mempool can see a pending registration and attempt to snipe the name. The commit-reveal pattern prevents that.
Payment occurs in ETH, and the domain gets minted as an NFT upon completion. The annual cost for ENS names follows a tiered structure based on character count: registration costs vary by name length — names with five or more characters cost $5 annually, four-character names cost $160 annually, and three-character names cost $640 annually. These are denomination-in-USD figures payable in ETH, which means the actual ETH amount fluctuates with market price at the time of transaction. Clients need to understand this. A name priced at $640 per year will require whatever amount of ETH equals $640 at the moment the transaction is signed, plus gas.
The Unstoppable Domains model works differently and is worth understanding because many clients confuse the two ecosystems. Unlike traditional domain names, users only pay a one-time fee to secure an Unstoppable Domain. Once you mint an Unstoppable Domain, you own it forever, or until you sell or transfer it. The absence of renewal fees is a genuine structural difference with real downstream implications for how you advise clients on the total cost of ownership and how you model the value of a name being held long-term.
On the minting side, the network choice matters for cost. Choosing to mint on the Polygon network rather than Ethereum eliminates NFT minting fees entirely. The domain minting process pushes domains from Unstoppable Domains’ database onto the blockchain and into a cryptocurrency wallet, and minting gives the owner full custody over the domain name. Until minting occurs, the registrant has a claim but not actual on-chain custody. This distinction is operationally relevant: a name that has been purchased but not minted cannot be transferred via wallet-to-wallet mechanics.
The secondary market: where deal professionals earn their value
Primary registrations are commodity transactions. Secondary market acquisitions — where the name already exists, is held by someone else, and must change hands through a negotiated deal — are where advisory skill determines outcomes. This is also where the payment and transfer problem becomes the central professional concern.
When a buyer wants a name that someone else already holds, the deal structure involves at least three distinct elements: price discovery, payment mechanics, and transfer execution. None of these are automatic.
Price discovery for onchain names
The price of an onchain domain depends on whether it’s being minted for the first time or sold on the open market. Secondary prices vary enormously — regular names might transact at low double-digit figures, while premium names or desirable handles in active categories can reach thousands or tens of thousands of dollars. Short names command substantial premiums. The blockchain ensures secure ownership transfer, and popular or short names often command premium prices in secondary markets.
The market for onchain names has a liquidity profile that differs meaningfully from traditional DNS. Names trade on NFT marketplaces like OpenSea, on protocol-specific marketplaces, and through direct peer-to-peer negotiation. A premium four-character .eth with strong brand relevance is not the same as a .com acquisition — the buyer pool, the valuation methodology, and the negotiating dynamics are all different. Your job as an advisor or broker is to frame that correctly for a client who may be coming to this market with DNS instincts.
Payment mechanics: crypto versus fiat, and the gap between them
Here is where many transactions stall. The name is an NFT on a blockchain. The seller wants to be paid. The buyer may have funds in a bank account, stablecoins in a wallet, or ETH sitting ready. Getting all three parties — payment, seller, and transfer — to align requires deliberate structure.
For fresh registrations through platforms like Unstoppable Domains, fiat payment is straightforward. These platforms accept credit and debit cards via Stripe, PayPal, Coinbase, and cryptocurrency. But in a secondary market deal between a buyer and a named seller, payment options depend entirely on what both parties agree to and what they’re set up to handle. A seller who holds the name in a cold wallet and wants payment in ETH or a stablecoin is not going to accept a wire transfer — at least not without a trust arrangement that substitutes for on-chain atomicity.
The core risk in any peer-to-peer onchain name transaction is sequencing: who moves first. If the seller transfers the name NFT first, they’re trusting the buyer to pay afterward. If the buyer pays first, they’re trusting the seller to transfer the name. Neither position is comfortable when deal values run into five or six figures. This is the exact friction that creates demand for deal professionals who understand how to structure the handoff.
Some marketplaces and platforms handle this internally by escrowing both sides of the transaction within their smart contracts, releasing payment to the seller and the NFT to the buyer simultaneously. This atomic structure is the cleanest resolution to the sequencing problem. The significance of on-chain instant settlement is that it ensures a trustless process by removing the need for either party to go first. When you’re facilitating a deal outside of a marketplace environment — in a direct negotiation between parties — replicating that atomicity requires either a trusted intermediary or a purpose-built smart contract mechanism.
What “transfer” actually means for ENS names
Transfer of an ENS name is not a single action. ENS names carry two distinct roles that must be separately managed: the registrant and the controller. Understanding this distinction is non-negotiable if you’re advising a buyer.
The registrant is the ultimate controller and owner of the ENS registration — it’s the address that registered and paid for the name. After securing the name, the registrant can set the controller and owner, and can assign and reclaim ownership of the name. The controller manages ENS records and subdomains, while the registrant controls the controller address and registration transfers.
Simply sending the ENS domain NFT to the other wallet will only transfer the registrant role but not the controller role of the domain. A buyer who receives only the registrant role cannot change the resolver records, cannot update the wallet address the name points to, and cannot fully control the name’s configuration. This is a material deficiency in a transfer, and it’s one of the most common ways name acquisitions go wrong when the parties attempt to execute without professional guidance.
A complete ENS transfer involves: transferring the controller role to the new wallet, and transferring the registrant role via the NFT transfer itself. The transfer data for ENS domains is viewable on the registry and proves current ownership rights. Both steps need to be confirmed on-chain, each requiring its own transaction and its own gas payment, before the buyer has unambiguous, complete control.
Each address change requires its own transaction. If the existing owner address is not the same as the manager or ETH address, it will not update all three roles automatically. The order of transactions is always: ETH record, then manager, then owner. A clean transfer requires the seller to execute these in sequence, and the buyer to verify each step on-chain before releasing any payment — or before confirming that payment has been received and final.
Resolver records and what the buyer inherits
A name is more than its ownership record. Once registered, the user can set the resolver — a smart contract that provides information about the Ethereum wallet address associated with the ENS name. The resolver functions as a mapping between the name and the address. When someone sends a payment to an ENS name, the resolver is queried to retrieve the associated address.
The buyer of a name needs to update the resolver records to point to their own wallet address. If they don’t, anyone who sends crypto to that name after acquisition will still be sending it to the previous owner’s address. This is not a trivial concern — it’s a live financial risk. Part of advising a buyer through an onchain name acquisition is making sure they understand that taking ownership of the NFT and taking functional control of where the name resolves are two separate actions that must both happen before the acquisition is operationally complete.
ENS supports over 100 different cryptocurrency addresses. A single ENS name can be configured to receive Bitcoin, Litecoin, and many other cryptocurrencies, making it a universal payment identifier across multiple blockchain networks and ecosystems. Each of those record entries must be updated by the new owner if the name is to function correctly post-transfer. That’s not a seller responsibility — it’s a buyer configuration step.
Renewal, expiry, and what happens to the deal if timing is wrong
ENS names expire. ENS-based Web3 domains require annual renewal fees. This creates a dimension of deal timing that doesn’t exist with Unstoppable Domains, and it creates genuine risk in any secondary acquisition.
Your domain enters a 90-day grace period where only you can renew it. After this period, it becomes available for public registration. If an acquisition closes and the name is close to its expiry date, the buyer may need to renew it immediately after transfer — at their own cost — or risk losing the name they just paid for. This should be surfaced and negotiated before deal close. Is the seller responsible for ensuring the name is renewed to a minimum forward term? Is the buyer taking the name as-is and accepting the renewal obligation? These are material deal terms.
For names acquired through platforms that manage custody on behalf of buyers, auto-renewal mechanisms exist to prevent the accidental loss of .eth domains through missed on-chain renewal deadlines. But buyers who take full self-custody into a personal wallet are entirely responsible for managing their own renewal cadence. Advising a client to set calendar reminders or use ENS app notifications is part of the handoff.
Unstoppable Domains names do not carry this risk. Once minted, an Unstoppable Domain is owned until sold or transferred, with no renewal fees. For clients who want to hold a name indefinitely without administrative overhead, that permanence is a meaningful advantage — and one that should factor into valuation discussions when comparing the two name ecosystems.
The multi-party payment problem
Most onchain name deals involving a professional facilitator create a payment distribution problem: the seller gets proceeds, the broker or advisor earns a fee, and the deal may involve other parties who are owed compensation. In a traditional DNS deal, this is handled through wire instructions and a closing statement. In an onchain transaction, that same distribution needs to happen on-chain — and doing it manually means either multiple transfers with multiple points of failure, or someone collects everything and then redistributes it, which creates a hold period that the parties may not have anticipated.
This is precisely the problem that a payment router like Shaka solves. The deal professional sets up a payment link before the funds move — defining who receives what, at what percentage, in which wallet. When the buyer sends payment, it moves instantly to each recipient according to the agreed split. There is no intermediate hold, no second step, no “I’ll send your portion after the funds clear.” The seller gets paid, the facilitator gets paid, and every party who earned a piece of the deal receives it the moment the transaction confirms.
That atomicity matters in onchain name deals for a specific reason: buyers are often already operating in a crypto-native mindset. They expect payments to be final. They expect settlement to be instant. A facilitator who handles the payment distribution with the same precision and speed as the transfer itself operates at the level of sophistication this market demands.
Practical deal structure: sequencing a clean close
Given everything above, the professional managing an onchain name acquisition has a responsibility to sequence the deal correctly from the outset. The following is not a checklist — it is the logic of how these transactions work when they work well.
Before any funds move, verify what the buyer is actually acquiring. Confirm that the seller controls both the registrant and controller roles. Confirm the current expiry date if the name is on ENS, and negotiate the renewal position as a deal term. Confirm the network on which the name is minted, because this determines where the transfer happens and what gas token is required.
Establish the payment structure clearly before the transfer begins. If the name has significant value, the sequencing risk is real: neither party should be expected to perform blind trust. Either the transaction occurs through a marketplace or protocol that handles it atomically, or you structure a clear order of operations that both parties agree to in advance. Define the payment currency — ETH, a stablecoin like USDC or DAI, or fiat routed through a platform — and confirm that the seller’s wallet is capable of receiving it.
Execute the transfer in the correct order. For ENS, the controller role should move before or simultaneously with the registrant transfer. Each step should be verified on-chain before the next is initiated. After transfer is complete, the buyer must update resolver records immediately. This is non-optional if the name is to function as intended.
Document the entire chain of events. On-chain transactions are their own receipt — every action is visible on the public ledger with a transaction hash and a timestamp. That transparency is an asset: it provides the permanent record of what happened, when, and to which addresses. Any professional managing these deals should be fluent in reading a block explorer and should provide their client with confirmation of each step as it completes.
The advisor’s edge in an opaque market
A key focus in transitioning to blockchain-based domain transactions is the enhanced control over assets that blockchain technology offers, which is an essential factor in driving adoption among established market participants. That enhanced control is real — but it comes with the requirement that someone in the transaction actually understands the mechanics. Most buyers and sellers in onchain name deals do not.
The professional who understands ENS role separation, who knows to verify resolver records post-transfer, who structures the payment distribution before the deal closes rather than apologizing for confusion afterward — that professional earns trust that extends well beyond a single transaction. The onchain name market is still early enough that expertise is sparse. The mechanics are documented in protocol repositories and support articles, but threading them together into a deal that actually closes, pays correctly, and leaves the buyer with full operational control of what they purchased: that is the work. The advisor who does it reliably will not be short of clients.
