Tokenized real-world assets: issuer, records and rights

A token can sit in several different legal and record systems

A tokenized real-world asset is not one universal contract. Depending on the design, an issuer may use a network as part of its official ownership record; an intermediary may hold an asset and issue a separate claim; a token may be a notice or transfer instruction that updates an offchain register; or an unrelated party may issue a token that only references an asset or price. The token can also exist without creating a right against the underlying asset's issuer.

The SEC staff's January 28, 2026 statement discusses U.S. tokenized securities, not every real-world asset or every jurisdiction. It describes issuer-sponsored and third-party models and explains that holder rights and obligations can differ. It is useful evidence that model and rights matter, not a decision about a particular token, issuer, offer or user's legal status.

Evidence: SEC staff views on tokenized securities (U.S. federal law) · BSC overview

This is a staff statement by three SEC divisions addressing U.S. federal securities laws and tokenized securities. It describes models and staff views, not every real-world asset, a specific issuer, a fact-specific legal determination, or rules in other jurisdictions. It does not establish that any particular token is a security or compliant.

Used only for BNB Smart Chain identity and EVM compatibility. The same page includes time-bound performance, fee and adoption figures; they are not treated as current facts or a current support/availability list.

Ask who owes what to whom, under which document

Start with the named legal issuer and the person or entity that promises performance. Then identify the instrument that defines the claim: for example, a share, custody entitlement, debt, delivery agreement or a token that merely references an underlying asset. Read who is the counterparty, how a holder is recognized, what transfers, whether redemption or delivery is promised, which conditions apply and what law and forum govern a dispute.

A token balance can be evidence of what a contract records on a network. It does not by itself prove that the issuer recognizes the address, that a custodian holds the asset, that a contract promise is enforceable, that a holder has voting or payment rights, or that an asset can be redeemed. A third-party failure or insolvency may add a risk that the underlying asset holder would not face. BNB Chain is a network, BNB is an asset, and Binance Exchange is a separate service; a chain record does not by itself prove that Binance is the issuer or recorded a customer-account balance.

Evidence: SEC staff views on tokenized securities (U.S. federal law) · BSC overview

This is a staff statement by three SEC divisions addressing U.S. federal securities laws and tokenized securities. It describes models and staff views, not every real-world asset, a specific issuer, a fact-specific legal determination, or rules in other jurisdictions. It does not establish that any particular token is a security or compliant.

Used only for BNB Smart Chain identity and EVM compatibility. The same page includes time-bound performance, fee and adoption figures; they are not treated as current facts or a current support/availability list.

A precise example: a Delaware corporation's stock ledger

Delaware General Corporation Law Title 8, §224 permits corporate records, including a stock ledger, to be kept using electronic networks or databases, including distributed ones, if the records can be converted to clearly legible paper within a reasonable time and the stock-ledger requirements are met. Section 219(c) defines the ledger as records administered by or for the corporation that record stockholders of record, their addresses and shares, and issuances and transfers in accordance with §224. It says that ledger is the evidence for the specified rights to inspect a meeting list or vote under that section.

The limited lesson is not that any token equals a share. A token balance is not shown to be a Delaware corporation's ledger merely because it is on a distributed network. The evidence must connect the issuer's administered record, the share and transfer rules, and the holder's recognized entry. These statutory sections are a Delaware example for corporations subject to that law; they do not settle the rules for another jurisdiction, asset, company or contract.

Evidence: Delaware corporate stock-ledger record rules, §§219(c), 224

A narrow Delaware corporation example: §224 permits specified corporate records, including a stock ledger, to use electronic or distributed networks subject to conditions; §219(c) defines and gives an evidence role to the corporation-administered ledger for rights specified in that section. It does not make an arbitrary onchain balance a stock ledger, decide a particular holder’s status, or generalize to other entities, assets or jurisdictions.

Keep jurisdiction and classification attached to the evidence

The SEC staff statement describes models and views about the U.S. federal securities laws. It notes that token format does not, by itself, decide how those laws apply and that third-party tokens may or may not represent ownership or contractual obligations of the underlying issuer. It is a staff statement, not a fact-specific ruling or a universal legal test. Do not use it to declare that a token is or is not a security elsewhere.

For any other claim, identify the asset's situs if relevant, issuer's legal entity, governing law, place of offer, service provider and dispute forum. A regulator page may describe only one jurisdiction or product class. The correct result can depend on documents and facts not visible onchain; a qualified professional in the relevant jurisdiction must assess personal legal consequences. This guide does not classify an offering or determine compliance.

Evidence: SEC staff views on tokenized securities (U.S. federal law) · Delaware corporate stock-ledger record rules, §§219(c), 224

This is a staff statement by three SEC divisions addressing U.S. federal securities laws and tokenized securities. It describes models and staff views, not every real-world asset, a specific issuer, a fact-specific legal determination, or rules in other jurisdictions. It does not establish that any particular token is a security or compliant.

A narrow Delaware corporation example: §224 permits specified corporate records, including a stock ledger, to use electronic or distributed networks subject to conditions; §219(c) defines and gives an evidence role to the corporation-administered ledger for rights specified in that section. It does not make an arbitrary onchain balance a stock ledger, decide a particular holder’s status, or generalize to other entities, assets or jurisdictions.

Solved fictional case: 30 ORCH tokens and a delivery promise

Fictional example only: a made-up network record shows 30 ORCH units at a placeholder address. A promotional page calls ORCH a share in Demo Orchard Inc., a fictional corporation described as incorporated in Delaware. No real company, token, address, chain record or offer exists. No governing document or company stock ledger is supplied.

Result: the hypothetical record supports only that the named fictional contract reports 30 units at that placeholder address. It does not prove the person behind the address, recognized stockholder status, 30 company shares, voting or dividend rights, ownership of an orchard, a delivery claim, or redemption. Because the issuer's administered stock ledger and contract terms are absent, the claimed share and any enforceable right remain unknown. Under the Delaware example, the next decisive question is whether this record is actually part of the corporation's §219/§224-compliant stock ledger—not whether the token uses the word “share.”

Compare a second fictional document: suppose an identified issuer signs terms that expressly promise one basket of fictional fruit per ORCH unit to a defined contractual holder, state the delivery date and conditions, and name the governing law and dispute forum. If authentic and applicable, those terms could support a claim against that named issuer within their wording; they would not automatically establish ownership of the orchard, a share, guaranteed delivery, or a claim against Binance. The documents and counterparty still need independent verification.

Evidence: SEC staff views on tokenized securities (U.S. federal law) · Delaware corporate stock-ledger record rules, §§219(c), 224

This is a staff statement by three SEC divisions addressing U.S. federal securities laws and tokenized securities. It describes models and staff views, not every real-world asset, a specific issuer, a fact-specific legal determination, or rules in other jurisdictions. It does not establish that any particular token is a security or compliant.

A narrow Delaware corporation example: §224 permits specified corporate records, including a stock ledger, to use electronic or distributed networks subject to conditions; §219(c) defines and gives an evidence role to the corporation-administered ledger for rights specified in that section. It does not make an arbitrary onchain balance a stock ledger, decide a particular holder’s status, or generalize to other entities, assets or jurisdictions.

Build an evidence chain without buying or connecting anything

On paper, record: exact token and network; contract and token identifier; named issuer and its legal entity; underlying-asset evidence; governing instrument and authorized signatory; the official register or custodian record; holder-recognition and transfer rules; redemption or delivery conditions; custody and insolvency terms; governing law and forum; and the source date. For a BNB Chain claim, distinguish BSC or opBNB from a Binance exchange screen and from BNB itself.

Mark each link verified, contradicted or missing. A missing contract, register, issuer identity or jurisdiction is a real unresolved gap, not evidence of a right. Do not infer yield, value, liquidity, safety, compliance or a financial result from a token count. This exercise uses no live contract, account or transaction and offers no legal or investment recommendation.

Evidence: SEC staff views on tokenized securities (U.S. federal law) · Delaware corporate stock-ledger record rules, §§219(c), 224 · BSC overview

This is a staff statement by three SEC divisions addressing U.S. federal securities laws and tokenized securities. It describes models and staff views, not every real-world asset, a specific issuer, a fact-specific legal determination, or rules in other jurisdictions. It does not establish that any particular token is a security or compliant.

A narrow Delaware corporation example: §224 permits specified corporate records, including a stock ledger, to use electronic or distributed networks subject to conditions; §219(c) defines and gives an evidence role to the corporation-administered ledger for rights specified in that section. It does not make an arbitrary onchain balance a stock ledger, decide a particular holder’s status, or generalize to other entities, assets or jurisdictions.

Used only for BNB Smart Chain identity and EVM compatibility. The same page includes time-bound performance, fee and adoption figures; they are not treated as current facts or a current support/availability list.