How Real Estate Tokenization Actually Works: SPVs, Token Standards, and the Compliance Stack That Holds It Together

The token is not the asset. The token is a claim on an equity interest in a legal entity that owns the asset. This distinction is load-bearing: if the special purpose vehicle (SPV) holding title to the property is structured wrong, the token is a transferable receipt for nothing enforceable. Most tokenized real estate discourse fixates on the on-chain layer — which EVM chain, which DEX for secondary liquidity — while the binding constraint is almost always the off-chain legal wrapper and the servicing layer that connects cash flows to token holders.

Tokenized real estate doesn't disintermediate law. It encodes a specific legal arrangement into a programmable format and then inherits every limitation of both systems.

The standard architecture: an originator (property owner or fund manager) transfers title to a single-asset SPV — typically a Delaware LLC, a Cayman exempted company, or a Luxembourg SCSp depending on jurisdictional and tax considerations. Token holders receive membership interests (LLC) or limited partnership shares (LP) in that SPV.

• The SPV isolates the property from the originator's bankruptcy estate — this is the entire point. Without proper bankruptcy remoteness, creditors of the originator can claw back the asset.
• Title insurance and the deed remain in the SPV's legal name, not "on-chain." No US county recorder's office accepts an NFT as proof of ownership.
• The operating agreement (or equivalent) must explicitly authorize tokenized membership interests and define how on-chain transfers map to the cap table. If it doesn't, a transfer on Ethereum has no legal effect on the LLC's membership register.
• Tax treatment flows through: US LLCs are typically pass-through entities, meaning K-1s must reach token holders — which requires KYC at every level. This is why open, permissionless secondary trading is structurally incompatible with most US real estate token structures today.

The SPV is also where the property manager, debt servicer, and distribution agent sit. Cash flows from rent collection pass through the SPV's bank account, get converted (sometimes via stablecoin rails, often still via ACH), and reach holders. The fidelity of that cash-flow pipeline is the real product — the token is just the delivery mechanism.

Vanilla ERC-20 tokens can't enforce transfer restrictions. Tokenized securities therefore use standards that embed compliance logic at the contract level.

• ERC-1400 (and its family: ERC-1410 for partitions, ERC-1594 for issuance/redemption hooks) — designed explicitly for security tokens. Supports forced transfers (needed for legal compliance, e.g., court orders), document management hashes, and partitioned balances for different share classes. Adoption is real but not dominant; Polymath/Polymesh pushed this standard.
• ERC-3643 (formerly T-REX, developed by Tokeny) — uses an on-chain identity registry (ONCHAINID) where each address is linked to verified claims from trusted claim issuers. Transfers revert unless both sender and receiver have valid identity claims satisfying the compliance module. This is the standard behind most European-regulated tokenized securities.
• Custom whitelists — many issuers (RealT, Lofty, Centrifuge-adjacent structures) simply maintain a mapping of approved addresses and block transfers to non-whitelisted wallets. Simpler, but fragile: a single admin key controls the whitelist, and the compliance logic is centralized.

The trade-off is clear: ERC-3643's on-chain identity registry is more composable and auditable but adds gas overhead and requires claim issuers to stay operational. Custom whitelists are cheaper but create a single point of failure and regulatory opacity.

Transfer Agents and Cap Table Reconciliation

Regulated securities need a transfer agent — the entity legally responsible for maintaining the definitive record of ownership. In traditional finance, this is Computershare or similar. In tokenized real estate, the on-chain ledger aspires to be the canonical cap table, but regulators (notably the SEC) have not formally blessed any smart contract as a compliant transfer agent.

Platforms like Securitize hold a registered transfer agent license and maintain a parallel off-chain record that they reconcile with on-chain state. If the chain forks, if a private key is lost, or if a court orders a reversal, the off-chain record is the legal source of truth. The on-chain state is authoritative only to the extent the legal docs say it is.

1. Entity formation and title transfer — originator creates SPV, transfers deed via standard conveyance. Title insurance is obtained in the SPV's name.

2. Legal documentation — operating agreement, private placement memorandum (PPM) or prospectus (for Reg D, Reg S, Reg A+, or EU Prospectus Regulation), subscription agreement. The exemption chosen determines who can buy and where.

3. Compliance module deployment — identity registry, claim issuers, and transfer restriction logic deployed on-chain. Addresses are whitelisted post-KYC/AML.

4. Token minting — tokens minted to the issuance contract, allocated to subscribers upon fund receipt. Token supply maps 1:1 to total equity units defined in the operating agreement.

5. Distribution mechanism setup — smart contract or off-chain service for pushing rental yield to holders, typically in USDC or DAI. Frequency (monthly, quarterly) and the fee waterfall (property management, servicing, platform fees before distributions) are encoded or documented.

6. Secondary market enablement — if applicable, tokens are listed on a compliant ATS (e.g., tZERO, INX) or allowed for peer-to-peer transfer within the whitelist. Reg D tokens are subject to a 12-month lockup for US buyers.

The sequence matters: deploying the token before the legal docs are finalized creates a mismatch between what the token represents on-chain and what the holder actually owns. This has happened — and it's ugly to unwind.

• SPV governance capture — if the SPV manager has unilateral authority to amend the operating agreement, they can dilute token holders, redirect cash flows, or encumber the property with new debt. Mitigation: on-chain governance votes gating material decisions, but enforcement still depends on the manager honoring the vote.
• Oracle-free valuation — unlike DeFi collateral with liquid price feeds, real estate NAV depends on appraisals. Stale or manipulated appraisals can misrepresent LTV ratios for tokens used as DeFi collateral (e.g., on Centrifuge or MakerDAO vaults). There is no trustless price oracle for a specific building.
• Redemption illiquidity — most tokenized real estate offers no guaranteed redemption at NAV. If secondary markets are thin (they usually are — daily volume on most real estate tokens is negligible), holders are locked in. Some platforms offer quarterly redemption windows funded from reserves, but these can gate or suspend during stress.
• Key management and forced transfers — admin keys that can pause transfers, freeze accounts, or force-transfer tokens are necessary for legal compliance but are also the exact attack surface for rug pulls. Multisig with time-locks mitigates but doesn't eliminate this.
• Jurisdictional mismatch — a token issued under Reg D sold to a non-accredited investor via a DEX creates liability for the issuer, even if the buyer circumvented the whitelist by acquiring the wallet address off-market. The issuer's compliance module failing is the issuer's problem, not the buyer's.
• Tax reporting breakdown — if the platform or SPV servicer fails to issue K-1s or equivalent tax documents, token holders face compliance risk. This is operationally harder at scale with pseudonymous wallets, even with KYC at onboarding, because wallets can change hands informally.

The honest state: most "tokenized real estate" volume is concentrated in a few platforms, and the total market remains small relative to both traditional REIT markets and DeFi TVL.

• RealT — tokenized single-family rentals on Gnosis Chain (xDai). ERC-20 tokens representing fractional LLC interests. Rent paid in USDC to holder wallets. Limited to accredited US investors and non-US investors.
• Centrifuge / MakerDAO (now Sky) — real estate debt (not equity) tokenized as Tinlake pool assets, used as collateral for DAI minting. The RWA vaults (e.g., BlockTower Andromeda, New Silver) demonstrated the model but also exposed servicing risk when underlying loan performance deteriorated.
• Propy — focuses on the transaction layer (deed transfer automation) rather than fractional ownership. Limited jurisdictional support.
• Ondo, Backed, Maple — primarily tokenize Treasuries or credit, not direct real estate equity, though some real estate debt is in the mix.

The secondary liquidity promise remains largely undelivered. Most real estate tokens trade on proprietary platforms or Uniswap pools with minimal depth.

• ERC-3643 specification: github.com/TokenySolutions/ERC-3643 — read the transfer validation flow in detail
• ERC-1400 family: github.com/ethereum/eips — EIP-1400, EIP-1410, EIP-1594
• RealT token contracts: viewable on Gnosisscan (blockscout.com/xdai/mainnet) — search any RealT property token to inspect the whitelist logic
• MakerDAO RWA vault documentation: mips.makerdao.com — MIP21 (Real World Finance) and MIP65 (Monetalis Clydesdale) detail how real estate and Treasury collateral integrates with the Maker protocol
• Securitize transfer agent registration: SEC EDGAR filing, CRD# for Securitize Markets LLC
• rwa.xyz — dashboard tracking tokenized RWA TVL by category, including real estate debt and equity; useful for validating actual on-chain volume claims