On-chain ownership is the record in your wallet - the token balance a blockchain says is yours. Legal ownership is the claim a court or regulator will actually enforce - usually shares in the entity that holds the asset. In a well-built RWA the two point to the same thing, so moving the token moves the claim. When they come apart, the legal record wins, because a token cannot override the law that governs the asset.

Two kinds of ownership, one asset

Every tokenized asset lives in two worlds at once. The on-chain world knows one fact: which address controls the token. The off-chain legal world knows a different fact: who holds title to the asset, and under what agreement. Tokenization tries to keep those two facts in sync so that the on-chain record is a faithful mirror of the legal one.

They are not the same thing, though. A blockchain can prove you control a private key and therefore the token. It cannot, by itself, prove you own a building - that depends on a legal structure the chain knows nothing about. The token is evidence of the claim, not the claim itself.

How the two are kept in sync

In a standard deal the asset sits in a special-purpose vehicle, and your legal claim is shares or a membership interest in that SPV, set out in a subscription agreement you sign when you invest. The token is then issued one-to-one against those shares. The link that makes them move together is usually a transfer agent: the agent keeps the official register of owners and treats the token holder as the record holder, so a valid on-chain transfer updates who legally owns the shares.

This is also why most return-paying RWAs are built as security tokens with rules baked into the contract. The smart contract enforces a transfer restriction so the token can only move between approved, identity-verified addresses on a whitelist. That is the on-chain side keeping itself compatible with the off-chain law: the code refuses transfers that would break the legal structure, like selling to someone who is not allowed to own the security.

What happens when they disagree

The two records can drift apart, and when they do the legal layer governs. A few common cases:

• Lost or stolen key. On-chain, whoever holds the key controls the token. Legally, a theft does not transfer ownership - so the issuer or transfer agent can freeze the address and reissue the token to the rightful owner.
• A forced correction. Courts, inheritance, or a sanctions match can require moving a claim regardless of who holds the key. Permissioned security tokens are built to allow this; a pure bearer token is not.
• A broken link. If the token was never properly tied to the SPV shares - weak documents, no transfer agent - you may hold a token that proves nothing in court. This is the failure we see break deals most often: the code works, the claim does not.

The takeaway is not that on-chain ownership is fake. It is that the token's power comes entirely from the legal claim standing behind it. Strong claim, and the token is a fast, auditable way to hold and move it. No claim, and it is just a number.

How this changes what you check

Because legal ownership is the backstop, due diligence on an RWA is mostly off-chain work. Confirm there is a real entity holding the asset, that your token maps to a documented interest in it, and that a named party - a transfer agent or equivalent - keeps the two in sync. On-chain, check that transfers are actually restricted to approved holders; a return-paying "security" that anyone can freely trade to anyone is a red flag, not a feature.

Self-custody changes your control, not your claim. Holding the token in a self-custody wallet means you move it without a middleman, but the legal claim behind it is identical to the custodial version. Custody decides who holds the keys; the legal structure decides what those keys are worth.

Where to go next

• Next: what proof of reserves is and how backing is verified.
• Back to the pillar: what you actually own in a tokenized asset.
• Glossary: the role of a transfer agent.

Sources: U.S. SEC (sec.gov); rwa.xyz, as of 2026.