Real estate is the largest asset class on Earth. A report by Deloitte projects that tokenized real estate could surge from under $300 billion in 2024 to about $4 trillion by 2035. The momentum is real, the technology is ready, and the appetite from both retail and institutional investors is growing. But almost everyone building in this space is ignoring a foundational problem — one that sits not in the smart contract layer, not in the legal wrapper, but in the address itself.
Where does a property NFT actually live on the internet? And who controls that address?
The Problem with Property NFTs Today
When you mint a real estate NFT today, the token points to a metadata URI — a web address that holds the property's details: location, title hash, floor plans, photos, legal documents. That address is typically hosted on a centralized server, a standard ICANN-registered domain, or at best an IPFS hash with no human-readable name.
Traditional domain ownership is not really ownership at all — it is a lease. A registrar issues you access to a name, and ICANN sits above the entire system. No government can seize your property title, but a registrar can let your domain expire or suspend it while you are not paying attention.
This creates a quiet but serious fragility: the NFT might be on-chain forever, but the address it points to can disappear overnight. A villa in Marbella with an immutable title deed that resolves to a dead link is not a decentralized asset — it is half of one.
The appeal of replacing a months-long closing process with near-instantaneous digital transfers is undeniable. But that promise only holds if every layer of the stack is as permanent as the blockchain itself — including the address.
What Real Estate NFTs Actually Need from a Namespace
To work properly, a real estate NFT needs its address layer to satisfy five things simultaneously:
1. Permanent ownership — The address cannot expire, be revoked by a registrar, or be seized by a government order. A property title that can be stripped of its domain is no more secure than a paper deed in a government registry.
2. No intermediaries — Traditional real estate transactions take about 50 days from offer to closing, with agents, notaries, escrow services, and lawyers consuming a significant portion of transaction value. The whole point of a Web3 property protocol is to remove those intermediaries — but if the namespace layer still depends on ICANN and centralized registrars, the intermediary problem is not solved, just moved.
3. Censorship resistance — ICANN is a centralized service with a single point of failure. If one part of the system fails, or a government applies pressure, the entire address can stop working. For cross-border real estate — where a foreign national is buying property in another jurisdiction — this is not a theoretical risk. It is a live one.
4. Native composability with NFT standards — The namespace needs to bind directly to the NFT token, not just point to it externally. The domain and the deed should be the same object, not two separate things linked by a fragile URL.
5. A full sub-namespace economy — A real estate protocol is not one property, it is thousands. The namespace layer needs to support a structured hierarchy: every listing, every lease, every fractional share getting its own permanent, discoverable address under one sovereign root.
No standard domain system — not .com, not ENS .eth — satisfies all five of these at once.
Why Handshake TLDs Solve All Five
Handshake is a decentralised blockchain whose only purpose is the permanent ownership of DNS root-zone names. Unlike ICANN — which controls the global root zone and can revoke, seize, or refuse to renew any domain — Handshake auctions root-level TLDs via an on-chain auction. The winner holds a covenant that represents ownership with no annual fees, no registrar above them, and no authority that can revoke it.
This is the critical distinction. When ROSSOBAY/ is registered on Handshake, nobody owns .rossobay except the protocol itself. Every second-level domain beneath it — villa42.rossobay/, lease.apt12.rossobay/, frac.mansion1.rossobay/ — is the protocol's own product, issued permanently, on its own terms.
Instead of leasing a name from a centralized registrar, you mint it as a token on the blockchain and store it directly in your crypto wallet. No renewal fees. No middlemen. No company that can flip a switch and make your address disappear.
For real estate, this permanence is not a nice-to-have. It is structural. A property title that lives at villa42.rossobay/ is as permanent as the Handshake blockchain — which means it is as permanent as Bitcoin. It cannot be seized, it cannot expire, and it cannot be taken down by a registrar policy change.
How ROSSOBAY/ Puts This Into Practice
ROSSOBAY/ is a Web3 real estate protocol built natively on the Handshake TLD. Every property in the ecosystem gets its own SLD — a permanent, human-readable address that serves as both the property's internet identity and its on-chain title deed anchor.
The naming convention is intuitive by design:
villa42.rossobay/— a 3-bedroom villa in Marbella, Spainoffice7b.rossobay/— a commercial office floor in Dubai DIFCplot99.rossobay/— a 2,000m² plot of land in Bali, Indonesialease.apt12.rossobay/— a tokenised rental agreement in Berlinfrac.mansion1.rossobay/— fractional shares in a Miami luxury mansion
Each SLD is bound to an ERC-721 NFT — the on-chain title deed. The NFT metadata carries the property's coordinates, area, legal document hash, IPFS links to photos and floor plans, and the Arweave transaction ID for permanent archival. A legal entity such as a Special Purpose Vehicle holds the physical property, and token holders own shares in that entity — ensuring digital ownership corresponds with legally recognised rights.
The result is a four-layer stack where every layer is permanent: the Handshake TLD at the root, the SLD as the property address, IPFS/Arweave for the data, and the EVM smart contract for the title deed and transfer logic.
The Namespace Economy That Follows
What makes Handshake uniquely powerful for real estate is not just the permanence of individual addresses — it is the economic architecture a sovereign TLD enables.
Under ROSSOBAY/, the protocol can issue SLDs as NFTs themselves, turning the namespace into a marketplace directory. Every new listing is a new SLD. Every rental generates a time-locked lease token. Every fractional share trades against the protocol's RBAY token on a DEX. A rigorous legal wrapper linking the on-chain NFT to an off-chain SPV operating agreement — with the blockchain ledger as the authoritative ownership record — is the model that has already been validated in court, including a German ruling in February 2025 that set a precedent for institutional adoption.
ENS .eth cannot replicate this. When a project builds on ENS, they do not own .eth — the Ethereum Name Service does. Their sub-namespace is a tenant, not a sovereign. Under Handshake, ROSSOBAY/ owns the root. Every SLD it issues is its own product, with its own economic weight.
A Clearer Way to Think About It
Here is the simplest way to understand why Handshake TLDs are the right place for real estate NFTs:
A property title is only as strong as the system that records it. For centuries, that system was a government registry — which is why titles can be forged, seized, and disputed across borders. Blockchain brings the record on-chain and makes it tamper-proof. But if the address pointing to that record can be taken down by a registrar or expired by a registry, the problem has not been solved — it has been decorated.
Handshake removes the last centralized dependency. The address and the asset are both permanent, both on-chain, and both owned outright. That is not a technical detail. That is the foundation of a trustless property market.
"The next trillion-dollar opportunity in Web3 is not DeFi or gaming — it is the tokenization of the physical world. Real estate is the foundation. ROSSOBAY/ is the protocol."
ROSSOBAY/ is an original Web3 real estate protocol concept authored by Sina Khoshtarkib Zenoozi, May 2026. For more on building on Handshake, explore LearnHNS.