# How to pay for a premium onchain name from a secondary seller
A practical guide for domain brokers, OTC desks, and settlement professionals on structuring and executing payment when acquiring a premium onchain name from a secondary seller.
---
The deal memo is signed. The price is agreed. The name — a short, category-defining `.eth` or a premium Web3 identifier — is sitting in a secondary seller's wallet. Now comes the part that most guides quietly skip: how, exactly, does the money move? Who gets paid, in what order, and how does everyone at the table confirm it is done?
That question matters more than it might first appear. Selling a premium domain is entirely different from listing a regular name on a marketplace. High-value names require discretion, negotiation skill, buyer reach, and trust. When those qualities are present in an acquisition, the closing mechanics had better match the quality of the work that got everyone to the table. For brokers, OTC desks, and settlement professionals closing these transactions, the payment leg is where reputations are made or broken.
This article walks through the payment problem in full — from why onchain names create unique settlement dynamics, to the parties typically involved, to how a single onchain payment routed through shaka.deal can give every participant simultaneous, final confirmation without a multi-step wire chain.
## Why onchain names are a distinct asset class at closing
Blockchain domains like `.eth`, `.crypto`, and `.zil` continue to gain users. These blockchain-based domains work without central servers, making them resistant to censorship. They connect smoothly with DAOs and cryptocurrency wallets, letting owners control their online presence directly. The system also supports digital assets and smart contracts, making domains more than just web addresses.
Blockchain-based naming systems such as Ethereum Name Service (ENS) and Handshake continue to gain traction among crypto communities. Although mainstream adoption is gradual, the secondary market for decentralized domains is expanding, presenting a new asset class for brokers.
That phrase — new asset class — is where the settlement complexity begins. A premium `.eth` name is an ERC-721 non-fungible token on Ethereum. Ownership is not recorded in a registrar's database; it is encoded in the chain's state. Transferring the name means executing an on-chain transaction that reassigns the token to a new controlling address. There is no "push the name to the new registrar" workflow, no WHOIS update to wait on, no five-to-seven-day propagation window. The transfer is either confirmed in a block or it has not happened. That binary, immediate nature of the asset side of the deal creates an expectation — and frankly a demand — that the payment side should match it.
Yet most premium domain transactions still rely on payment infrastructure designed for a slower world: wire transfers that may take one to three business days to clear internationally, ACH batches, or multi-step escrow processes where funds sit pending confirmation at each stage. The mismatch between an asset that settles in minutes and a payment that settles in days is not merely inconvenient. It creates a genuine window of counterparty risk.
The secondary market for domains has intensified, with more businesses willing to invest in premium domain names in order to achieve recognition and superior rankings quickly. That urgency — the buyer who needs the name now, before a competitor bids — only amplifies the pressure to close fast without creating new exposure.
## The typical parties in a premium secondary sale
Before mapping the payment flow, it helps to be precise about who is at the table. In a well-structured premium onchain name transaction, there are usually more than two parties. Understanding each one's role and their right to be paid is prerequisite to building a clean settlement.
**The seller.** This is the current on-chain owner of the name. They may be an individual domain investor, a portfolio company, or a protocol treasury. Their payment address is a wallet. They expect to receive the agreed net proceeds promptly and in the asset they negotiated — typically stablecoin or ETH, sometimes with a USD-equivalent floor.
**The buy-side broker.** A professional who identified the name for the acquirer, approached the seller, conducted due diligence on chain history and trademark risk, and managed the negotiation. A domain name broker helps buy or sell domain names, especially ones that are already taken, without making them public. A broker is important to help secure owned domains using their negotiation skills and market insights. The brokerage process makes buying or selling smoother by handling pricing and outreach, helping you avoid mistakes and saving time.
**The sell-side broker (where applicable).** In larger transactions, the seller also engaged a professional who helped position the asset, fielded inbound inquiries, and negotiated on their behalf. This party has a commission claim against the seller's gross proceeds.
**The settlement or closing agent.** For six- and seven-figure transactions, an independent settlement agent or closing attorney is often brought in to hold the instruction set — the agreed price, the split of proceeds, the wallet addresses — and to confirm that each step of the closing has executed correctly. Their role is not ceremonial. They provide the paper trail, the audit record, and the professional accountability that institutional buyers and their legal counsel require.
**The OTC desk (where applicable).** When the buyer needs to convert fiat to stablecoin or ETH at scale before the purchase, an OTC desk manages that conversion. OTC trades typically involve three parties: a buyer, a seller, and an intermediary who facilitates the trade. This intermediary could be a broker, a trading desk, or an OTC trading platform. The desk may also route the converted funds directly into the closing wallet on behalf of the buyer.
Each of these parties is a professional providing a service. Each has a right to their agreed share of the gross purchase price. The question is not whether they get paid — it is whether they all get paid cleanly, simultaneously, and with certainty, or whether the money moves in a queue that introduces delay, ambiguity, and friction at every step.
## How settlement is done today — and where the friction lives
The conventional workflow for a premium domain acquisition looks something like this. Buyer sends funds to the settlement agent. Settlement agent confirms receipt, then instructs the seller to initiate the name transfer. Seller transfers the name. Settlement agent confirms the transfer on-chain. Settlement agent then disburses the agreed split — net to seller, commission to buy-side broker, commission to sell-side broker — via separate wire instructions. Each wire is a new banking event with its own processing window. Each disbursement requires its own confirmation. The closing agent reconciles all of this and issues a final settlement statement.
The total elapsed time from "buyer sends funds" to "every party has confirmed receipt" can stretch across multiple business days, even when the actual name transfer took under five minutes. That asymmetry frustrates buyers and sellers alike. It also creates operational risk. If the seller's wire details were entered incorrectly, the error may not surface for 24 hours. If a broker is in a different time zone, confirmation of their disbursement may arrive outside business hours. If the settlement agent is managing multiple closings, the queue matters.
Each intermediary in OTC trading may have its own settlement process. The absence of standardized procedures adds a logistical challenge for traders and makes it difficult to ensure a secure and transparent trade settlement.
This is the gap that onchain payment routing closes — not by removing any of the professionals involved, but by collapsing the multi-step disbursement chain into a single, atomic transaction.
## What onchain settlement finality actually means
Before explaining how the routing works, it is worth spending a moment on what "final" means in an onchain context, because the word is used loosely and the legal and operational implications matter to every professional at the table.
Onchain settlement is the process of transferring final ownership of an asset and its payment on a blockchain, where the ledger update itself is the settlement. Onchain settlement replaces the multi-day, intermediary-heavy process of moving money and assets with a single blockchain transaction that transfers value and records final ownership at the same time.
On a proof-of-stake network like Ethereum, a transaction becomes technically final when it is incorporated into a validated block and subsequently confirmed. Where traditional settlement relies on institutional rules and operational procedures to establish finality, blockchains achieve it through cryptography and economic deterrence.
Practically: once a stablecoin payment is confirmed on Ethereum, it is done. There is no bank-side reversal window, no pending period, no clearing-house queue to pass through. The economic cost of reversing even a handful of confirmations makes rollback practically impossible. To unwind a confirmed transaction on a major proof-of-stake chain, a malicious actor would need control of a supermajority of validators and would incur massive slashing penalties. Billions in staked collateral would be automatically destroyed. This deterrent exceeds any comparable mechanism in traditional payment systems, where reversals can be initiated by a central operator, a court order, or a back-office correction.
For a settlement professional, this is highly significant. The moment the transaction confirms, the settlement statement is effectively self-executing and self-proving. The blockchain is the audit trail. The transaction hash is the receipt. No party needs to wait for a bank to confirm that a wire "cleared." Cleared and confirmed are the same event, occurring at the same instant.
## How a routed onchain payment works in practice
This is where shaka.deal enters the picture. Shaka.deal is a B2B onchain payment router on Ethereum. When a buyer initiates a payment, shaka.deal routes the total amount and distributes it simultaneously to every party at their preset shares — seller, buy-side broker, sell-side broker, closing agent — in one transaction. It routes; it does not hold. The funds move directly and immediately to their destinations.
The mechanics, in plain terms:
One routed payment, from instruction set to confirmation
Before closing, the settlement agent assembles the instruction setThe agreed gross purchase price. The wallet address of the seller. The wallet address of the buy-side broker and their commission percentage. The wallet address of the sell-side broker and their commission percentage. The settlement agent's own address if they are receiving a fee. These are the preset shares that shaka.deal will use to split and route the incoming payment.
The buyer sends a single payment to the shaka.deal routeOne transaction, covering the full gross amount. The buyer does not send separate payments to each party. They do not need to know any individual party's wallet address. They pay one amount, once.
Shaka.deal routes and distributes simultaneouslyIn that same transaction, the preset shares are applied and each party receives their portion. The seller sees their net proceeds arrive. The buy-side broker sees their commission arrive. The sell-side broker sees their commission arrive. All of this happens at the same block, at the same moment.
The settlement agent confirmsBecause every disbursement is contained in a single transaction hash, the settlement agent can point to one on-chain event and confirm the entire closing. There is no "waiting on the broker wire" and no "seller received but broker still pending." Done is done.
## A concrete scenario: closing a five-figure `.eth` name
Consider a specific scenario. A corporate buyer wants to acquire a four-character `.eth` name from a portfolio investor. The agreed price is $80,000 USD (approximately AUD 124,000 at a standard exchange rate). The deal was sourced by a buy-side broker on a 10% commission. The seller engaged their own broker, also on 10%, to be paid from gross proceeds. A settlement agent is coordinating the closing for a flat fee of $1,500 USD (approximately AUD 2,325).
Under the conventional sequential disbursement model:
- Buyer wires $80,000 USD to the settlement agent's client account.
- Settlement agent holds while the name transfer is initiated and confirmed on-chain.
- Settlement agent then wires: $64,000 to the seller (gross less two broker commissions), $8,000 to the buy-side broker, $8,000 to the sell-side broker, less the $1,500 settlement fee.
- Wait for each wire to clear.
- Reconcile and issue closing statement.
That is four separate disbursement events. Each one carries its own execution risk and processing time.
Under an onchain routing model using shaka.deal:
- The buyer converts $80,000 USD to an equivalent stablecoin (USDC, for example) via their OTC desk.
- The settlement agent pre-configures the shaka.deal route with the shares in the table below.
- Buyer executes a single onchain payment to the route.
- Every party receives their allocation in the same transaction.
- The name transfer, if also coordinated atomically or immediately after, completes the closing.
| Party | Share of the route | Amount on $80,000 |
| --- | --- | --- |
| Seller | 79.375% (net of commissions) | $63,500 |
| Buy-side broker | 10% | $8,000 |
| Sell-side broker | 10% | $8,000 |
| Settlement agent | 0.625% | $500 |
The settlement agent's 0.625% represents the $500 flat fee portion routed onchain, with the remainder handled separately if applicable — or the full flat fee configured into the percentage.
The settlement agent has one transaction hash to record in the closing file. Every party has confirmed receipt in the same instant. There is no queue.
## A second scenario: OTC-facilitated acquisition with a multi-party seller structure
Premium onchain names sometimes come with more complex ownership on the seller side. Consider a `.eth` name jointly owned by two co-founders of a dissolved startup, managed through a multisig wallet. The agreed sale price is $210,000 USD (approximately AUD 326,000). The proceeds must be split equally between the two co-founders. A domain broker represented the sellers on a 12% commission. A buy-side acquisition specialist represented the corporate acquirer on a 10% commission. A closing attorney is coordinating.
Here, the payment parties are: two co-founders (39% each of gross, after commissions), sell-side broker (12%), buy-side broker (10%), closing attorney (flat fee).
Without clean routing, this closing requires five disbursement events and creates coordination overhead on the seller side that the co-founders, their counsel, and the closing attorney all have to verify independently. If one wire is delayed, the closing is not confirmed until the last one settles.
With shaka.deal, the closing attorney pre-configures all five wallet addresses and their respective shares. The OTC desk converts the buyer's fiat at the agreed rate and executes a single stablecoin payment to the route. Every party's allocation lands simultaneously. The closing attorney issues the final settlement statement immediately, with a single transaction hash as the supporting document.
The professional value of the closing attorney is not diminished here — in fact, it is enhanced. They are the party who assembled the instruction set correctly, coordinated the name transfer, and issued the legal closing documentation. The routing tool handled the payment mechanics precisely as instructed. That is what good tooling does: it lets professionals spend their expertise on the work that requires judgment, and automates the parts that just need to execute correctly.
## What brokers should know before configuring a route
A few operational notes for domain brokers and settlement agents who are new to onchain routing:
**Agree on the payment asset in the deal memo.** USDC, USDT, ETH — different sellers have different preferences. Some may want USD-denominated stablecoin to avoid volatility between closing and their own conversion event. Others may prefer ETH if they intend to hold. This should be negotiated and fixed in the deal memo, not left to closing day. Document it alongside the agreed price, commission splits, and wallet addresses.
**Time the name transfer relative to payment confirmation.** On Ethereum, the name transfer and the payment are two separate transactions unless a more sophisticated atomic swap arrangement is used. The conventional approach is: payment confirms first, then the seller initiates the name transfer. This ordering is the seller's protection. The settlement agent coordinates both steps and confirms completion of each. Some platforms and smart contract arrangements allow for atomic delivery-versus-payment — where name and funds move in the same block — and these are worth exploring for high-value deals.
**Document the shaka.deal route configuration in the closing file.** Just as a closing attorney files the escrow instruction letter, they should file the record of how the route was configured — the preset shares, the addresses, the total amount routed. This is the closing document. It sits alongside the transaction hash and provides the human-readable explanation for what the blockchain record shows.
**Cross-border tax documentation is still your responsibility.** The routing layer handles the payment mechanics. It does not handle tax reporting, jurisdictional compliance, or the broker's obligation to issue the appropriate documentation to their client. Those responsibilities remain exactly where they always were: with the licensed professionals managing the transaction.
## Why the market is moving in this direction
Premium domains are increasingly viewed as valuable digital real estate. In a digital landscape where virtual real estate is becoming as valuable as physical property, the domain market has undergone a remarkable transformation, with the industry witnessing unprecedented growth driven by emerging technologies and shifting user behaviors. As artificial intelligence reshapes how we select and value domain names, and blockchain technology introduces new possibilities for digital ownership, we're seeing a fascinating evolution in how businesses and individuals stake their claim in the online world.
ENS domains integrate with traditional DNS through a bridge, allowing `.eth` names to function like regular websites in some contexts. The infrastructure supporting `.eth` is mature, with robust tooling, established marketplaces, and deep liquidity for premium names.
As the asset class matures and as deal values climb, the professionals who serve this market will be held to higher standards on the closing side. Institutional buyers will not accept a premium acquisition process where the payment confirmation takes three business days while the asset confirmed in five minutes. Corporate legal teams will want a cleaner audit trail. Sellers who are portfolio managers — 125 addresses hold half of the domains registered in ENS, and around 1,600 addresses hold more than 10 domains each; these figures point to a significant number of domains being purchased for reselling — will seek closing processes that match the sophistication of their holdings.
The professionals who adapt their closing workflows first will have a clear competitive advantage. Not because they automate away their value — the negotiation, the due diligence, the legal coordination, the institutional relationships remain indispensable — but because their closings are faster, cleaner, and more certain.
## The settlement agent's role in an onchain closing
It is worth being explicit about this, because onchain tooling sometimes carries the misconception that it reduces the need for professional coordination. The opposite is true for high-value transactions.
The settlement agent's role in an onchain premium name closing includes: verifying the seller's right to transfer the name (checking that the wallet controlling the ENS token is the wallet that will initiate the transfer); confirming all wallet addresses through test verification; configuring the payment route with the agreed split; coordinating the sequence of events — payment first, transfer second, confirmation last; issuing the closing statement with the transaction hash and the settlement breakdown; and maintaining the closing file in a form that will satisfy the parties' legal and accounting requirements.
None of that is mechanical. All of it requires professional judgment and professional accountability. What changes with onchain routing is that the disbursement step — historically the part that added the most delay and the most reconciliation overhead — is reduced to a single confirmed transaction. The professional's time is freed from chasing wire confirmations and redirected toward the judgment-intensive work.
Brokers bring three things you usually can't get by listing alone: access to qualified buyers, expert pricing and valuation, and discreet, professional negotiation — all backed by escrow and payment mechanisms to protect both sides. Onchain routing through shaka.deal strengthens that final piece — the payment mechanism — without touching the first three. The broker still brings the buyer, sets the price, and manages the negotiation. The settlement infrastructure just ensures that when the closing table is ready, everyone gets paid in the same instant, with certainty.
## Putting it together: a closing checklist for onchain name transactions
For settlement professionals, brokers, and OTC desks who want to standardize their workflow for premium onchain name acquisitions, here is a practical framework:
**Pre-closing (typically two to three business days before):**
- Confirm the agreed gross price in USD (and AUD equivalent if applicable) and the denominated payment asset (USDC, USDT, ETH).
- Collect and verify wallet addresses for every party: seller, buy-side broker, sell-side broker, settlement agent.
- Execute a small test send to each address and confirm receipt.
- Confirm commission percentages and flat fees; express everything as percentage shares of the gross payment for route configuration.
- Document the route configuration in a signed instruction letter, countersigned by both parties.
**Closing day:**
- Confirm seller still controls the ENS name (check on-chain).
- Buyer (or OTC desk on their behalf) executes the single payment to the shaka.deal route.
- Confirm the transaction hash.
- Seller initiates the name transfer transaction.
- Settlement agent confirms name transfer on-chain.
- Issue final settlement statement with transaction hash, split breakdown, and transfer confirmation.
**Post-closing:**
- Each party issues their own tax documentation as required by their jurisdiction.
- Settlement agent archives the closing file.
- Buyer confirms name is now resolving to their configured wallet address.
This workflow is cleaner, faster, and more auditable than the sequential-wire alternative. More importantly, it is professional. It reflects the sophistication that premium onchain assets deserve at the closing table.
## Final note on the market
ENS has surpassed 2.7 million registered domains, and Unstoppable Domains exceeds 4.6 million registrations. The secondary market that has grown alongside this inventory is increasingly institutional. Deals are larger. Buyers are more sophisticated. Sellers are more experienced. The professionals who close these transactions — brokers, settlement agents, OTC desks, closing attorneys — are doing substantive work that deserves substantive tooling.
Shaka.deal was built for exactly this environment: B2B onchain transactions where multiple parties have legitimate claims on the same payment, where certainty matters, and where the closing needs to happen cleanly and simultaneously rather than in a queue. One incoming payment. Preset shares. Simultaneous distribution. Final settlement. That is the spine of every clean closing — and it is what every professional in this market deserves to offer their clients.