# How to sell an onchain name and settle in one transaction

A practical guide for domain brokers, OTC desks, and settlement professionals on how onchain payment routing collapses the multi-step settlement of a name sale into a single, final transaction.

---


The sale of a premium onchain name — a short .eth, a category-defining .crypto, a tokenized legacy domain — is not a simple two-party handshake. By the time a deal reaches closing, there is typically a seller, a buyer, a broker who sourced one or both sides, sometimes a co-broker on the other end, and occasionally a finder or referral party who introduced the lead. Each of those parties expects to be paid. Each payment is negotiated separately. And in the conventional workflow, each payment arrives separately — if it arrives at all.

This article is written for the professionals who run those closings: the domain brokers, OTC desk operators, settlement agents, and closing coordinators who spend meaningful time not on the deal itself, but on the disbursement process that follows it. The question it answers is precise: how do you compress all of that into one transaction that pays everyone, simultaneously, with finality, the moment the buyer sends funds?

The answer is onchain payment routing — specifically the kind that shaka.deal was built to provide.

## The anatomy of a name sale and why settlement lags

To understand where the friction lives, it helps to walk through a realistic deal.

A seller holds a four-letter .eth name they registered years ago. A broker finds a buyer — a fintech company that wants the name as its primary Web3 identity handle. Owning a premium .eth works like holding a premium .com domain, linking a company's Web3 wallets to its existing brand. The strategic value is real. The buyer is motivated. The negotiation takes three weeks and lands at $180,000 (approximately AUD 275,000).

Now the settlement mechanics begin.

Domain brokers are professionals who negotiate domain purchases and sales on behalf of their clients, handling everything from initial contact to final transfer. In a typical deal, the broker's commission comes out of proceeds. In sell-side representation, the seller pays from their proceeds. Some high-value deals involve split commission structures where both parties contribute. If there are two brokers — one representing the seller, one representing the buyer — both commissions must be accounted for before the seller sees a dollar. The closing agent or escrow service coordinates the sequencing.

Escrow service charges are variable, typically ranging from under 1% for high-value transactions to around 2–3% for smaller deals. Escrow protects both parties by holding payment until the domain transfers successfully. That protection is necessary and professional. But it introduces a temporal gap: the buyer funds escrow, the domain is verified and transferred, escrow releases payment to the seller, the seller then cuts a separate payment to the broker, and if there is a co-broker, that payment flows again. 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.

Each hop introduces delay. Each delay is a window for dispute. Each separate wire or crypto transfer requires its own confirmation, its own reconciliation entry, and its own moment of trust.

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.

For deals done in fiat, this multi-step disbursement can stretch across several business days. For deals done in stablecoins — increasingly common in the onchain name market — there is no technical reason for the delay. The rails are available instantly. But the workflow still sequences payments one after another because no one has set up a routing layer to handle them in parallel.

That is the specific problem onchain payment routing solves.

## What onchain names actually are, and why they complicate settlement

Before getting into the mechanics of the routing solution, it is worth being precise about what is being sold.

Blockchain domains are human-readable addresses — like yourname.eth or brand.crypto — minted as unique tokens on public blockchains. Unlike traditional domain names managed through ICANN's centralized Domain Name System, blockchain domains are stored in smart contracts, giving owners cryptographic control over their digital property.

The Ethereum Name Service is a system of smart contracts on the Ethereum blockchain that allows users to own domain names like vitalik.eth. "Ownership" here means possession of a non-fungible token (NFT) that lives on the Ethereum blockchain. The name is the token. Transfer the token, transfer the name. There is no registrar push, no auth code, no WHOIS update to wait on. The ownership change is atomic and immediate.

An ENS .eth name lives entirely on Ethereum. It resolves through ENS-aware wallets and apps, not in a plain browser address bar. The value of a short or category-relevant .eth is as a payment routing identity and brand anchor — not as a website URL.

The three major platforms are Ethereum Name Service (ENS) with over 2.7 million .eth domains, Unstoppable Domains with 4.6+ million domains across extensions like .crypto and .nft, and Handshake (HNS) which offers decentralized top-level domains. Each of these ecosystems has produced a secondary market for premium names, and each sale in that market carries the same multi-party disbursement problem described above.

What makes onchain names different from traditional domain sales — and what makes the settlement problem more tractable — is that the payment leg of the transaction is already happening on the same rails as the asset transfer. The buyer is typically paying in USDC, USDT, ETH, or another onchain asset. The seller receives an onchain asset. The brokers, if they accept onchain payment, can also receive their shares onchain. Every party has a wallet. The preconditions for a single-transaction settlement are already met. The only missing piece is a router that knows how to split one incoming payment and fan it out to all recipients simultaneously.

## How a payment router changes the settlement structure

A payment router like shaka.deal accepts one inbound transaction and distributes it to multiple wallet addresses in the same block, according to preset percentage shares. The router never holds funds — it moves them. The configuration is set before the payment arrives: wallet A gets X%, wallet B gets Y%, and so on until the shares sum to 100%. When the buyer sends the agreed amount to the routing address, every party receives their portion in the same transaction, at the same moment, with the same finality.

Settlement finality — the legal moment when a transfer becomes unconditional and irrevocable — lies at the heart of financial stability. When settlement is slow, uncertain, or exposed to after-the-fact reversals, the system must absorb significant credit, liquidity, and operational risks.

With a conventional multi-hop disbursement, finality for each party arrives at a different time. The escrow service achieves finality when it releases. The seller achieves finality when the wire clears. The broker achieves finality when the seller pays out. There is also atomic settlement — the ability to exchange assets instantly and simultaneously. It eliminates counterparty risk by ensuring that both sides of a transaction are completed or cancelled together, with no exposure in between.

With a routing transaction, finality is simultaneous. Settlement plays a key role in reducing counterparty risk and ensuring payment finality. Once a transaction is settled, ownership is transferred, and the transaction is irreversible. This eliminates ambiguity and reinforces trust between parties.

For a domain broker who has managed dozens of closings, this changes the operational posture entirely. Instead of coordinating four separate outbound payments and waiting for each confirmation, the closing coordinator sets one routing configuration at the start, shares the routing address with the buyer, and the moment the buyer sends, the deal is done. Not "done pending confirmation." Done.

T plus zero, or instant settlement, means the trade settles the moment it is executed, which atomic settlement on a blockchain makes possible because a smart contract can complete both legs simultaneously. Moving from T plus two to T plus zero frees capital immediately and shrinks the risk window from days to seconds.

## A concrete scenario: the $180,000 .eth sale

Return to the deal described at the top. A four-letter .eth selling for $180,000 (AUD 275,000). Two brokers. An escrow/settlement coordinator. Here is how the disbursement might be structured through shaka.deal.

The sell-side broker negotiated a 10% commission on gross proceeds: $18,000 (AUD 27,500). The buy-side broker negotiated 5% from the buyer's side, meaning the buyer is effectively paying $189,000 (AUD 288,750) total — $180,000 for the name and $9,000 as the buy-side broker's fee embedded in the transaction. The settlement coordinator charges a flat closing fee, say $1,200 (AUD 1,833), which the seller agreed to bear from proceeds. The seller's net is $180,000 minus $18,000 broker commission minus $1,200 closing fee = $160,800 (AUD 245,667).

In a single-transaction model, the total buyer payment of $189,000 (AUD 288,750) flows to a shaka.deal routing address configured as follows:

| Wallet | Share | Amount | In AUD |
| --- | --- | --- | --- |
| Seller | 85.08% | $160,800 | AUD 245,667 |
| Sell-side broker | 9.52% | $18,000 | AUD 27,500 |
| Buy-side broker | 4.76% | $9,000 | AUD 13,750 |
| Settlement coordinator | 0.63% | $1,200 | AUD 1,833 |

The buyer sends one payment. Four wallets receive their shares in the same block. The seller does not need to distribute anything. The brokers do not need to chase a payout. The settlement coordinator does not need to cut a separate invoice and wait for the seller to act on it.

The token transfer — the actual ENS name — moves in a linked transaction, either immediately before or after, coordinated by the settlement agent. That part of the workflow remains exactly as professional and careful as it would be in any high-value name transfer. The improvement is entirely on the payment side: where there used to be four sequential disbursements, there is now one.

This is not a simplification for the benefit of unsophisticated parties. It is a precision instrument for professionals who understand that the closer a deal is to a single atomic event, the less surface area exists for disputes, delays, and errors.

## The multi-broker scenario and why preset shares matter

One of the more delicate negotiations in any brokered name sale is the commission split when two brokers are involved. If a broker is involved in a transaction, the party who retained that third party is solely responsible for the third party's fees and commissions and indemnifies the other party for any such claims that may arise. This provision attempts to avoid the situation where the transaction is completed and a broker pops up and makes a claim for a commission.

Disputes about broker commissions after a deal closes are not hypothetical — they happen. And they happen precisely because the payment and the agreement are separated in time. The agreement is made during negotiation; the payment happens at closing; and if there is any ambiguity in the agreement or any change in the deal structure between negotiation and closing, the disbursement becomes a negotiation itself.

Preset shares in a routing configuration eliminate this ambiguity. The configuration is the agreement, expressed in code, visible to all parties before the buyer sends a single dollar. Everyone can verify their wallet address in the routing setup. Everyone can confirm the percentage. If there is a disagreement, it surfaces before the money moves — not after. And once the buyer sends, the distribution is automatic, simultaneous, and not subject to anyone's discretion or delay.

This is particularly valuable in deals where the two brokers have never worked together and have no established trust relationship. Brokers provide discretion, negotiation expertise, and access to private buyer and seller networks. They are not accountants. Asking a sell-side broker to pay a co-broker from their gross commission receipt — on a tight timeline, from a wallet they may not have fully funded at that moment — is an operational ask that can go sideways. Routing removes that ask entirely. Each broker receives their share directly, from the buyer's payment, in the same transaction.

## Finality as a feature, not just a technical property

Settlement professionals who work primarily in traditional finance sometimes treat blockchain finality as a curiosity or a risk factor. It is neither. It is the most operationally useful property of the underlying rails, and it is underused in the name sale market.

Finality is the guarantee that past transactions in a blockchain network cannot be altered, reversed, or cancelled. Its primary purpose is to provide absolute certainty to users, merchants, and smart contracts that a transaction is permanently settled and digital assets are secure.

In a name sale settled through onchain routing, this means the seller's proceeds land in their wallet and stay there. The broker's commission lands and stays. The coordinator's fee lands and stays. There is no reversal window, no pending state, no "waiting on the bank." The transaction is a permanent entry in a public ledger that any party can verify at any time.

When a payment settles via stablecoin on a fast-finality chain, settlement is atomic: clearing and settlement merge into a single operation. There is no batch processing, no interbank settlement delay, and no regulatory reversal window. The recipient has full, irreversible custody of the funds within seconds.

For a closing coordinator who has previously managed a disbursement where a wire was recalled three days after closing — a rare but not impossible event — the permanence of onchain settlement is not an abstraction. It is the specific feature that makes the deal truly done.

## What the settlement professional's workflow actually looks like

Integrating shaka.deal into a name sale closing is not a technical overhaul. It is one additional step in a workflow that professionals already know well.

<figure class="fig">
<figcaption><b>The closing workflow with a routing address</b><span>From wallet collection to reconciliation</span></figcaption>
<ol class="steps">
<li><b>Before closing</b>The settlement agent collects wallet addresses from all parties — seller, sell-side broker, buy-side broker, any other named recipients. Shares are agreed in the purchase and sale agreement or in a separate disbursement instruction document, exactly as they would be in a traditional closing. The agent configures the routing address in shaka.deal with those shares and verifies the configuration with each party.</li>
<li><b>At closing</b>The buyer receives a single payment address — the routing address — and the agreed total amount. The buyer sends one transaction.</li>
<li><b>Settlement</b>shaka.deal routes the inbound payment to all configured wallets simultaneously. Each party receives their share in the same block. The transaction hash is the closing record. Any party can look it up on a public block explorer and confirm their receipt without asking anyone else.</li>
<li><b>Post-close</b>The settlement agent's reconciliation is a single line item: one inbound, one transaction hash, four outputs. No chasing, no follow-up, no "did you receive it?" messages.</li>
</ol>
</figure>

This workflow is not speculative. It is a direct application of what a non-custodial payment router does. The coordination and trust that a closing professional brings to the deal — verifying the name transfer, managing the purchase agreement, protecting both parties' interests during the handoff — remains exactly as important as it has always been. The improvement is that when it comes time to distribute proceeds, the mechanics match the quality of the work that got the deal to closing.

## Handling deal variations: earnest deposits, phased payments, and co-ownership

Not every name sale closes in a single payment. Some deals involve an earnest deposit to take a name off the market while due diligence is completed, followed by a balance payment at close. Others involve installment structures for very large transactions. Some names are co-owned, with two or more sellers each holding a fractional interest.

Each of these variations fits within the routing model.

For an earnest deposit scenario, a routing configuration can be set for the deposit amount — directing, for example, a portion to a seller wallet and a portion to a settlement coordinator wallet — with a separate configuration prepared for the closing balance. The two transactions are independent but both transparent.

For installment payments, each installment gets its own routing transaction. The shares are identical across all installments. There is no risk that the second installment is distributed differently from the first, because the configuration is fixed. Every party's running total is visible on-chain.

For co-owned names — say, a .eth registered jointly by two founders who are now selling — the routing can include both seller wallets at their respective ownership percentages, alongside broker and coordinator shares. The routing configuration makes the co-ownership disbursement explicit and automatic. Neither seller has to trust the other to forward their portion after receiving a combined payment.

Instant, around-the-clock settlement requires institutions to manage liquidity continuously instead of within business-day cycles, a real change to how treasury operations work. For domain market professionals, the practical implication is simpler: a deal that closes on a Friday evening settles completely by Friday evening, because the routing transaction does not observe business hours.

## Why this matters for the onchain name market's next phase

ENS registration gas costs dropped roughly 99% after Ethereum's 2025 scaling upgrades, removing its biggest historical cost disadvantage. Lower registration costs mean more names in circulation, which means a more active secondary market, which means more transactions flowing through brokers and settlement professionals. The volume is growing. The deal complexity is growing with it.

In Web3 environments, address readability directly affects payment security, user experience, and the efficiency of identity verification. Traditional blockchain interactions rely on lengthy string addresses that are hard for users to remember and prone to mistakes during transfers, approvals, or contract calls. The premium placed on short, memorable onchain names is only going to increase as more protocols and companies adopt onchain identity as a primary channel. The names being sold today for five figures will be the reference transactions for an industry that is still formalizing its settlement practices.

Onchain domain platforms in 2026 increasingly lean into bridging traditional DNS with onchain ownership primitives. The value proposition is simple: a domain becomes an identity handle that can route payments, unify profiles, and reduce address errors. As that value proposition becomes mainstream, the professionals who close these deals need settlement infrastructure that matches the speed and finality of the underlying asset class.

A name that transfers in one block should settle in the same block. A broker who negotiated the deal in good faith should not wait three days to confirm their commission arrived. A seller who agreed to distribute proceeds among multiple parties should not bear the operational burden of executing those distributions manually.

One inbound payment. Preset shares. Simultaneous distribution. That is the model shaka.deal is built for, and it is the natural fit for a market where the asset, the payment, and the parties are already operating on the same chain.

## Getting started: what professionals need to configure a routing transaction

For a settlement agent or closing coordinator ready to use shaka.deal for a name sale, the practical requirements are minimal.

Collect wallet addresses for all parties before closing. Agree on share percentages in writing as part of the deal documentation — this is no different from how disbursement instructions work in any closing. Configure the routing address in shaka.deal with those shares. Share the routing address and the total payment amount with the buyer. When the buyer sends, the distribution is automatic.

The closing record is the transaction hash. It is public, permanent, and verifiable by any party at any time without requesting documentation from the settlement agent. That transparency is not a loss of professional control — it is the most auditable closing record in the industry.

For market professionals who have spent years managing the gap between when a deal closes and when everyone actually gets paid, that gap is now optional. The technology to close it exists. The only step remaining is using it.