512-567-5308

Frequently Asked Questions

Tokenization Basics

Real estate tokenization is one of the most rapidly evolving areas at the intersection of property law, securities law, and blockchain technology. Understanding the fundamentals is essential before diving in.

What is real estate tokenization?

Real estate tokenization is the process of representing ownership interests in real estate — or in an entity that owns real estate — as digital tokens on a blockchain. Each token corresponds to a fractional ownership interest, much like shares in a company. Tokenization can apply to a single property, a portfolio, or a real estate fund, and can represent equity, debt, or hybrid interests.

 

⚠ The legal structure underlying the token determines everything — your securities law obligations, your investor rights, and your liability exposure. Before you tokenize anything, talk to an attorney who understands both the technology and the law.

In the vast majority of cases, yes. Under the Howey test — the Supreme Court’s foundational framework for defining a security — a real estate token is almost certainly a security if investors are putting money into a common enterprise with an expectation of profit from the efforts of others. This means that offering and selling real estate tokens triggers the full framework of federal and state securities laws, including registration requirements and disclosure obligations.

 

⚠ Calling your token a ‘utility token’ does not make it one. The SEC looks at economic substance, not labels. We help token issuers properly analyze their token’s legal status and structure compliant offerings.

Ethereum remains the most widely used blockchain for real estate tokenization, largely due to the maturity of its smart contract infrastructure and broad ecosystem support for the ERC-3643 (T-REX) standard. Polygon, Avalanche, and Hedera — which has integrated ERC-3643 into its Asset Tokenization Studio — are also used for real-world asset tokenization. The choice of blockchain affects interoperability, transaction costs, and smart contract capabilities — but the legal analysis does not change based on the chain.

 

⚠ Technology choices have legal implications. We work with clients and their technical teams to ensure the chosen platform and token standards are compatible with their regulatory requirements.

Equity tokenization gives token holders a fractional ownership interest in the underlying property or the entity that owns it — entitling them to a share of cash flow, appreciation, and (potentially) voting rights. Debt tokenization represents a loan secured by real estate, with token holders receiving interest payments and priority repayment. Both are securities, but the regulatory treatment, investor rights, and deal economics differ significantly.

 

⚠ Whether you tokenize equity or debt shapes your entire offering structure, your investor disclosures, and your ongoing obligations. We help clients choose the right structure for their goals.

ERC-3643 — originally developed by Tokeny Solutions under the name T-REX (Token for Regulated EXchanges) and formally accepted as an official Ethereum standard — is the most sophisticated and widely adopted token standard for regulated real-world assets. Unlike basic ERC-20 tokens (which allow free peer-to-peer transfers with no compliance controls), ERC-3643 embeds identity verification, investor eligibility rules, and transfer restrictions directly into the token’s smart contract logic. Every transfer is conditioned on both the sender and the receiver satisfying predefined compliance criteria — verified through ONCHAINID, ERC-3643’s decentralized on-chain identity system. The standard also supports token pausing and freezing, forced transfers (for legal compliance or wallet recovery), and modular compliance rules that can be configured for different jurisdictions. Critically, ERC-3643 is backwards compatible with ERC-20, meaning it can interact with standard wallets, custodians, and exchanges that are equipped to handle permissioned tokens. As of 2025, ERC-3643 has become the institutional-grade standard of choice for tokenized securities offerings globally.

 

⚠ ERC-3643 is not just a technical choice — it is a compliance architecture. Choosing it (and configuring it correctly) directly affects your ability to satisfy securities law transfer restrictions, KYC/AML obligations, and investor eligibility requirements. We help issuers understand what the standard commits them to legally, not just technically.

ERC-20 is the baseline Ethereum fungible token standard — it enables token creation and transfer but has no compliance features whatsoever. Any wallet can receive any ERC-20 token, making it fundamentally unsuitable for regulated securities. ERC-1400 was an earlier attempt at a security token standard that introduced transfer restrictions and document attachment, but it was never formally accepted as an official ERC standard and has seen limited institutional adoption. ERC-3643 goes significantly further: it is the only officially accepted ERC standard designed for regulated securities, it integrates a full on-chain identity and credentialing system (ONCHAINID), it enforces compliance at the smart contract level through a modular compliance engine, and it supports the full lifecycle of a security token from issuance through transfer, forced recovery, and retirement.

 

⚠ The standard you build on shapes your compliance posture for the life of the token. We help issuers select and implement the right token architecture before a line of code is written.

ERC-3643: Compliance Architecture & Legal Implications

ERC-3643 is more than a technical standard — it is a compliance framework with direct legal implications for how a tokenized real estate offering must be structured, documented, and operated.

What is ONCHAINID, and what legal role does it play in an ERC-3643 offering?

ONCHAINID is ERC-3643’s decentralized on-chain identity system. Each investor is assigned an on-chain identity contract that records verified claims — such as KYC/AML approval, accredited investor status, and jurisdictional eligibility. Before any token transfer can occur, the ERC-3643 compliance engine checks the ONCHAINID claims of both the sender and the receiver. From a legal perspective, ONCHAINID is the mechanism by which the issuer satisfies its obligation to verify investor eligibility under the applicable securities exemption — programmatically and at scale. The on-chain record of claims also creates an auditable compliance trail.

 

⚠ ONCHAINID bridges the gap between KYC/AML law and blockchain execution. Proper configuration of claim types and claim issuers is both a technical and legal decision. We help issuers design ONCHAINID architectures that satisfy their regulatory obligations.

ERC-3643’s transfer and transferFrom functions are conditionally implemented — a transfer only executes if the compliance contract approves it. The compliance contract runs a series of modular checks before approving any transfer: Is the receiver’s ONCHAINID verified? Does the receiver hold the required credentials (e.g., accredited investor status, non-U.S. person status for Reg S)? Does the transfer violate holding period restrictions (e.g., the 12-month Rule 144 lockup)? Does the transfer exceed the maximum investor count permitted under the exemption? If any check fails, the transfer is rejected at the blockchain level — not just flagged for manual review. This architecture means transfer restrictions are self-executing and tamper-resistant.

 

⚠ Self-executing transfer restrictions are powerful — but only if they are correctly configured to match your securities law obligations. A misconfigured compliance module can create both technical failures and securities law violations. We review ERC-3643 compliance module configurations against the requirements of the applicable offering exemption.

ERC-3643 includes a forcedTransfer function that allows an authorized agent to move tokens between wallets without the token holder’s consent. Legally, forced transfers may be required in several scenarios: court orders directing transfer of assets in connection with litigation or bankruptcy; regulatory orders directing an issuer to freeze or transfer assets; the death or legal incapacity of an investor requiring transfer to an estate or guardian; and wallet recovery where an investor loses access to their private key (a common problem in digital asset holdings). The forced transfer function makes ERC-3643 more legally manageable than standards that offer no recovery mechanism.

 

⚠ Forced transfer authority is a double-edged sword — it enables legal compliance but must be governed by robust internal policies to prevent abuse. We help issuers draft governance frameworks that define when and how forced transfers may be authorized.

ERC-3643’s compliance engine is modular — instead of a single monolithic set of rules, it allows issuers to stack compliance modules that each enforce a specific rule. For a multi-jurisdiction offering, different modules can enforce different rules simultaneously: a U.S. module enforcing Regulation D accredited investor requirements, a European module enforcing MIFID II eligibility criteria, a Reg S module restricting U.S. persons, and a holding period module enforcing lockup periods. Each investor’s ONCHAINID claims are matched against the applicable module. This modularity allows a single token to be offered compliantly in multiple jurisdictions without creating separate token series.

 

⚠ Multi-jurisdiction offerings require coordination between legal counsel in each relevant jurisdiction and the technical team configuring the compliance modules. We manage the legal layer so that your compliance architecture reflects actual regulatory requirements, not assumptions.

ERC-3643 allows issuers to pause all transfers globally (pausing the entire token) or freeze the tokens held by a specific investor. Legal scenarios that may require these functions include: SEC or regulatory investigation requiring preservation of assets; a court injunction prohibiting transfer of specific interests; discovery that a particular investor’s identity verification was fraudulent, requiring suspension pending re-verification; and material adverse events at the property level that require a temporary halt to secondary trading. Unlike traditional securities where freezing requires intermediary action, ERC-3643 allows the issuer to act directly and immediately.

 

⚠ The ability to pause and freeze tokens is a legal compliance tool — but deploying it incorrectly can itself create liability. We help issuers draft policies for when pausing and freezing are authorized, and by whom.

Securities Law & Regulatory Compliance

Regulatory compliance is the most complex and highest-stakes aspect of any real estate tokenization project. Getting it wrong can result in rescission liability, SEC enforcement, and personal liability for founders.

What securities exemptions can be used for a real estate token offering?

The most commonly used exemptions for real estate token offerings are Regulation D (Rule 506(b) and 506(c)), Regulation A+ (which allows offerings up to $75 million with lighter disclosure requirements), and Regulation S (for offerings made exclusively to non-U.S. persons). Each exemption has different investor eligibility requirements, offering size limits, and ongoing compliance obligations. ERC-3643’s modular compliance architecture can be configured to enforce the eligibility and transfer restriction requirements of each exemption automatically.

 

⚠ The right exemption depends on your capital target, your investor base, and your timeline. We help token issuers select and execute the right exemption from day one — and configure the ERC-3643 compliance modules to match.

Regulation A+ (sometimes called a ‘mini-IPO’) allows companies to raise up to $75 million from both accredited and non-accredited investors using a simplified offering circular reviewed by the SEC. It permits general solicitation and public marketing. For real estate tokenization projects targeting retail investors or seeking broader distribution, Reg A+ can be attractive — and ERC-3643’s investor eligibility controls can be configured to allow non-accredited investors while still enforcing other transfer restrictions. However, Reg A+ involves meaningful upfront cost and SEC review time of typically 3-6 months.

 

⚠ Reg A+ is powerful but resource-intensive. We help clients evaluate whether the benefits justify the costs for their specific tokenization project.

KYC and AML obligations in token offerings arise from both federal securities law and FinCEN regulations. ERC-3643 addresses these obligations through ONCHAINID — investors cannot receive or transfer tokens unless they hold a valid, issuer-approved KYC/AML claim on their on-chain identity. This means that KYC/AML compliance is not just a onboarding process but is continuously enforced at the smart contract level: if an investor’s credentials expire or are revoked, their ability to transfer tokens is automatically suspended. The issuer retains ultimate legal responsibility for the integrity of the KYC/AML program and the accuracy of the claims issued.

 

⚠ ERC-3643 makes KYC/AML compliance self-executing — but the legal responsibility for the program design and claim issuance remains with the issuer. We help issuers build KYC/AML programs that satisfy their regulatory obligations and integrate properly with their ERC-3643 architecture.

In many cases, yes. The Securities Exchange Act of 1934 generally requires that persons effecting securities transactions register as broker-dealers unless an exemption applies. The most commonly used exemption is the issuer exemption, which allows issuers to sell their own securities without a broker-dealer license if they meet certain conditions. Platforms facilitating secondary trading of ERC-3643 security tokens almost always need Alternative Trading System (ATS) registration, because the secondary market transfer function — even though executed by the smart contract — constitutes effecting a securities transaction.

 

⚠ Broker-dealer and ATS registration requirements are frequently overlooked in token offerings. We help issuers and platform operators understand their registration obligations before they launch.

An Alternative Trading System is a SEC-registered trading venue that can facilitate secondary trading of securities including security tokens. In an ERC-3643 framework, the ATS and the token’s compliance module must work in tandem: the ATS matches buyers and sellers and confirms their eligibility, while the ERC-3643 compliance engine independently verifies that the proposed transfer satisfies all on-chain rules before executing. This dual-layer approach — legal compliance at the ATS level and technical compliance at the smart contract level — is the architecture that sophisticated real estate tokenization platforms are building toward.

 

⚠ Liquidity is the primary value proposition of tokenization — but delivering it legally requires both ATS infrastructure and a correctly configured ERC-3643 compliance layer. We help issuers structure offerings and platform relationships to enable compliant secondary trading.

In addition to federal securities law, every state has its own blue sky laws that may require notice filings or consent to service of process. Regulation D Rule 506 offerings are preempted from state registration requirements but still require notice filings in each state where investors reside. ERC-3643’s jurisdictional compliance modules can be configured to restrict token transfers to investors in states where the required filings have been made — providing a built-in technical enforcement mechanism for state-by-state compliance.

 

⚠ Blue sky compliance is often the most operationally complex part of a securities offering. We manage state filing requirements and ensure your ERC-3643 compliance modules reflect your actual state filing posture.

Deal Structure & Smart Contracts

Structuring a tokenization project involves decisions that sit at the intersection of corporate law, real estate law, and technology — each of which must be carefully coordinated.

How is the legal structure of a tokenized real estate offering typically organized?

Most real estate tokenization structures use a Special Purpose Vehicle (SPV) — typically an LLC — to hold the property or the real estate debt. Investors receive membership interests in the SPV, which are then represented as ERC-3643 tokens on the blockchain. The token itself does not hold real estate title — the LLC does. This structure is important because it separates the blockchain layer from the real estate title layer, preserving the legal enforceability of ownership rights while enabling the compliance controls that ERC-3643 provides.

 

⚠ The SPV structure is the legal backbone of your tokenization project. Poorly structured SPVs create title issues, investor disputes, and regulatory problems. We design SPV structures that are robust, compliant, and investor-ready.

Smart contracts — self-executing code on the blockchain — are increasingly recognized as legally enforceable in many jurisdictions for their payment and transfer mechanics. ERC-3643’s conditional transfer functions, compliance checks, and forced transfer capabilities all execute automatically and are difficult to dispute as a factual matter. However, smart contracts cannot replace the full legal documentation of a real estate transaction. The offering documents — PPM, subscription agreement, operating agreement — remain the authoritative legal record of investor rights. Where smart contract logic conflicts with underlying legal documents, serious legal uncertainty arises.

 

⚠ We review ERC-3643 smart contract logic against underlying legal documents to ensure consistency — and help issuers understand what their code actually commits them to legally.

Token holder rights upon a sale, refinance, or other liquidity event are determined by the operating agreement of the SPV — not by the token. The operating agreement must specify the economic waterfall, voting rights on major decisions, and distribution mechanics. Upon a disposition, the ERC-3643 token can be retired (burned) or converted, but the economic entitlement flows from the legal documents. ERC-3643’s token pausing function may be used to halt secondary trading during a pending sale to prevent transfers by investors who have not yet received proper disclosure of the transaction.

 

⚠ The disposition waterfall is where investors get paid — or do not. We draft operating agreements that protect investor rights at the most critical moment of the investment and coordinate the legal mechanics with the token’s lifecycle management.

Under SEC Rule 144, restricted securities (such as those sold in a Regulation D offering) generally cannot be resold for 12 months after issuance. ERC-3643’s compliance module can be configured to enforce this lockup period automatically — preventing any secondary transfer by an investor before their 12-month holding period has expired. This is a significant advantage over traditional paper-based transfer restrictions, which rely on manual review by transfer agents and legal counsel. Once the holding period expires, the compliance module can automatically unlock the investor’s transfer rights based on their ONCHAINID credentials.

 

⚠ Automating Rule 144 compliance through ERC-3643 reduces administrative burden and eliminates the risk of human error in monitoring holding periods. We help issuers configure compliance modules that correctly implement their securities law obligations.

Beyond securities law, real estate tokenization must contend with title insurance requirements, mortgage and lender consent obligations (most loans have transfer restriction covenants that may be triggered by SPV membership interest transfers), local recording requirements, and property tax implications. Due diligence on the underlying real estate must be as rigorous as in any conventional transaction. ERC-3643’s permissioned transfer architecture can actually help with lender consent issues — some lenders are more comfortable with tokenized interests when they can see that the token standard enforces investor eligibility controls and limits transferability.

 

⚠ Tokenization does not eliminate real estate risk — it concentrates it. We conduct real estate due diligence that identifies title, lender, and regulatory issues before they become investor problems.

Investor Relations & Ongoing Compliance

Launching a token offering is just the beginning. Ongoing compliance, investor communication, and secondary market management require sustained attention.

What ongoing reporting obligations does a tokenized real estate issuer have?

Reporting obligations depend on the exemption used. Regulation D issuers have minimal ongoing SEC reporting but must maintain records and honor investor information rights under the operating agreement. Regulation A+ issuers must file annual reports, semiannual reports, and current reports for material events. ERC-3643 issuers also have ongoing obligations to maintain the integrity of the ONCHAINID identity registry — updating or revoking investor credentials when investors no longer qualify (e.g., loss of accredited investor status) and ensuring compliance modules remain correctly configured as regulatory requirements evolve.

 

⚠ Ongoing ERC-3643 compliance obligations go beyond the initial offering. We build compliance calendars that cover both SEC reporting and token-level credential maintenance.

Distributions to ERC-3643 token holders must be made in accordance with the operating agreement. Many tokenization platforms automate distributions through smart contracts, directing cash flow to verified token wallets proportionally. ERC-3643’s identity registry ensures distributions only flow to wallets holding valid credentials — reducing the risk of distributions reaching ineligible transferees. However, the tax characterization of distributions, withholding obligations for foreign investors, and K-1 reporting must all be addressed in the underlying legal and accounting infrastructure, independently of the token mechanics.

 

⚠ Automated distributions are one of tokenization’s most compelling features — but they must be legally and tax-correctly structured. We help issuers build distribution frameworks that work both on-chain and in the tax code.

ERC-3643 is designed with upgradeability in mind — compliance modules can be updated or replaced without redeploying the entire token contract. However, material changes to compliance parameters — such as expanding the eligible investor universe, changing transfer restriction rules, or modifying holding period requirements — may constitute material changes to the securities offering that require disclosure to existing investors and potentially the right for investors to withdraw subscriptions. The legal analysis of whether a compliance module update requires investor notice is fact-specific and should be reviewed by securities counsel before implementation.

 

⚠ Post-launch changes to your ERC-3643 compliance architecture can have securities law consequences that are not obvious from a purely technical perspective. We review proposed compliance module updates against your offering documents and applicable exemption requirements.

Real estate tokenization does not create new tax advantages — the tax treatment of a token investment mirrors the tax treatment of the underlying asset and entity structure. ERC-3643 token holders in an LLC SPV should receive K-1s reflecting their share of the LLC’s income, deductions, and depreciation (including bonus depreciation and cost segregation benefits). However, the fractionalization that tokenization enables may allow more investors to access real estate’s tax benefits than conventional structures permit. The ONCHAINID identity registry can also help issuers track foreign investor status for FIRPTA withholding purposes.

 

⚠ Tax structuring in tokenized real estate requires coordination between securities counsel and tax counsel. We work with clients’ tax advisors to ensure the entity structure optimizes both investor tax benefits and regulatory compliance.