Before any token exists

Three things happen first, and they constrain everything afterwards.

The holding entity. A legal entity is formed to own the property, since a registry records title in the name of a legal owner. The entity's jurisdiction, form, and governing documents determine who controls decisions, how income can be distributed, and what happens on a sale, and none of that is changed later by the ledger.

Title and encumbrances. Existing mortgages frequently restrict transfer of the property or of interests in the owner, and lender consent may be required. Where the asset carries debt, the lender's position is senior to everything the structure does above it.

The offering structure. Interests sold to passive participants are generally securities, so the offering proceeds under an exemption or a registration, with the associated limits on who may invest, how it may be marketed, and what disclosure is required. This step decides whether the eventual token can be offered publicly, to accredited participants only, or to a specific jurisdiction's investors.

By the time anyone writes a contract, the economics and the constraints already exist. The technical layer implements decisions taken in these three steps rather than making them.

The technical layer, and why it is mostly restrictions

Token standard and transfer control. The distinguishing feature of a security token relative to an ordinary fungible token is that transfers are conditional. Transfers check an allowlist, jurisdiction rules, holding periods, or investor caps before succeeding. A structure whose token could move freely to anyone would in most cases be out of compliance, which is why the interesting engineering is in the restriction logic rather than the transfer itself.

The register. Someone must maintain the authoritative record of who holds what. Either a transfer agent maintains it with the ledger mirroring it, or the ledger is treated as the register with an agent reconciling. Both exist, and which one applies changes what happens when a holder loses access to their keys, which is a question worth asking early.

Custody and key management. Holders need a way to hold interests without the loss of a private key destroying an ownership record. Structures address this with custodial options, recovery mechanisms, or an agent who can reissue against the register. The traditional answer, that ownership is a record someone maintains and can correct, turns out to be a feature rather than a limitation.

Oracles and valuation. Where a structure references property value, that number comes from an appraisal or an index rather than from a market, and it updates rarely. Anything in the design that assumes a continuously observable price is assuming something property does not provide.

The parts that never stop

Issuance gets the attention and the operating burden is what determines whether a structure survives.

Income distribution. Rent arrives in fiat, expenses are paid in fiat, and the net has to reach holders. Doing that onchain requires converting or holding a stable settlement asset and executing many small payments, which is exactly the workload conventional distribution rails handle badly and where onchain settlement has a genuine cost advantage.

Reporting. Holders and regulators expect statements, valuations, and disclosures on a schedule. This is unavoidable operational work.

Property operations. Tenants, leases, maintenance, insurance, vacancy, and capital expenditure. The asset is a building and it behaves like one.

Corporate actions. Refinancing, capital calls, changes to the governing documents, and disputes among holders. Structures with many small holders make these harder than a conventional syndication with a handful of parties, and the governance provisions written at formation are what decide whether they are manageable.

Wind-down. The most underplanned part. At some point the property is sold, the entity distributes proceeds, and the tokens are retired. Whether that requires unanimous consent, a majority, or a sponsor decision is settled in the governing documents, and structures that never specified it discover the gap at the least convenient moment.

This is general information rather than legal advice. Securities structuring and property transfer are jurisdiction-specific and fact-specific, and both belong with qualified counsel before anything is offered.

Where the model is strongest

Given all of the above, the structures most likely to work share a shape.

Income-producing assets with predictable cash flows, where the distribution burden is the main administrative cost and onchain settlement genuinely reduces it. Clear single-jurisdiction title, so the legal wrapper is straightforward. A sponsor with conventional property operating capability, because the building still needs running. And a realistic position on liquidity, since a structure that promises a secondary market it cannot supply creates an expectation it will fail to meet.

The weakest structures invert those: complex or cross-border title, assets whose value depends on development outcomes, sponsors whose expertise is the token rather than the property, and marketing that leads with liquidity and tradability.

That pattern is useful when reading any specific offering, because it distinguishes projects using a ledger to reduce a real administrative cost from projects using property as a reason to issue a token.