Why the real estate industry's data problem isn't a data problem — and what happens when every US residential property has a persistent, cryptographically verifiable digital identity.
Every residential property transaction operates on an assumption that no one has ever formally enforced: at closing, the seller relinquishes digital control, and the buyer receives it.
For physical assets — keys, deeds, locks — this assumption is self-enforcing. You hand over the key. You change the lock. The transfer is real and observable.
For digital infrastructure, the assumption is entirely fictional.
A smart lock paired to the previous owner's phone does not unpair at closing. A security system tied to their account does not disconnect. A thermostat still in their app, a camera still sending footage to their cloud, a garage controller still accepting their credentials — none of these facts appear in any transaction record. No disclosure form captures them. No closing process addresses them.
A seller may factory reset a device. They may delete an account, transfer ownership in an app, or represent at closing that all connected systems have been cleared. No one verifies this. No inspector checks it. No title agent confirms it. The disclosure form has a signature line — it does not have a proof-of-execution line. There is no cryptographic record of a factory reset, no timestamped log of an account deletion, no independent witness to the action. The seller's word is the only evidence, and it is buried in a stack of documents no one reads after the keys change hands.
And if the seller did not take those steps — if the reset never happened, the account was never deleted, the credential was never revoked — there is no witness, no log the new owner controls, and no record that survives the transaction. Any subsequent access may exist in a manufacturer's cloud server in another jurisdiction, behind a terms-of-service wall, accessible only to the account that still holds the credential. The new owner has no standing to request it. Law enforcement has no standardized mechanism to retrieve it. The closing agent who processed the deed has no awareness it occurred. Ownership transferred. Accountability did not.
Seven US states have introduced language touching connected devices in their standard purchase agreements. Pennsylvania goes furthest — Section 10, Seller Representations, Subsection H requires the seller to make "a reasonable effort to clear all data stored on all IoT devices" and disconnect personal devices prior to settlement. The paragraph survives settlement. It is the most explicit IoT clause in any US residential contract today.
It is also technically unenforceable as written. A factory reset disconnects a device from the local network — it does not remove the previous owner's cloud credentials, revoke their app access, or terminate their account association with the manufacturer. No inspector verifies the seller's work. No protocol defines what "cleared" means for a Nest account, a Ring subscription, or a SimpliSafe system that the buyer now owns the hardware but the seller still controls the cloud instance of. The buyer is explicitly told to do remediation work after closing — on a system they have no visibility into and no certified baseline for.
The previous owner can, in many cases, still open the front door. Seven states acknowledge this problem exists. None of them have a mechanism to verify it was resolved.
The industry has a name for the accumulated digital systems affixed to a property: we call them Smart Device Fixtures (SDF). They are not personal property — they are fixtures. They are not portable — they are physically installed. But unlike every other fixture disclosed in a residential transaction, their operational state, account associations, and access permissions are completely invisible at closing. A "reasonable effort" clause surviving settlement creates liability exposure, not compliance. It gives buyers a legal argument after something goes wrong — not a verified record that nothing did.
This is the Ghost Device Problem. Recognized in seven states. Unsolved in all fifty.
Before you can document what's in a property, the property needs an identity that exists independently of who owns it, who sold it, and what systems are currently installed.
This sounds obvious. It has never been done.
Every existing property data system — MLS, county assessor, title databases, Cotality (formerly CoreLogic CLIP) — is retrospective. It matches data to a property record that was created after some transaction or registration event. The identifier follows the data. The property has no pre-existing digital identity before that event.
MyHOME ID (MYHID) is fundamentally different. It is deterministic — generated from the property's address data through a salted key derivation function, producing the same identifier regardless of which institution queries it or how they format the address. It is pre-instantiated — it exists before any transaction, before any device is installed, before any data event occurs. It is on-chain — anchored to the Ethereum blockchain via a national Merkle root structure covering 138M+ US residential properties.
The contrast with Cotality (CLIP) is instructive. CLIP is a retrospective system: it matches incoming property data to existing records, creating an identifier after the fact. CLIP has no cryptographic anchor. It has no on-chain commitment. It is a lookup table, not an identity layer. MYHID is a pre-existing digital identity — generated before any data event, anchored on a public blockchain, deterministic across every system that queries it.
138M+ US residential properties have MYHID vaults already generated, already anchored, already waiting. Four regional Merkle manifests — Northeast (18,799,009 properties), West (36,322,545), Midwest (39,026,722), South (43,488,149) — are committed to Ethereum and pinned to IPFS. A single national root (MYHID_ROOT_02) commits all four regions into one canonical keccak256 hash, anchored July 27, 2026. ROOT_01 remains on-chain as the prior version; the underlying regional datasets and manifests were unchanged. These are not promises. They are verifiable facts, auditable by anyone on Etherscan today.
| Region | Properties | Anchored |
|---|---|---|
| Northeast | 18,799,009 | Ethereum — Feb 24, 2026 |
| West | 36,322,545 | Ethereum — Mar 9, 2026 |
| Midwest | 39,026,722 | Ethereum — Mar 9, 2026 |
| South | 43,488,149 | Ethereum — Mar 9, 2026 |
| National · MYHID_ROOT_02 | 137,636,425 | Ethereum — Jul 27, 2026 · Block 25,628,067 |
Nobody calls a CARFAX® report an RWA. It doesn't give you equity in the car. It tells you what happened to it — accidents, ownership transfers, odometer readings — in a format that's verifiable at the point of sale. The KODA Metadata Certificate is the CARFAX® for the home's digital infrastructure.
The VIN is the identity layer: a permanent, deterministic identifier that follows the vehicle across every ownership cycle. MYHID is that layer for residential property — pre-instantiated, cryptographically anchored, independent of any transaction event. The site at myhomeid.com positions it plainly: vehicles have VINs, real property has title and APN, the home's digital infrastructure now has MYHID.
But a VIN alone doesn't tell you whether the car was in an accident, who owned it last, or what condition its systems are in today. For that, you need the report. The record. The verified history that a buyer, a lender, or an insurer can actually use at the moment of transfer.
A Verified Infrastructure Asset (VIA) is a cryptographically verifiable record of the operational state of digital systems affixed to real property at a specific point in time. It answers a different question than ownership. It answers: what was here, who confirmed it, and what state was it in?
VIA records are generated through the SL8 Audit process. A multi-modal hardware scanner — the SL8 Access Point — is deployed at the property. It passively receives wireless signal emissions from installed devices across multiple protocols: Wi-Fi, BLE, Zigbee, Z-Wave, Thread. It does not connect to devices. It does not require credentials. It detects presence and extracts device metadata from broadcast traffic. The Access Point is initiated and controlled by the SL8 iOS or Android application — the agent must be physically present with the app running to perform the scan. The Access Point does not operate autonomously.
That metadata — device identifiers, manufacturer data, service advertisements, signal characteristics — is transmitted to the SL8 Sentinel intelligence layer for normalization, device fingerprint matching against a library of 4,000+ device profiles across 211 vendor ecosystems, and structured dataset assembly.
Producing a verified SL8 Snapshot or higher-tier audit report requires two mandatory gates — both seller-controlled, both required, neither bypassable.
Gate 1 — Agent Authorization. The licensed real estate professional engaging CleanSL8 confirms their authority to contract pre-listing professional services on behalf of the seller — consistent with their executed listing agreement. This is the same authorization chain under which agents engage home inspectors, photographers, and title services. No scan session initiates without an authorized agent credential on file. No credential, no snapshot, no record.
Gate 2 — Seller Attestation. The seller reviews the assembled device dataset and attests to the point-in-time state of every detected SDF. Per device, the seller must: confirm that factory reset and cloud account deactivation have been performed; or flag the device for removal if the seller intends to retain it; or manually add a device the scan did not detect — for example, a powered-off or boxed device that was not broadcasting at scan time. Both gates are required. The seller's per-device attestation is what gives the record its legal standing.
Once both gates are satisfied, the KODA Metadata Certificate (KMC) is generated: a cryptographic attestation binding the seller-confirmed device dataset to the property's MYHID identifier. The confirmation timestamp, confirmation method, and per-device attestation actions are embedded within the attestation and covered by the digital signature.
The KMC is not a deed. It is a point-in-time truth record — the report you pull at closing. It says: on this date, these devices were present, in this state, confirmed by this participant, bound to this property identity. That record cannot be altered without invalidating the signature. It survives ownership transfer. It becomes the first link in a verifiable infrastructure chain across the property's lifetime.
| Device | Location | Status |
|---|---|---|
| Brilliant Smart Device | Ambient | ✓ Confirmed |
| Google Nest Hub | Ambient | ⚑ Flagged — personal device, removed |
| MyQ Garage Door Opener | Ambient | ✓ Confirmed |
| Google Home Speakers | Whole-Home Audio | ⚑ Flagged — personal device, removed |
| Yale X Nest Smart Lock | Ambient | ✓ Confirmed |
| Yeeuu Smart Lock | Front / Back / Side Doors | ✓ Confirmed |
| Budget Blinds | Ambient | ✓ Confirmed |
| Phyn Smart Water Assistant | Smart Sensor | ✓ Confirmed |
| Ecobee Smart Thermostat | Ambient | ✓ Confirmed |
Live SL8 Audit Record · Pittsburgh, PA · Seller identity withheld · Racheallee Lacek, Piatt Sotheby's International Real Estate
KMC_01 is the genesis certificate. When the property sells again and the new owners engage CleanSL8 for a subsequent SL8 Audit — completing both the consent and attestation gates — KMC_02 is generated and appended to KMC_01. KMC_02 includes a cryptographic hash of the prior attestation, forming an immutable chain. The chain only grows by choice: a subsequent owner who does not engage CleanSL8 does not invalidate KMC_01 — they simply do not extend it. A buyer, a lender, an insurer, or any authorized party can verify the complete infrastructure history of a property at any point in that chain: what was there, when it was documented, who confirmed it, and what changed between transfers.
The Ghost Device Problem has a solution. It is not a disclosure form. It is not a "reasonable effort" clause that survives settlement and assigns remediation to the person who had no baseline. It is the CARFAX® for the home's digital infrastructure — generated before closing, cryptographically signed, and verifiable by anyone with a legitimate interest in the property's state.
Property identity is only as powerful as the number of systems that can reference it. Which creates a problem that has nothing to do with technology and everything to do with coordination.
The US residential real estate ecosystem involves hundreds of institutional participants: title companies, lenders, insurers, MLS systems, government assessors, property data platforms, PropTech providers. Each of them maintains property records. Each of them uses different identifiers, different address formats, different schemas. A property record at a title company does not automatically correspond to a record at the lender, which does not automatically correspond to a record at the MLS, which does not automatically correspond to the assessor's database.
Each institution that wants to share property identity data with another must build a bilateral integration: agree on a schema, build an API connection, maintain a trust relationship. For N institutions, that is N(N-1)/2 bilateral integrations. Fifty institutions = 1,225 unique integration relationships. The complexity does not scale. It collapses.
MyHOME ID/e is the enterprise API layer that makes this collapse possible. Every institutional participant integrates once — adding MYHID as a nullable field in their existing database. MyHOME ID/e holds the canonical property identity. Every participant that has integrated can now reference any other participant's property records through a shared, neutral identifier that none of them owns or controls.
This is not a new database. It is not a data aggregator. It is a coordination layer — a neutral hub that collapses the bilateral integration problem into a single integration per participant. The identifier becomes the standard.
MyHOME ID/e does not charge SaaS subscription fees in dollars. It charges in KODA compute units per identifier resolution. The analogy is AI infrastructure: Claude charges per token consumed. Gemini charges per API call. MyHOME ID/e charges per property identity resolution, denominated in KODA.
Three mechanics govern how KODA flows through the enterprise layer:
The 1.45T Enterprise Activation pool is the supply source for this consumption economy. It depletes as the network grows. It does not replenish. The larger the institutional footprint, the faster it depletes, and the more structurally scarce the remaining pool becomes. An acquirer inherits both sides of that trade.
There are three things KODA is not, and understanding them is more important than understanding what it is.
KODA is not a financial claim on real property. Holding KODA does not entitle you to any share of a property's value, rental income, or appreciation. There is no yield mechanism. There is no property backing the token. The housing market does not determine KODA's value — KODA's scarcity mechanics determine its value.
KODA is not a speculative instrument built on hype. The infrastructure it coordinates already exists, is already deployed, and is already operating. Four Ethereum anchors covering 138M+ US residential properties are not a roadmap item. They are verifiable facts on the blockchain today.
KODA is not governed by arbitrary supply mechanics. No halving schedule set by a whitepaper author. No governance vote to decide when to burn. The supply deployment of KODA's largest allocation — the 3T infrastructure reserve — runs on a fixed formula sealed on-chain at genesis: a ~1% monthly deployment into the live identity base. CleanSL8 cannot alter, accelerate, or halt it.
KODA is the coordination currency for a national property identity infrastructure. It governs how systems access verified infrastructure records, how KMC attestations are issued, how enterprise participants consume identifier resolution capacity, and how the protocol maintains neutrality as it expands across institutional relationships it was never designed to control.
KODA is the mechanism that makes MyHOME ID/e possible at national scale without any single institution owning the identity layer. It is the reason a title company in Pittsburgh and a lender in Dallas can reference the same property identity without trusting each other — because they both trust a neutral cryptographic anchor that neither of them controls.
Crypto has a halving problem. Every major supply compression mechanism in digital assets is arbitrary: a schedule set in advance by developers, a governance vote executed by token holders, a burn triggered by protocol fees. None of them are tied to anything real.
The 3T infrastructure reserve is not held in a contract. It is not released over time. It is burned — in a single on-chain transaction at presale open — and the burn amount is derived from a computation that has no precedent in crypto.
Every home participates from day one — no activation, no claiming, no wallets required. The model produced the number. The burn consumed it. The depletion horizon is generational by design — anchored to the sealed reserve formula, not to a market cycle. The formula sized the burn. The burn is the event.
Two curves. Opposite directions. Same ignition point. One counts the public float down. The other counts infrastructure participation up. Both run for a generational timeline until they converge — peak scarcity meets full infrastructure realization.
Two curves. Opposite directions. Same ignition point. One governed by the sealed reserve formula — per-identity capacity growing as the 1.62T reserve depletes into the existing base. One governed by secondary-market burn mechanics — the public float shrinking as the allocation compresses. Neither resets. Neither replenishes. The supply is fixed at 5 trillion. No new minting. Ever.
The canonical failure mode of crypto projects: raise capital to build infrastructure that never materializes. KODA inverts this. The infrastructure exists. Capital is being raised to scale it.
The path to national scale runs on two parallel tracks that never interfere with each other.
The Tortoise track operates entirely through normal real estate transaction activity. SL8 Audit deployments through the existing agent and brokerage network — the $160–250 professional product, the SL8 Access Point at listing, the KMC at closing. KODA is never mentioned. The agent never needs to understand the coordination layer. Every transaction generates a KMC as part of the SL8 Audit lifecycle. KMC issuance is independent of the Infrastructure Reserve — the 138M vaults were allocated at genesis and the reserve deploys on its own sealed schedule. The Tortoise builds the infrastructure. Slowly, permanently, at the pace of the housing market.
The Tortoise does not need to win everything. It needs to establish residual digital access as a recognized, documented, insurable risk category — one with no visible leak, no smell, no alarm, no damage report, and no moment of discovery. A water intrusion leaves a stain. A carbon monoxide event triggers a detector. Unauthorized access to a smart lock, a camera feed, or a garage controller leaves nothing. No evidence. No notification. No record that it occurred at all. The homeowner never knows. The agent never knew. The closing attorney never asked. This is not a cybersecurity problem in the enterprise sense — it is a consumer safety and privacy exposure embedded in the most significant financial transaction of most people’s lives, with zero detection infrastructure and zero regulatory framework. The legislative path is not incremental adoption — it is a RESPA-level mandate. The moment a single E&O carrier prices the gap, a single title underwriter requires the record, or a single state legislature frames residual digital access as the invisible, omnipresent consumer safety exposure it is, the standard becomes the floor. The Hare does not wait for the Tortoise to build market share. It waits for the Tortoise to build the case.
The Hare track is the institutional and KODA-facing layer. MYHID/e enterprise integrations. The KODA presale for non-US participants. The institutional SAFE for accredited US investors. The consumption model generating ARR. The acquisition thesis for PE and strategic buyers who will eventually recognize that the identity layer for 138M US residential properties — with a live patent, operating infrastructure, and a consumption economy already running — is not something they can replicate cheaply or quickly.
The two tracks converge at the same place: a national property identity infrastructure that is too embedded, too verifiable, and too legally protected to displace.
This document is for informational purposes only. Nothing in this whitepaper constitutes an offer to sell, a solicitation of an offer to buy, or a recommendation to purchase any security or financial instrument in any jurisdiction. CleanSL8 does not intend KODA to represent equity, debt, profit share, property ownership, or any claim on company or real estate assets. This whitepaper does not constitute investment advice. The public KODA presale gateway operates under Regulation S and is open to non-US persons only; US IP addresses are blocked at the gateway level. Any accredited US investor participation is conducted separately, off-platform, and subject to Regulation D Rule 506(c) documentation and independent verification. Prospective participants must complete all applicable compliance procedures before participating. These access controls are technical controls only and do not determine whether participation is lawful for any particular person. Access sessions expire after approximately 30 days; participants may be required to re-attest or refresh compliance information at that time.
MyHOME ID(TM), KODA(TM), VIA(TM), KMC(TM), SL8 Audit(TM), SL8 Wipe(TM), and SL8 Signature(TM) are proprietary marks, schemas, or service marks of MYHOME IDENTITY REGISTRY FOUNDATION DAO LLC or affiliated entities. Registered address: 852 Long Island Rd, Majuro, MH, 96960. MIDAO Registration Number: 10264-26. KODA does not represent equity, real estate ownership, revenue share, yield, staking rights, monitoring privileges, credential custody, or any ownership interest in residential property.
This whitepaper may contain forward-looking statements. Actual results may differ materially from those anticipated. Cryptographic assets are subject to significant risk. Regulatory treatment of digital assets varies by jurisdiction and is subject to change.