Tokenized Security Rights Entitlements

Economic rights: distributions, repayment, and conversion

Economic rights include cash dividends, interest coupons, principal repayment, redemption value, liquidation proceeds, conversion consideration, and distributions in new securities. The security terms define the amount, priority, timing, currency, and conditions. A board declaration, trustee instruction, issuer action, or event documentation may be required before a payment or allocation can be processed.

Administration requires more than identifying a token balance. The responsible party must establish the record date, eligible quantity, fractional-unit treatment, payment account, tax status, withholding instructions, and any restrictions on payment. A direct model can use the issuer or transfer-agent holder file. An intermediated model can move consideration from issuer to depository or custodian and then through customer-account records.

Tokenization can support controlled delivery or the representation of a new position. It does not remove the need for cash-leg evidence, tax reporting, accounting entries, and reconciliation. The programme needs rules for wallet eligibility, failed delivery, sanctions screening, return of funds, and the relationship between a token event and the payment record.

Governance and information rights

Governance rights can include voting, consent solicitation, meeting participation, election of directors, and other corporate decision rights. Information rights can include proxy materials, periodic reports, notices, statements, and disclosures required by the instrument or applicable rules. They are not inherent in every tokenized asset. Their availability follows the security terms and the legal relationship between the issuer and holder.

For a directly registered position, the issuer or its agent can identify the holder from the official record and deliver the relevant process directly. For an intermediated position, the issuer, depository, bank, broker, or custodian follows the chain of records and communication procedures needed to pass materials and instructions to the beneficial holder. The operational result is similar in purpose but different in evidence, timing, and responsible parties.

A wallet signature may be used within a recognised digital voting or instruction process. It must be linked to the eligible holder or authorised representative and accepted by the governing procedure. A protocol-valid signature alone does not establish voting, intermediary, or election authority.

Transfer and control rights

A security holder may have the ability to sell, transfer, pledge, redeem, convert, or otherwise direct a position, subject to the instrument terms and applicable restrictions. These rights are frequently conditional. Private-placement restrictions, holding periods, investor eligibility, jurisdictional limits, lockups, sanctions controls, court orders, and account authority can all affect whether a requested transfer may proceed.

Smart-contract permissioning can check a wallet allowlist or block an address. Such controls are useful when linked to the policy and evidence supporting a restriction. They need processes for additions, removals, manual review, wallet rotation, lost credentials, administrative intervention, and dispute resolution. A code-level rule without the required account and legal context can either reject a permitted transaction or permit one that cannot be serviced correctly.

Transfer completion also needs a clear rule. In one programme, a validated ledger transaction can change the master securityholder file. In another, the ledger event initiates a transfer-agent update. In an intermediated structure, the relevant completion can be a credit to the entitlement holder's securities account. The programme documents should identify the recognised completion point and the handling of in-flight, rejected, reversed, or exceptional events.

Corporate-action rights

Corporate actions are where rights administration becomes most visible. A tender offer, exchange offer, merger, split, spin-off, warrant exercise, conversion, call, rights offering, or consent solicitation requires an institution to determine who is eligible, what they may elect, the deadline, the consideration, and the evidence required to complete the event.

The process begins with an event record and a designated record date or eligibility cut-off. Operations then determine the relevant holder quantity and status, deliver notices, collect and authenticate instructions, calculate allocations, post the resulting cash or security movements, and reconcile the outcome. Different systems can carry different pieces of that process. Token state may support a position snapshot; account and holder records can establish identity, authority, tax, and servicing instructions.

Tokenized architecture needs a clear approach to timing. A blockchain snapshot has a block height and network timestamp. An issuer's record date or an intermediary's cut-off may follow another controlled clock and record. A transfer near the boundary can produce a valid network event while the related issuer, transfer-agent, custody, or entitlement update remains pending. The programme should state which record controls eligibility and how such exceptions are handled.

Servicing and evidentiary rights

Holders and institutions require evidence as well as event outcomes. Depending on the structure, this can include account statements, transaction confirmations, notices, tax reporting, valuation records, audit confirmations, and an accessible history of instructions and corporate actions. The responsible provider needs to retain the records required for its role and provide them through the appropriate holder or account relationship.

A token transaction history can support that evidence, but it is rarely complete on its own. A transaction hash does not necessarily identify the legal holder, the tax character of a payment, an authorised account representative, a corrected allocation, or the legal basis of a restriction. An institutional audit trail links network events with account postings, approvals, notices, record-date determinations, and exception decisions.

This is especially important for omnibus structures. A provider can hold tokens in a single registered or controlled wallet while allocating the position among multiple customers in its internal records. The customer receives rights through that account relationship. The provider must be able to demonstrate the allocation and servicing path without exposing confidential downstream data on a shared ledger.

Rights paths across tokenization models

An issuer-sponsored tokenized security can integrate distributed ledger technology into the issuer's master securityholder file or a connected recordkeeping process. The holder's rights may be administered directly through the issuer or transfer agent, subject to the programme's terms and controls. Onchain and offchain information can be linked, including wallet address, quantity, issue date, legal holder identity, and contact details.

A direct security can also retain an offchain master securityholder file while using a token to initiate or evidence a transfer. In that design, the holder's rights follow the person recorded on the offchain file at the relevant time. The onchain event supports the workflow, while the programme specifies how it becomes an effective update to the holder record.

A tokenized security entitlement is held through a third-party intermediary. The underlying security may remain within custody or depository infrastructure, while the intermediary's entitlement record and tokenization process determine how the customer position is administered. UCC Article 8 defines a security entitlement as the rights and property interest of an entitlement holder with respect to a financial asset. It also establishes duties for a securities intermediary relating to distributions and directed exercise of rights.

A synthetic or linked tokenized security follows its own terms. The product may reference the value or events of another security, but the holder's claim is against the product issuer or counterparty. The SEC staff statement describes linked securities and security-based swaps as structures that can provide synthetic exposure without conveying equity, voting, information, or other rights from the referenced issuer. Product documentation needs to make that boundary clear.

A fact-specific DTC entitlement example

DTC's December 2025 no-action letter describes a preliminary, participant-level tokenization service. The facts presented to SEC staff include tokenized entitlements held in registered wallets, an underlying position moved to DTC's Digital Omnibus Account, and LedgerScan as DTC's official books and records for tokenization entitlements. The underlying securities remain registered in the name of Cede & Co., DTC's nominee.

This structure shows how rights can remain within an intermediated chain while a tokenized entitlement moves among approved participants. The participant's downstream customer servicing remains a separate responsibility from DTC's participant-level records. The letter addresses the stated facts and conditions of the preliminary service. It should not be read as a general rule for every tokenized-security arrangement.

A disciplined rights inventory

A practical rights inventory identifies the security class, legal terms, holding model, authoritative record for each event, record-date rule, wallet and account relationship, restriction controls, instruction channels, payment path, and exception owner. It also identifies conversion steps and controls that prevent duplicate use across rails.

Devancore can map instrument rights, record hierarchies, holder and account relationships, token states, election workflows, distribution evidence, and reconciliation exceptions across traditional, tokenized, and onchain rails. One hybrid core provides an operating layer for institutions to coordinate rights administration without requiring all parties to replace their established records or providers.

Devancore does not establish security terms, act as an issuer, transfer agent, broker-dealer, custodian, depository, or paying agent; determine legal entitlement; or administer a corporate action in place of the responsible party. Those functions remain with the parties designated by the applicable instrument, agreements, and regulatory framework.