Tokenized real estate does not eliminate cross-entity conflicts. In most cases, it adds a layer to them. A multi-entity structure now has a fund, one or more SPVs, a platform, governing documents, and a digital record that all need to tell the same story. When they do not, the conflicts that result are not technology problems. They are legal and structural problems that the technology makes harder to see.
A tokenized real estate platform operates a flagship fund and a series of separately tokenized SPVs, all managed by the same sponsor affiliate. Each SPV holds a single property. Each issues tokens to its own investor group. The flagship fund holds a diversified portfolio including positions in several of the same SPVs. The sponsor earns an acquisition fee at the SPV level, a management fee at the fund level, and a platform fee from the technology infrastructure that serves both.
Over three years, three things happen that are individually defensible and collectively damaging. First, the sponsor routes the best-performing assets into the flagship fund’s portfolio, which has the most favorable carry economics, rather than into the standalone SPVs, which charge lower management fees. Second, when one SPV encounters a capital shortfall after an unexpected capital expenditure requirement, the flagship fund provides a bridge loan at an interest rate the sponsor determines without independent validation. The interest payments flow from the SPV’s investors to the fund’s investors, who include the sponsor. Third, the platform’s investor dashboard aggregates all positions into a single portfolio view that makes each investor feel like part of a unified ecosystem, while the governing documents give each investor separate, and in some respects materially different, rights depending on which entity they invested in.
None of those decisions results in immediate legal action. Each one is disclosed somewhere in a document that most investors did not read carefully when they subscribed. Each one is individually authorized somewhere in the governing documents. Together they describe a structure where the sponsor’s economic incentives systematically advantage some investors and some entities over others, in ways that were present from the first day of the platform’s operation and that the unified digital presentation actively obscured.
The 2026 Project Crypto Release and the January 28, 2026 SEC Staff Statement on Tokenized Securities both confirmed that tokenized real estate interests are digital securities subject to the full federal securities law framework. The SEC has consistently identified multi-entity fund structures as one of the highest-conflict environments in private fund management, and the addition of tokenization does not reduce that complexity. It adds another layer of apparent unity to a structure whose underlying conflicts are legal and economic rather than technological.
Why Multi-Entity Structures Create Structural Conflicts
Cross-entity conflict in a tokenized real estate structure begins with a simple fact: the same sponsor controls entities with different investors, different economics, and different obligations, and those entities interact with each other in ways that the sponsor determines. The prior posts in this series on entity structures and on role separation established the foundational principle: legal entity separation and operational separation are two different things, and a sponsor who controls multiple entities formally separated on paper but operationally integrated under common management is not insulated from the conflicts that arise when those entities have adverse interests.
The structure that the opening scenario describes, a flagship fund plus standalone SPVs plus a platform under common control, is not unusual in the tokenized real estate market. It is a common architecture for building a scalable capital formation program. What makes it a conflict-intensive architecture is the combination of three features: the sponsor controls allocation decisions that determine which entity gets which opportunity; the sponsor earns different fees from each entity and from the platform infrastructure that serves all of them; and the digital presentation makes the structure look unified to investors whose legal rights are actually separated, different, and in some cases adverse to each other.
The January 28 Staff Statement identified exactly this dimension when it noted that the legal rights tied to a token depend on how the structure is set up and how the official ownership records are maintained. Two investors looking at the same platform dashboard may believe they are holding equivalent positions in a common enterprise when one holds a senior fund interest with diversified exposure and priority claim on management attention, and the other holds a junior SPV equity interest in a single asset with no claim on the fund’s other resources. Those are different investments. The platform’s presentation does not make them the same.
| The digital interface creates the impression of a unified investment ecosystem. The legal documents create a fragmented collection of separate entities with separate stakeholders, separate obligations, and separate interests. When the sponsor controls all of them, cross-entity conflict is not a risk. It is a structural feature that must be managed from the first day of the platform’s operation. |
The Six Sources of Cross-Entity Conflict: A Practical Map
The following table maps the six most significant sources of cross-entity conflict in tokenized real estate multi-entity structures against what each conflict actually is and its practical implication and mitigation:
| Conflict Source | What the Conflict Actually Is | Practical Implication and Mitigation |
| Fee design across entities | Acquisition fees, financing fees, asset-management fees, property-management fees, platform fees, and disposition fees paid to sponsor affiliates at different entity layers. Each fee reduces cash available to investors at that layer, and investors in different entities may not know what fees are being paid at layers above or below them. | A fund investor who expects to share in acquisition economics may not know that the SPV manager receives a separate acquisition fee before distributions flow upward. An SPV investor who expects clean asset-level economics may not see the platform fee charged at the fund level. Disclosure of every fee at every entity level, in plain dollar terms rather than percentage approximations, is the minimum required for informed investor consent. |
| Allocation of investment opportunities | The sponsor controls the deal pipeline and decides which opportunity goes to the flagship fund, a separately tokenized SPV, a sidecar vehicle, a co-investment vehicle, or a new fund. Investors in vehicles that receive worse allocations bear real economic harm relative to investors in vehicles that receive better allocations. | IOSCO has identified allocation as one of the most persistent conflict sources in multi-fund management. A sponsor who routes an opportunity to the vehicle with the highest management fee, the most favorable carried interest, or the lowest reporting burden has made an allocation decision that is not neutral across its investor constituencies. A written allocation policy, disclosed to all investors before they subscribe, is the primary mitigation tool. |
| Cross-entity lending and rescue financing | A fund lends to an SPV, one SPV supports another through an intercompany facility, or an affiliated vehicle provides rescue capital to a distressed property entity. The lending entity and the borrowing entity have different stakeholders, different economics, and potentially adverse interests in a workout scenario. | The SEC has highlighted conflicts where clients are invested in different layers of the same capital stack and may become adverse in a bankruptcy or workout. The pricing of cross-entity loans, the collateral terms, the cure rights, and the enforcement priority all require independent validation rather than sponsor-determined terms. An affiliated rescue financing that solves a sponsor liquidity problem at the expense of the borrowing entity’s investors is a textbook conflict of interest. |
| Waterfall and distribution misalignment | A property-level SPV has one distribution waterfall. A feeder or fund entity has another. The token holder’s economic expectations may reflect neither document accurately. Cash generated at the property level may be retained at an intermediate layer for reserves, debt service, or operating expenses before reaching the investor. | The most common investor expectation failure in tokenized real estate is the assumption that property-level cash flow translates immediately into token holder distributions. The actual path from property revenue to investor distribution passes through debt service, operating expense reserves, entity-level approvals, and waterfall calculations that can be days, weeks, or quarters long. Each step is governed by a different document at a different entity level, and none of them appears in the token balance. |
| Information asymmetry across entity layers | Fund investors receive aggregated portfolio reporting. SPV investors receive asset-specific reporting. Token holders may see only a dashboard abstraction. Each investor group is making decisions from a different informational base about the same underlying deal. | When one group of investors knows about reserves, intercompany liabilities, covenant breaches, or sponsor-affiliate transactions while another group sees only a simplified yield figure, governance stops being coordinated. An investor who votes on a reserved matter without knowing that the SPV has an undisclosed intercompany loan that affects the waterfall is not making an informed governance decision. Information consistency across entity layers is a legal obligation, not a platform design choice. |
| Sponsor control of multiple entity layers simultaneously | The same sponsor or affiliate serves as fund manager, SPV manager, asset manager, platform operator, and token administrator, earning different compensation from each role. Every major decision about the investment passes through an entity controlled by the same party that benefits from multiple outcomes. | Delaware’s LLC Act permits broad contractual modification of fiduciary duties, but it does not eliminate the implied contractual covenant of good faith and fair dealing. A sponsor who controls allocation, pricing, financing, governance, and reporting across multiple related entities, and who earns fees from each of those roles, must disclose those conflicts specifically and provide mechanisms through which investors can hold the sponsor accountable. Vague conflict disclosures that acknowledge the theoretical possibility of conflicts without identifying specific transactions and their terms do not satisfy the SEC’s disclosure standard. |
Reading this table, the pattern that recurs across every conflict category is the same: the sponsor controls a decision that affects the relative economic and legal positions of investors in different entities, and the investors in each entity do not have the same information about that decision or the same ability to influence it. The six conflicts are not independent. Fee design affects allocation incentives. Allocation decisions affect which investors benefit from cross-entity financing terms. Information asymmetry prevents investors from recognizing that their entity is being disadvantaged. Sponsor control of multiple layers makes each individual decision look innocuous while the cumulative pattern is systematically self-serving.
The Duty Framework: What Delaware Law and the SEC Require
The legal framework governing cross-entity conflicts in tokenized real estate structures is primarily contractual at the entity level and regulatory at the securities level. Delaware’s LLC Act is explicit: the LLC agreement may expand, restrict, or eliminate fiduciary duties and liabilities, but it cannot eliminate the implied contractual covenant of good faith and fair dealing. That covenant is the floor beneath every Delaware LLC agreement, and it means that a sponsor who contractually eliminates standard fiduciary duties of loyalty and care cannot also act in ways that are fundamentally inconsistent with what investors reasonably expected when they subscribed based on the disclosures they received.
The SEC’s standards-of-conduct framework applies where the sponsor or an affiliated entity is registered as an investment adviser. The SEC has stated that investment advisers must eliminate a conflict of interest or make full and fair disclosure of it so that the client can give informed consent, and that where disclosure alone is insufficient to protect investors, the conflict must be eliminated or adequately mitigated. Critically, the SEC has specified that disclosure cannot be vague or hypothetical when the conflict actually exists. A disclosure that says the sponsor “may” have conflicts of interest when the sponsor is currently earning multiple fees from multiple related entities is not the disclosure the SEC’s standard requires.
The SEC’s private fund rulemaking, which addressed compensation schemes, allocation practices, affiliated transactions, and investor-disclosure obligations in private funds, reinforced the same principle: investors cannot give meaningful consent to conflicts they do not understand. The specific transactions, the specific fee amounts, the specific allocation decisions, and the specific terms of affiliated lending arrangements must be described with enough precision that investors can evaluate whether the conflict is acceptable to them before they commit capital. A summary disclosure at the back of a lengthy offering memorandum does not achieve that standard when the conflicts are pervasive and ongoing throughout the life of the investment.
How Tokenization Changes the Conflict Analysis
Tokenization does not create new categories of conflict, but it does change two aspects of the conflict environment in ways that make existing conflicts harder to detect and disclose. The first is the information presentation effect: a polished investor dashboard that aggregates multiple entity positions into a single portfolio view makes the structure look coherent and unified in a way that a traditional multi-entity fund structure with separate quarterly reports does not. An investor who receives separate reporting from each entity at least knows that the entities are separate. An investor who sees a unified platform interface may not recognize that their rights in different vehicles are materially different until they try to enforce one of them.
The second is the governance divergence effect: as described in the prior posts on on-chain governance conflicts, a platform that displays a unified voting interface may give investors the impression that they share governance rights across the platform when their actual governance rights are defined by the operating agreement of the specific entity they invested in. A token holder in SPV-3 who votes on a platform governance proposal that is actually a reserved matter under the flagship fund’s operating agreement has not exercised a binding governance right. They have interacted with a feature whose legal effect is determined by documents they may never have read carefully.
Capital Allocation: The Conflict That Is Always Present
The allocation of investment opportunities across related entities is the most persistent and the most difficult to manage cross-entity conflict in a tokenized real estate platform. The sponsor controls the deal pipeline and determines which opportunity is offered to which vehicle. Every allocation decision is a choice that advantages some investors and disadvantages others, because the best assets cannot simultaneously be in every vehicle.
IOSCO has documented this conflict extensively in its guidance on multi-fund management, noting that when firms operate multiple vehicles with overlapping strategies, conflict arises in allocating opportunities between earlier and later funds, between flagship and sidecar vehicles, and between fund vehicles and co-investment opportunities. Common mitigation approaches include written allocation policies that specify the order in which vehicles have priority for specific opportunity types, pro rata frameworks that distribute opportunities proportionately across eligible vehicles, and advance disclosure to investors of the allocation methodology before they subscribe.
For a tokenized real estate platform with a flagship fund and separately tokenized SPVs, the allocation question arises every time a new acquisition opportunity is identified. Does the opportunity go to the fund, which provides the sponsor with diversification benefits and portfolio-level management fees? Does it go to a standalone SPV, which generates an acquisition fee and an asset-specific token offering? Does it go to a co-investment vehicle for certain preferred investors? The sponsor’s economic incentives may differ for each vehicle, and the investors in each vehicle have a legitimate interest in knowing that the opportunity was allocated to their vehicle on terms that were not systematically disadvantaged by the sponsor’s fee and carry economics.
A written allocation policy, disclosed to all investors in all vehicles before they subscribe, is the primary mitigation tool for this conflict. The policy should specify which types of opportunities each vehicle has priority access to, how opportunities are allocated when multiple vehicles could accommodate the same deal, what happens when an opportunity arises that fits only one vehicle, and how the sponsor’s fee and carry economics in each vehicle are disclosed and compared. That policy does not eliminate the conflict. It makes the conflict visible and gives investors the information they need to evaluate whether it is acceptable before they commit capital.
Cross-Entity Lending: When the Capital Stack Becomes the Conflict
Cross-entity lending is the conflict category that most directly pits investors in one entity against investors in another. When a fund lends to an SPV, when one SPV provides bridge financing to another, or when an affiliated vehicle injects rescue capital into a distressed entity, the lending entity’s investors and the borrowing entity’s investors have potentially adverse economic interests. The lender wants repayment at market terms. The borrower’s investors want favorable financing that does not further burden their capital stack. The sponsor controls both sides of the transaction.
The SEC has consistently identified this structure as a high-priority conflict area, noting that when clients are invested in different layers of the same capital stack, they may become adverse to each other in a workout or bankruptcy scenario. The specific risks in cross-entity lending between related real estate entities include the pricing of the loan (an affiliated lender who sets terms more favorable to itself than a third-party lender would offer is transferring value from the borrower’s investors to the lender’s investors), the priority of the loan in the capital stack (a senior secured intercompany loan that subordinates the existing equity diminishes the equity investors’ recovery in a distressed scenario), and the enforcement of the loan (a lender who controls the borrower can choose when to enforce or waive remedies, and that choice is not neutral across the two investor groups).
The mitigation for cross-entity lending conflicts requires more than disclosure. It requires independent validation of the loan terms by someone who does not have an interest in the outcome of the negotiation, a defined approval process that does not allow the sponsor to approve the transaction on behalf of both the lender and the borrower, and specific disclosure to investors in both entities describing the loan’s terms, the conflicts it creates, and the independent review that was conducted. A cross-entity loan that appears as a footnote in the quarterly report is not adequate disclosure of a transaction that has materially changed the borrowing entity’s capital structure.
Building a Conflict-Resistant Multi-Entity Structure: The Design Principles
Cross-entity conflicts in a tokenized real estate multi-entity structure are structural, not accidental. They are built into the architecture the moment the same sponsor begins controlling multiple related entities with different investors. The goal of conflict management is not to pretend that these conflicts do not exist. It is to acknowledge them, design mechanisms that constrain the sponsor’s ability to act on them in ways that harm investors, and disclose them with enough specificity that investors can make informed decisions about whether to participate in a structure where those conflicts will always be present.
SEC guidance, IOSCO conflict analysis, and Delaware’s contractual LLC framework all point toward the same practical design principles. First, define the conflicts specifically before capital is raised, in the offering documents rather than in a general acknowledgment that conflicts of interest may arise. Second, constrain the sponsor’s discretion in the highest-conflict areas through written policies, independent approval requirements, and investor consent mechanisms. Third, report consistently across entity layers so that investors in each vehicle have access to the information they need to monitor the conflicts they were told about when they subscribed.
| The Cross-Entity Conflict Mitigation Checklist: What Every Multi-Entity Tokenized Real Estate Structure Must Address Before Launch • Written allocation policy: A document that specifies which types of opportunities each vehicle in the platform has priority access to, how conflicts between vehicle eligibility are resolved, and how the policy is disclosed to investors in each vehicle before they subscribe. • Fee disclosure at every entity level: A complete description of every fee earned by the sponsor or any affiliate at every entity level in the structure, including the fund, each SPV, the platform, and any service provider. Generic descriptions of fee types are not sufficient when the fees are actually being charged. • Cross-entity transaction policy: Written procedures governing any transaction between related entities, including affiliated lending, intercompany services, expense sharing, and rescue financing. The policy must specify independent pricing validation, independent approval authority, and specific disclosure to investors in each affected entity. • Independent oversight mechanism: An advisory committee, independent director, third-party administrator, or other oversight function with the authority to review and approve related-party transactions and to report directly to investors on the exercise of that oversight. • Consistent reporting across entity layers: Reporting to investors in each vehicle that includes the same categories of information about affiliated transactions, intercompany obligations, fee payments, and allocation decisions, so that no investor group is operating from a materially different factual base about the same underlying structure. • Governance divergence disclosure: Specific disclosure to token holders that the platform’s unified interface does not reflect unified governance rights, and that each investor’s governance rights are defined by the operating agreement of the specific entity in which they invested, not by the platform’s governance features. • On-chain and off-chain record consistency: A written protocol specifying which record is authoritative for each category of ownership and transaction information, and how discrepancies between on-chain and off-chain records are identified and resolved, so that investors in different entities are not relying on different records that reflect the same transaction differently. |
The Bottom Line
The sponsor in the opening scenario did not set out to harm investors. Each decision, the allocation of the best assets to the highest-fee vehicle, the intercompany loan at sponsor-determined terms, the unified platform interface that obscured entity-level differences, was individually defensible and collectively problematic. The harm was not in any single action. It was in the accumulation of discretionary decisions made by a single sponsor across multiple entities with different investors, over three years, in an environment where the digital presentation made the structure look more unified than the legal documents made it.
Cross-entity conflict in a tokenized real estate multi-entity structure is not a failure of the technology. The platform worked as designed. The blockchain recorded every transfer and every distribution accurately. The tokens represented what the governing documents said they represented. The conflict was in the decisions the sponsor made using the discretionary authority the governing documents granted, across entities whose investors had different information, different economic interests, and no mechanism for coordinating their response to a sponsor whose incentives were not uniformly aligned with all of them.
The structure that can manage cross-entity conflicts is not the one that eliminates the sponsor’s discretion. Discretion is essential for managing real estate investments through uncertain markets. It is the structure that constrains the exercise of discretion in the highest-conflict areas through written policies, independent oversight, consistent disclosure, and governance mechanisms that give investors in each entity the information and the tools to hold the sponsor accountable to the obligations it undertook when they subscribed. Building that structure requires treating cross-entity conflict as a design problem to be solved before the first token is issued, not a disclosure footnote to be added after the documents are otherwise complete.