What tokenization is and is not

"Tokenization" is used for very different things: a bond issued directly on a blockchain, a token that points to gold in a vault, a fund share whose register happens to be kept on-chain. For a professional the label says almost nothing. What matters is what the holder legally owns, which record decides ownership, and who can stop or reverse a transfer.

Two kinds of tokenized asset

The most useful distinction is between native digital issuance and tokenized representation.

A native digital asset (also called a digitally native security) exists only on the ledger. The token is the asset because a law says so: the on-chain register is the legal register of ownership. Examples are bonds issued as crypto securities under Germany's Electronic Securities Act (eWpG), ledger-based securities under Swiss law, or the digital bonds that the European Investment Bank has issued on public and private blockchains since 2021. If the ledger shows you as holder, you are the holder.

A tokenized representation is a token that stands for an asset that exists and is recorded somewhere else: a share in a fund, a bar of gold, a loan, a building. The token is a claim, usually a contractual one, against an issuer or a special purpose vehicle that holds the asset. The real register of ownership may still be kept off-chain, for example by a transfer agent, a custodian or a land registry. If the token and the off-chain record disagree, the off-chain record usually wins.

Most real-world asset (RWA) tokens on the market today are representations, not native assets. That is not a flaw in itself, but it moves the key risks off-chain: the issuer, the custodian of the underlying asset and the legal link between them. Those risks are the subject of the lesson Risk and due diligence for RWA tokens.

The register and the legal claim

Every tokenized asset has at least three layers, and they can fail separately.

• The underlying asset: Treasury bills, a building, a receivable, an ounce of gold. It is held by someone, often a custodian or a vehicle.
• The legal claim: the bundle of rights the holder has, set by a prospectus, fund documents, a trust deed or statute. It answers "what can I enforce, against whom, under which law?"
• The register: the record that says who holds the claim. In a native issuance the blockchain is the register. In a representation the blockchain may be the register, a mirror of it, or just a convenient transfer layer.

A useful test is to ask: if the private key is lost, or the chain halts, what happens to my rights? For a well-built representation the answer is that the issuer or transfer agent can identify the holder off-chain and reissue the token. For a bearer-style token with no off-chain record, the asset may be gone. Neither answer is right or wrong, but a professional must know which one applies before accepting the token as an asset, as collateral or as a custody responsibility.

Token standards for real-world assets

Fungible tokens on Ethereum and compatible chains mostly follow ERC-20, the basic interface for balances and transfers. ERC-20 knows nothing about investors, eligibility or legal restrictions: anyone holding the token can send it to any address. That is a problem for securities, which usually may only be held by verified, eligible investors.

Security token standards add rules on top of ERC-20:

Two features recur in every security token design. First, a compliance check runs before each transfer: is the receiver on the allowlist, would the transfer breach a country or holder-count limit? Second, the issuer or its agent has administrative powers: freezing an address, burning and reissuing tokens to a new wallet after a lost key, or forcing a transfer when a court orders it. These powers are what make the token legally workable, and they are also a concentration of risk, because whoever controls the admin key controls the asset.

Permissioned and public chains

Tokenized assets are issued on two broad kinds of infrastructure.

Permissioned (private) ledgers restrict who can run nodes and who can transact. Examples include bank platforms such as JPMorgan's Kinexys and the Canton Network used by several large institutions. The operator knows every participant, can meet confidentiality obligations and can fix errors. The cost is limited reach: assets on one private ledger do not easily meet assets or cash on another.

Public chains such as Ethereum, its layer-2 networks, Solana or Stellar let anyone run a node and read the ledger. Many tokenized funds now issue there, but restrict who can hold the token through an allowlist enforced by the smart contract. This model is sometimes called "permissioned tokens on a permissionless chain." It gains reach and composability (the token can be used in other smart contracts) but exposes holdings to public view, depends on a validator set the issuer does not control, and inherits the chain's smart-contract risks.

Choosing between them is a trade-off between control, privacy and interoperability, not a question of one being modern and the other old.

Claimed benefits and real ones

Tokenization is promoted with a long list of benefits. Some are real today, some depend on conditions that do not yet exist.

The pattern is that tokenization improves the transfer and record-keeping layer. It does not change the economics of the underlying asset. An illiquid property is still illiquid, a risky loan is still risky, and a Treasury bill earns the same yield whether it is held in a token or in a brokerage account, minus the extra fees.

What a professional should ask first

Before going further into structures and products, five questions classify almost any tokenized asset:

1. Is the token the asset itself (native) or a claim on an asset held elsewhere (representation)?
2. Which record is legally decisive: the blockchain or an off-chain register?
3. Who is the issuer, which law governs the claim, and what happens in the issuer's insolvency?
4. Which token standard and which chain, and who holds the administrative keys?
5. How does a holder exit: redemption with the issuer, a secondary market, or both?

The legal side of questions 2 and 3 is developed in the lesson Legal structures for tokenized assets.

Exam focus: the difference between native digital issuance and tokenized representation; the three layers (underlying asset, legal claim, register) and why the decisive register matters; what ERC-20 lacks for securities and what ERC-1400 and ERC-3643 add (identity-based transfer checks, partitions, freeze, recovery and forced transfer); why admin powers are both a legal necessity and a risk; permissioned ledgers versus permissioned tokens on public chains; which claimed benefits are real (programmability, collateral mobility, same-ledger settlement) and which are often overstated (liquidity, cost, 24/7 redemption).