Native Tokenization of Equity

Part I - U.S./Delaware

For a Delaware corporation whose equity is represented in tokenized form, when can a blockchain token be legally “native” or constitutive equity—meaning the distributed ledger is part of the issuer’s operative stock ledger and transfer register—rather than merely a synthetic exposure, a custody entitlement, a credential, or a mirror of an off-chain register?

Assumptions

The issuer is a Delaware corporation. The instrument is intended to represent corporate stock, not merely a derivative, linked note, swap, depository receipt, or contractual claim. U.S. federal securities law applies where offers, sales, transfer-agent functions, or market infrastructure use interstate commerce.

Executive Summary

• Delaware law permits a corporate stock ledger to be kept on “1 or more distributed electronic networks or databases,” but that permission is conditional. The records must be convertible into clearly legible paper form, must support stockholder lists and inspection rights, must record statutorily required stockholder information, and must record transfers as governed by UCC Article 8. A wallet-address-only ledger is not enough if the corporation cannot identify names, addresses, shares registered, issuances, and transfers. Official source: 8 Del. C. §224.

• For Delaware corporate stock, legal transfer is an Article 8 problem, not merely a cryptographic-control problem. Delaware corporate shares are personal property transferable under Article 8; corporate equity is a “security”; and delivery of an uncertificated security occurs when the issuer registers the purchaser as registered owner. Native tokenization therefore requires the on-chain state, alone or with issuer-administered linked records, to function as the issuer’s legally operative registration system. Official sources: 8 Del. C. §159; 6 Del. C. §§8-103, 8-301.

• Delaware Article 12 does not make “token control” sufficient for corporate stock ownership. A controllable electronic record expressly excludes “investment property,” while Article 8 classifies corporate shares as securities. Article 12 may matter for non-stock token attributes or non-security digital records, but it does not displace DGCL stock-ledger rules or Article 8 securities-transfer rules for equity. Official source: 6 Del. C. Article 12.

• If an off-chain transfer-agent record remains authoritative and token movement merely notifies the issuer or transfer agent, the token is not native equity in the legal sense. In that structure, stockholder status follows the issuer’s stock ledger and Article 8 registered-owner rules, not possession of the token alone. Official sources: 8 Del. C. §219; 6 Del. C. §8-207.

• Transfer restrictions, stop-transfer demands, legal process, and wrongful-registration rules must be embedded or operationally respected. A smart contract that allows automatic transfer when Article 8 conditions are not satisfied can create wrongful-registration risk; conversely, a smart contract that hard-codes restrictions without legally effective notice may fail against purchasers without knowledge. Official sources: 6 Del. C. §§8-204, 8-401 to 8-404.

• Intermediation changes the legal object. If tokenized shares are held through a broker, custodian, or securities account, the customer generally holds a “security entitlement” against the intermediary rather than direct record ownership, unless Article 8’s direct-holder exception applies. That is legally different from native direct holding. Official source: 6 Del. C. Part 5.

• Federal securities law is format-neutral for these purposes. “Stock” and “investment contract” are securities under the Securities Act, and offers or sales using interstate commerce require registration unless an exemption applies. Tokenizing stock does not remove Securities Act §5 exposure. Official sources: Securities Act §§2(a)(1), 5; 15 U.S.C. §§77b(a)(1), 77e.

• Transfer-agent law remains central. A person that registers transfers, monitors issuance, countersigns securities, or transfers record ownership by bookkeeping entry can be a “transfer agent.” For covered securities, Exchange Act §17A makes it unlawful for an unregistered transfer agent to use interstate commerce to perform transfer-agent functions, absent exemption. Official sources: Exchange Act §§3(a)(25), 17A; 15 U.S.C. §§78c(a)(25), 78q-1.

• For public/reporting equity, SEC Rule 17Ad-20 materially constrains “closed” tokenization designs. A registered transfer agent may not transfer a covered equity security if it is subject to a restriction or prohibition on transfer to or from a securities intermediary in its intermediary capacity. Official source: 17 C.F.R. §240.17Ad-20.

• The SEC staff’s 2026 statement is useful but not binding. It distinguishes issuer-sponsored tokenized securities where DLT is integrated into the master securityholder file from models where the network merely notifies an off-chain recordkeeper; however, the statement expressly says it has no legal force and does not alter federal securities laws. Official source: SEC Staff Statement on Tokenized Securities, 2026-01-28 / updated 2026-01-30.

Can a Delaware corporation use a distributed ledger as its legally operative stock ledger?

Conclusion: Yes, but only if the ledger system satisfies Delaware corporate-law functions. The legal test is not “is there a blockchain token?” but “does the corporation’s record system meet DGCL §§219 and 224?”

Rule: DGCL §224 permits corporate records, including the stock ledger, to be kept by means of electronic networks or databases, including distributed electronic networks or databases, if the records can be converted into clearly legible paper form within a reasonable time. For the stock ledger, §224 requires records that can prepare the stockholder lists required by §§219 and 220, record specified statutory information, and record transfers governed by Article 8. DGCL §219 defines the stock ledger as records administered by or on behalf of the corporation containing the names of stockholders of record, their addresses, number of shares registered, and all issuances and transfers. It further provides that the stock ledger is the only evidence of the stockholders entitled to examine the list or vote.

Application: A Delaware-native tokenized equity system is legally plausible where the blockchain, together with issuer-administered associated records, is the corporation’s stock ledger. The ledger must identify record stockholders, not merely wallet addresses, unless wallet addresses are linked in issuer-administered records to the statutorily required names, addresses, share counts, issuances, and transfers. A purely public token balance display that cannot produce the DGCL-required stockholder list, or that cannot be converted into a legible paper record, is not sufficient as the legal stock ledger.

A permissioned or hybrid architecture is more straightforward than a bare public-chain balance table because DGCL §219 and §224 require record-owner identity, addresses, and transfer history. Delaware does not require that all such data be public on-chain; it requires that the corporation’s records contain the required information and perform the required functions. The legal design question is therefore whether the issuer-administered system, taken as a whole, makes token transfer equal to registered transfer.

Limitations and counterarguments: DGCL §224 is enabling, not self-executing. It does not say that every token ledger is a stock ledger. It permits distributed networks only if the statutory record functions are satisfied. For uncertificated shares, the board must also resolve that some or all shares are uncertificated under DGCL §158.

When does token transfer become legal transfer of Delaware corporate stock?

Conclusion: Token transfer becomes legal stock transfer only when it constitutes or causes Article 8 registration of transfer on the issuer’s books. Cryptographic control alone is insufficient unless the blockchain state is the issuer’s registered-owner record.

Rule: DGCL §159 states that shares of stock are personal property and transferable as provided in Article 8 of Title 6. Delaware UCC §8-103 provides that a share or similar equity interest issued by a corporation is a security. UCC §8-301 provides that delivery of an uncertificated security occurs when the issuer registers the purchaser as registered owner upon original issue or registration of transfer, or when another person becomes registered owner on behalf of the purchaser and acknowledges that it holds for the purchaser. Before due presentment for registration or receipt of an instruction, the issuer may treat the registered owner as exclusively entitled to vote, receive notifications, and exercise ownership rights.

Application: A legally native tokenized share must collapse token transfer and issuer registration into the same legally recognized event. That can be done if the smart-contract ledger is administered by or on behalf of the issuer and a valid token transfer updates the issuer’s registered-owner records. In that model, the on-chain transfer is not merely evidence of a transfer; it is the transfer-registration mechanism.

By contrast, if a transfer agent maintains an off-chain master securityholder file and token transfers merely send notifications, credentials, or settlement instructions, legal ownership remains with the person shown on the issuer’s stock ledger until the transfer is registered. In that structure, the token is a useful technical artifact, but it is not native equity. The legal “thing” owned by the stockholder is the Article 8 security registered on the issuer’s books, not the token as such.

The official SEC staff taxonomy is consistent with this distinction, but only as nonbinding administrative material. The staff describes an issuer-sponsored tokenized security where DLT is integrated into the master securityholder file so that network transfer results in a master-file transfer, and distinguishes that from a model where the network is not part of the master file and merely prompts off-chain updates. The same statement expressly says it is staff views only and has no legal force.

Does Delaware Article 12 make token control enough for stock ownership?

Conclusion: No. Article 12 is not the governing ownership-transfer regime for Delaware corporate stock because a controllable electronic record excludes investment property, and corporate stock is an Article 8 security.

Rule: Delaware Article 12 defines a controllable electronic record but excludes, among other things, “investment property.” Article 12 also states that law other than Article 12 determines whether a person acquires a right in a controllable electronic record and what rights are acquired. Article 8 separately classifies corporate shares as securities. Article 12’s control definition focuses on power to obtain benefit, prevent others from obtaining benefit, transfer control, and identify the controller, including by cryptographic key or account.

Application: For stock, Article 8 and DGCL rules control the legal consequences of transfer, registration, adverse claims, and registered ownership. Article 12 may help analyze a token that is not itself stock, such as a digital receipt, a separable protocol asset, or a non-security claim evidenced by a token. But where the legal instrument is a share of a Delaware corporation, Article 12’s crypto-control rules do not substitute for Article 8 registration and DGCL stock-ledger compliance.

This point matters for “native tokenization” because the legal claim cannot be: “whoever controls the token necessarily owns the stock under Article 12.” For Delaware equity, the better claim must be: “the tokenized ledger is the issuer’s Article 8/DGCL-compliant stock ledger, so valid token transfer is valid issuer registration.”

Limitations and counterarguments: If the token is intentionally structured not as stock but as a separate controllable electronic record that evidences a contractual right, Article 12 may become central. That would no longer be native stock tokenization; it would be a tokenized claim or entitlement whose relationship to the underlying equity must be separately established.

How must transfer restrictions and failed or disputed transfers be handled?

Conclusion: Native tokenization must operationalize Article 8’s transfer-restriction, assurance, stop-transfer, and wrongful-registration rules. Otherwise, programmability can create legal mismatch rather than legal finality.

Rule: UCC §8-204 provides that a transfer restriction imposed by the issuer is ineffective against a person without knowledge unless the restriction is noted conspicuously on a certificated security or, for an uncertificated security, the registered owner has been notified. UCC §8-401 requires an issuer to register transfer if specified conditions are met, including appropriate instruction or endorsement, reasonable assurance, tax compliance, no violation of effective transfer restriction, no effective demand not to register or legal process, and a rightful transfer or transfer to a protected purchaser. UCC §8-402 allows the issuer to require reasonable assurance that an instruction is genuine and authorized. UCC §8-403 provides a mechanism for an appropriate person to demand that the issuer not register transfer. UCC §8-404 imposes liability for wrongful registration in specified circumstances, including ineffective instructions, registration after an effective demand without compliance, injunction, or collusion. A protected purchaser gives value, lacks notice of adverse claims, obtains control, and takes free of adverse claims.

Application: A native ledger must do more than prevent double-spending. It must encode or operationally respect legal eligibility, transfer restrictions, stop-transfer demands, injunctions, reasonable assurance procedures, tax-related conditions, and issuer authority. For example, a smart contract allowing any holder to transfer tokenized restricted shares without issuer-level notice and eligibility checks could produce a transfer that the issuer is not required to register. Conversely, if the smart contract’s on-chain transfer is the registration event, the issuer may face wrongful-registration exposure if the transfer was based on an ineffective instruction or occurred after a valid stop-transfer demand or injunction.

Automatic collateral enforcement and liquidation are possible in principle but fragile in legal design. If a secured party’s smart contract transfers shares upon default, the legal result depends on whether the secured party has a valid instruction, whether the purchaser is protected, whether transfer restrictions are satisfied, and whether the issuer’s registration duty is triggered. A purely mechanical token liquidation may not defeat adverse claims unless Article 8 requirements are met.

What happens when tokenized shares are held through an intermediary?

Conclusion: Intermediated holding generally converts the investor’s legal position from direct record stockholder to entitlement holder, unless the structure fits Article 8’s direct-holder exception. This is a different legal product from native direct equity.

Rule: UCC §8-501 provides that a person acquires a security entitlement when a securities intermediary credits a financial asset to the person’s securities account or otherwise agrees to treat the person as entitled to the financial asset. It also states that a person who holds a financial asset directly from an issuer or in registered form is not a securities intermediary with respect to that financial asset. UCC §§8-503 and 8-504 provide that financial assets held by a securities intermediary are not property of the intermediary, are held for entitlement holders, and must be maintained in sufficient quantity. UCC §§8-505, 8-506, 8-507, and 8-508 impose duties on the intermediary regarding payments, voting and other rights, entitlement orders, and wrongful transfer.

Application: If a custodian or broker is the registered owner of tokenized shares and customers hold account credits, the customer generally owns a security entitlement, not direct stock on the issuer’s ledger. The token may still move on-chain at the intermediary level, but the customer’s legal rights are against the intermediary under Article 8 Part 5. That structure may be commercially useful, but it is not the strongest form of native tokenization because the end investor is not the record stockholder.

The direct-holder exception is important. If the issuer’s ledger registers the individual investor directly and the intermediary is merely a technical agent without crediting a securities account or assuming entitlement obligations, the investor may remain a direct holder. But that result depends on the account agreement, registration architecture, and who is shown on the issuer’s stock ledger.

What federal securities-law consequences attach to native tokenized stock?

Conclusion: Tokenized stock remains a security. Offers, sales, transfer-agent activity, and public/reporting equity infrastructure remain subject to federal law.

Rule: Securities Act §2(a)(1) defines “security” to include stock, transferable shares, notes, bonds, investment contracts, certificates of interest or participation, and other enumerated instruments. Securities Act §5 makes it unlawful, absent an effective registration statement or exemption, to use interstate commerce or the mails to sell securities, deliver securities after sale, or offer securities before a registration statement has been filed. Exchange Act §3(a)(25) defines “transfer agent” to include persons engaging on behalf of an issuer, or as issuer, in countersigning securities, monitoring issuance to prevent unauthorized issuance, registering transfers, exchanging or converting securities, or transferring record ownership by bookkeeping entry without physical certificates. Exchange Act §17A makes it unlawful for a transfer agent to use interstate commerce to perform transfer-agent functions for specified covered securities unless registered, absent an exemption.

Application: A Delaware corporation cannot avoid Securities Act registration or exemption requirements by issuing shares as tokens. If the token is stock, it is a security because stock is expressly included in the statutory definition. If the token is not formally stock but represents a profit-linked or managed enterprise claim, it may still be a security under other statutory categories, but that point is outside the core native-stock assumption.

A native ledger that updates record ownership by bookkeeping entry appears to perform functions that fit the statutory transfer-agent definition when done by the issuer, transfer agent, or another person acting on the issuer’s behalf. For covered securities, the relevant transfer agent must be registered unless an exemption applies. SEC transfer-agent rules also require registered transfer agents to maintain current records, including records of received items, transfers, restrictions, authorized and outstanding shares where applicable, and other recordkeeping categories. Rule 17Ad-10 requires recordkeeping transfer agents to post debits and credits promptly and accurately to the master securityholder file and maintain accurate master and subsidiary files; it also requires a control book for each issue, with changes made only on written authorization from an authorized issuer agent.

For public/reporting equity, Rule 17Ad-20 adds a design constraint: a registered transfer agent may not transfer a covered equity security if it is subject to a restriction or prohibition on transfer to or from a securities intermediary in its capacity as such. A tokenization design that excludes all securities intermediaries may therefore be incompatible with public/reporting equity transfer-agent processing unless it fits an exception.

What is the legal difference among native tokenization, mirrored tokenization, custodial tokenization, and synthetic tokenization?

Conclusion: The legally meaningful distinction is not technological; it is where legally operative ownership sits.

Rule: Delaware law makes the stock ledger the only evidence of stockholders entitled to inspect or vote, and Article 8 permits the issuer to treat the registered owner as exclusively entitled to ownership rights until due presentment or instruction changes the registration. Article 8 creates a separate entitlement regime for securities credited through securities intermediaries. Federal law treats stock and many stock-linked instruments as securities regardless of token format.

Application: The categories can be stated as legal outcomes:

Native or constitutive tokenized stock exists where the distributed ledger is itself part of the issuer-administered stock ledger/master securityholder file, and valid token transfer is valid issuer registration of transfer.

Mirrored or pointer tokenization exists where token movement is evidence, notice, or instruction to update an off-chain ledger, but record ownership changes only when the off-chain register changes.

Custodial or intermediated tokenization exists where a broker, custodian, or other intermediary is the direct holder and customers have security entitlements or contractual claims.

Synthetic tokenization exists where the token gives economic exposure, settlement rights, swap-like exposure, or contractual payment rights without record stock ownership or security entitlement in the underlying stock.

Part II - Comparative Country Analysis

Question Presented. Across selected jurisdictions, when can a blockchain token, distributed ledger entry, or other DLT-based record be the legally operative equity record or transfer mechanism, rather than evidence of an off-chain right, an intermediated account entitlement, a custody receipt, or a synthetic financial product?

Assumptions. The instrument is ordinary corporate equity or an equity-like transferable security. The issuer is validly formed under the law of its jurisdiction. The question is direct legal ownership or record-holder status, not purely beneficial exposure. Market abuse, AML/CFT, sanctions, tax, investment company/fund regulation, insolvency set-off, data protection, and private international law are addressed only where the cited primary authorities directly affect native tokenization mechanics.

Executive Summary

• [Switzerland] Switzerland has one of the clearest native-tokenization pathways. Swiss Code of Obligations (CO) art. 622 permits shares to be issued as ledger-based securities under CO art. 973d, and art. 973d makes the right exercisable and transferable only through the securities ledger if the statutory register conditions and registration agreement are satisfied.
• [Germany] Germany's Electronic Securities Act (eWpG) now covers registered shares and central-register bearer shares. An electronic security is issued by register entry instead of a certificate; the holder is the person entered in the register; transfer of individually registered electronic securities requires re-registration on instruction plus agreement. eWpG ss. 1-4, 7, 16, 24-27, 30a.
• [France] French monetary and financial law permits DLT inscription to stand in place of securities-account inscription for qualifying financial securities. Transfer of ownership occurs by inscription to the acquirer's securities account or inscription for the acquirer through DLT. Code monetaire et financier arts. L.211-3, L.211-7, L.211-15, L.211-17; R.211-9-7.
• [European Union] Regulation (EU) 2022/858 creates a DLT market-infrastructure pilot for financial instruments issued, recorded, transferred and stored using DLT, including shares below the Regulation's quantitative thresholds. It is a market-infrastructure regime, not a general company-law rule making any token a share.
• [United Kingdom] English company membership remains register-centered: a person becomes a member when their name is entered in the register of members, and shares generally require a proper instrument of transfer unless a statutory dematerialized-transfer regime applies. The Uncertificated Securities Regulations 2001 and the Digital Securities Sandbox create controlled pathways, but there is no general free-standing token-is-share rule.
• [Luxembourg] Luxembourg law allows dematerialized securities accounts and issuance accounts to be kept through secure electronic recording devices, including distributed electronic registers. The operative legal model remains account/issuance-account inscription, not mere possession of a token.
• [Singapore] Singapore company law remains register/Registrar based. Public companies keep a register of members; private companies have an electronic register of members kept by the Registrar. MAS treats tokenized capital markets products by economic substance, but no reviewed primary company-law rule makes token movement alone a share transfer.
• [Hong Kong] Hong Kong company law remains register/proper-instrument based for shares. The SFC treats tokenized securities as traditional securities with a tokenization wrapper and applies a 'same business, same risks, same rules' approach; tokenization adds ownership and technology risk controls but does not displace the underlying legal register.
• [Cross-jurisdiction design rule] A token is legally native only where the on-chain or DLT event is itself the recognized register entry, securities-account inscription, re-registration, or statutory system transfer. If legal title changes somewhere else, the token is a mirror, custody representation, entitlement, or synthetic instrument.

Does the jurisdiction recognize a DLT entry as the constitutive equity record?

Conclusion. Recognition varies materially. Switzerland, Germany and France supply the clearest affirmative pathways. Luxembourg permits DLT-compatible account infrastructure but remains account based. The UK, Singapore and Hong Kong remain register/statutory-system based, with DLT possible only if it is embedded into the legal register, relevant system, sandbox, Registrar process, or equivalent official mechanism.

Switzerland. CO art. 622 permits shares to be issued as uncertificated or ledger-based securities where the articles provide for that form. CO art. 973d defines a ledger-based security as a right entered in a securities ledger pursuant to a party agreement and capable of being asserted and transferred only through that ledger. This is a true native route: the register is not merely evidentiary; the right is constituted as a ledger-based security and transfer must occur through the ledger. Missing facts include the issuer's articles, the registration agreement, the technical integrity of the ledger, and whether registered-share transfer restrictions or share-register obligations have been integrated.

Germany. eWpG s. 2(1) provides that an electronic security is issued when the issuer causes an entry in an electronic securities register instead of issuing a certificate. eWpG s. 3(1) identifies the holder as the person entered in the register. The statute therefore supplies a native register model for covered shares, subject to the eWpG scope rule in s. 1 and the separate share-register consequences preserved by the Aktiengesetz. For crypto securities registers, eWpG s. 16 requires a tamper-proof recording system with chronological data protected against unauthorized deletion and later alteration. This supports native tokenization where the token/ledger architecture is the statutory electronic securities register, not an external representation.

France. Code monetaire et financier art. L.211-3 states that inscription through DLT stands in place of securities-account inscription. Article L.211-7 permits qualifying non-CSD financial securities to be entered in the owner's name in an issuer account or, by issuer decision, by DLT. Article L.211-17 provides that ownership transfer results from entry in the acquirer's securities account or entry for the acquirer through DLT under art. L.211-3. France therefore recognizes a native DLT inscription route for qualifying securities, but the route is statutory and requires the DLT system to satisfy regulatory conditions, including owner identification and continuity under art. R.211-9-7.

Luxembourg. Luxembourg dematerialized securities are represented only by inscription in a securities account. The 2021 amendments allow relevant accounts and entries to be kept within or through secure electronic recording devices, including distributed electronic registers or databases; the 2024 amendments add a control-agent model. The DLT component can be legally operative if it is the account/issuance-account infrastructure recognized by the statute, but a freestanding token detached from the account framework is not enough.

United Kingdom. Companies Act 2006 ss. 112-113 make the register of members central to membership. Section 770 bars registration of a transfer unless a proper instrument of transfer has been delivered or a statutory exception applies. The Uncertificated Securities Regulations 2001 create such a statutory exception for uncertificated units transferred through a relevant system. Thus a DLT system may be native only if it is the legally recognized register/relevant system or is operated under a sandbox modification; ordinary public-chain transfer does not itself make the transferee a member.

Singapore and Hong Kong. Singapore company law centers public companies on a company-kept register of members and private companies on a Registrar-maintained electronic register. Hong Kong company law similarly requires a register of members and a proper instrument before registration of share transfer. MAS and SFC materials are substance-based supervisory guidance: they do not independently change company-law registers. Native tokenization therefore requires integration into the statutory register or official transfer process.

What event transfers legal ownership or record-holder status?

Conclusion. The operative legal transfer event is jurisdiction-specific, but the common pattern is register update, account inscription, or statutory-system transfer. Token control alone is not the cross-jurisdiction rule.

Germany. For individually registered electronic securities, eWpG s. 24 requires entry or re-registration for relevant dispositions to be effective. Section 25(1) requires re-registration to the acquirer on instruction of the beneficiary and agreement that ownership pass. Until re-registration, the beneficiary does not lose ownership. Section 26 creates good-faith effects based on register content, and s. 27 presumes ownership in favor of the registered holder.

France. CMF art. L.211-15 provides that financial securities are transmitted by account-to-account transfer or by DLT inscription under art. L.211-3. Article L.211-17 makes transfer of ownership result from the acquirer's securities-account entry or DLT entry for the acquirer. The tokenization design must therefore make the DLT inscription itself the legally recognized entry.

Switzerland. CO art. 973d and art. 973f make transfer dependent on the securities ledger and the registration agreement. A native Swiss tokenized share is not just a digital receipt; the legal right is structured so that it is asserted and transferred only through the securities ledger. The articles and registration agreement must align with share law and transfer restrictions.

Luxembourg. Transfer remains mediated by securities-account inscription and issuance-account mechanics. A DLT ledger can be the account infrastructure if it is within the dematerialized-securities statute, but transfer is not bare token possession. The relevant legal question is whether the DLT system is the statutory securities account or issuance account.

United Kingdom. In the ordinary certificated context, the company registers transfer after proper instrument delivery. In uncertificated form, title may be evidenced and transferred through a relevant system under the Uncertificated Securities Regulations 2001. That regime defines uncertificated status by recording title on the relevant Operator register and permits transfer by relevant system. A token transfer outside that regime is not enough.

Singapore and Hong Kong. Legal transfer analysis must be tied to statutory register update, Registrar filing or proper transfer instrument, as applicable. MAS and SFC guidance confirm regulatory characterization but not company-law title transfer. This makes native tokenization possible only as a systems-integration project, not by token design alone.

Direct native ownership versus intermediated tokenization

Conclusion. Intermediation often defeats the strongest form of 'native' direct equity. Where an intermediary, central securities depository, custodian, securities account keeper, or nominee is the legal holder and investors hold account claims or beneficial entitlements, the product may still be tokenized, but it is not direct native ownership by the end investor.

Germany. eWpG distinguishes individual entries and collective entries. Under s. 8, a natural or legal person may be individually entered, while a central securities depository or custodian may be collectively entered. Section 9 treats electronic securities in collective entry as a collective securities holding, with beneficiaries treated as co-owners by fractions and the custodian/CSD administering for beneficiaries. A tokenized product at the CSD/custodian layer can be legally valid but is not the same as each investor being individually registered in the electronic securities register.

France. French law allows securities to be entered through issuer accounts, intermediaries, CSD systems, or DLT depending on the category. Article L.211-4 contemplates entries in the name of one or more holders and recognizes intermediaries holding for others in specified cases. Native DLT strongest form occurs where the owner is identified directly through the DLT inscription rather than only through an intermediary account chain.

Luxembourg. The dematerialized-securities statute is account-based by design. Even where distributed registers are used, the legal framework turns on securities accounts, issuance accounts, liquidation bodies, central account keepers, and, after the 2024 amendments, control agents. Investors may hold through account keepers rather than directly on an issuer ledger.

United Kingdom. The Uncertificated Securities Regulations rely on an Operator and relevant system. Depending on structure, the relevant register may include an operator register and issuer register. This statutory system can transfer title without paper, but the legal validity comes from the Regulations, not from the token as a standalone asset.

Singapore and Hong Kong. Intermediary models are more likely than direct native corporate ledgers under current reviewed sources. In Hong Kong, the SFC circular asks intermediaries to disclose whether off-chain or on-chain settlement is final and to manage ownership and technology risks. That disclosure requirement is itself evidence that tokenization can be legally layered above different settlement/ownership models.

Regulatory overlay: offers, market infrastructure and supervisory treatment

Conclusion. Native corporate or property-law recognition does not remove securities regulation. EU, UK, Singapore and Hong Kong materials all preserve substance-based regulation of financial instruments. A native tokenized share can still require prospectus, offering, trading venue, settlement, custody, conduct and licensing compliance.

European Union. Regulation (EU) 2022/858 defines DLT financial instruments as financial instruments issued, recorded, transferred and stored using DLT and creates permissioned categories of DLT market infrastructure. It covers certain shares, bonds and fund units subject to thresholds. It is a regulatory sandbox/pilot regime for infrastructure, not an across-the-board rule that token balances equal shareholder status.

United Kingdom. The Digital Securities Sandbox under FSMA 2023 Sch. 4 and the 2023/2025 DSS Regulations is designed to let regulators modify or disapply specified enactments for FMI activities using developing technology such as DLT. It is important for pilots and production infrastructure, but its permissions and modifications are participant- and activity-specific.

Singapore. The Securities and Futures Act 2001 defines capital markets products to include securities, and securities include shares. MAS guidance applies a technology-neutral approach focused on economic substance. Tokenization therefore does not avoid capital-markets regulation where the tokenized product is a security or other capital markets product.

Hong Kong. The SFC circular states that tokenized securities are traditional financial instruments that are securities under the SFO and use DLT in their lifecycle, and that existing legal and regulatory requirements continue to apply. It expressly adopts a 'same business, same risks, same rules' approach and requires intermediaries to manage ownership and technology risks.

Germany, France, Switzerland and Luxembourg. Native register statutes solve only the civil-law or recordkeeping side. Issuance, public offering, listing, custody, exchange/MTF/OTF, settlement, licensing and prospectus obligations remain separate and must be mapped to the instrument and transaction.

Design criteria for a legally native tokenized equity architecture

A legally native design must convert token movement into the relevant jurisdiction's legally recognized issuance and transfer event. The common failure mode is building a technically elegant token while the legal register, securities account, or Registrar record remains elsewhere.

• Corporate authorization. Articles, charter, bylaws or board resolutions must authorize uncertificated, electronic, ledger-based or dematerialized shares where local law requires that authorization.
• Legal register designation. The DLT ledger must be designated as the statutory securities register, securities-account record, issuer account, operator register, Registrar-integrated process, or permitted sandbox infrastructure.
• Holder identity. Wallet addresses alone are usually insufficient if the law requires names, addresses, shareholder identification, beneficial owner data, or issuer/intermediary declarations.
• Transfer event. The smart-contract transfer must either be the statutory entry/re-registration/inscription or must automatically and reliably cause it. If a manual off-chain update remains authoritative, the token is mirrored rather than native.
• Restrictions and consents. Transfer restrictions, company consents, securities-law selling restrictions, sanctions, legal process, and error-correction mechanics must be enforceable at the register level, not merely noted in marketing materials.
• Register keeper/operator status. The issuer, register-keeper, CSD, account keeper, operator, control agent, custodian, or intermediary must have the role and permissions local law requires.
• Issue reconciliation. Total issued shares, class rights, voting rights, partial-paid status, restrictions, and cancellations must remain reconciled with the legally authorized capital and register state.
• Integrity and continuity. German and French rules expressly require integrity, authenticity, tamper-resistance, owner identification, and/or continuity. Similar controls are required by supervisory risk analysis in Hong Kong, Singapore and sandbox regimes.
• Intermediation disclosure. The legal documents must say whether holders are direct shareholders, account holders, entitlement holders, beneficial owners behind nominees, or holders of contractual/synthetic exposure.
• Migration and failure. The system must provide lawful procedures for register migration, fork handling, loss of keys, unauthorized transfers, court orders, insolvency of a service provider, and conversion back to conventional records.