Tokenized securities are blockchain-based tokens that represent legal ownership rights in traditional assets such as equities, bonds, real estate, and fund shares. By moving ownership records on-chain, they enable faster settlement, fractional ownership, improved capital efficiency, and more automated compliance processes.
Institutional adoption is now moving beyond pilot programmes into operational deployment. Organisations such as BlackRock, JPMorgan, and Franklin Templeton have launched tokenisation initiatives to modernise the issuance, transfer, and settlement of assets.
The challenge is no longer whether tokenisation works. It is whether the operational infrastructure surrounding custody, settlement, and compliance is mature enough to support institutional capital at scale. In this guide, we examine the infrastructure requirements that determine how tokenized securities move from experimentation to mainstream adoption.
What are tokenized securities?
A security token is a blockchain-native token that represents legal ownership rights in an underlying asset: a stock, bond, real estate interest, or private fund share. The token itself is not the security. It is a digital instrument that proves and transfers ownership on-chain, while the underlying asset remains in legal custody off-chain. When the token moves on the blockchain, ownership transfers atomically and instantly, without the intermediaries required by traditional settlement.
Security tokens span every major institutional asset class: public equities enabling fractional share ownership, corporate and government bonds, real estate fractional interests in individual properties or portfolios, and private fund shares converting illiquid LP positions into transferable tokens. Each asset class carries its own legal structuring requirements and regulatory pathway.
Security tokens differ from traditional securities in operational execution, not in ownership rights. Traditional securities settle through clearinghouses that take days and require multiple intermediaries. Security tokens settle in minutes, eliminating intermediaries, and transfer ownership without external confirmation. Both types carry identical ownership rights and regulatory obligations.
The operational advantages over traditional securities are concrete: fractional ownership at any denomination not constrained by minimum lot sizes, instant liquidity through atomic settlement rather than T+2 delays, programmable compliance with transfer restrictions and accreditation checks embedded in the token logic itself, and 24/7 transferability without geographic barriers. Each of these directly reduces the cost and operational overhead of running institutional securities operations.
How Tokenization of Securities Works?
Tokenisation is not a single process. It is a series of decisions starting with asset selection and ending with operational infrastructure that manages the token throughout its lifecycle.
Asset selection is the first constraint. An asset must have clear legal ownership structures, defined rights that survive transfer, and an established regulatory pathway in the target jurisdiction. REITs and private equity fund shares are natural candidates because their legal structures are well-established and their economic rights are clearly defined. Assets without regulatory clarity or ambiguous ownership structures require legal work before tokenisation is viable. Minimum scale matters: tokenisation infrastructure has fixed operational costs, so the asset must be large enough that the efficiency gains justify them, or must solve a specific problem like enabling fractional ownership of assets otherwise priced out of reach.
Legal structuring defines the relationship between the token and the underlying asset: which entity holds legal custody of the asset, how token transfers constitute ownership transfers under applicable law, what rights token holders can enforce, and how the structure operates across multiple jurisdictions when issuers and investors are in different regulatory regimes. This is the most jurisdiction-specific stage. This is the most jurisdiction-specific stage. A structure that is compliant in Singapore may still require material adjustments to satisfy MiCA requirements in the European Union, VARA regulations in the UAE, or SEC requirements in the United States.
Blockchain selection involves a direct tradeoff between compliance control and market accessibility. Permissioned networks such as Hyperledger Fabric, R3 Corda, and JPMorgan’s Onyx offer institutional-grade access controls and compliance enforcement but limit the investor base to participants on that network. Public or semi-public networks such as Ethereum, Polygon, and TRON provide broader accessibility and secondary market liquidity but require more sophisticated on-chain compliance automation to enforce transfer restrictions and investor accreditation. Most institutional tokenisation programs currently use permissioned or semi-permissioned networks, with hybrid approaches emerging as cross-chain infrastructure matures.
Investor onboarding embeds compliance directly into token transfer logic. KYC, AML, and accredited investor verification are completed before any token is issued to an investor, and the results are tied to wallet addresses in the smart contract. When a secondary transfer is attempted, the contract checks both the sender and receiver against the verified whitelist. The token cannot move to an unverified wallet. This shifts compliance enforcement from manual legal review per transaction to automated on-chain execution, reducing per-transaction cost and eliminating human error as a compliance risk.
Post-issuance lifecycle management is where programmable securities most clearly demonstrate their operational advantage. Dividend distributions, interest payments, stock splits, and maturity redemptions all execute automatically via smart contracts, eliminating the risk of manual processing or administrative errors. Secondary trades settle atomically on-chain: payment and token transfer occur in a single transaction, eliminating the counterparty risk window associated with T+2 settlement. Custodians like Liminal maintain audit logs connecting every on-chain event to the governance policy that authorised it, which is the record-keeping standard regulators expect.
Why is custody infrastructure important for tokenized securities?
Institutional adoption of tokenized securities depends entirely on a custody infrastructure capable of securing digital ownership, enforcing governance, properly segregating assets, and enabling regulatory compliance. This is not an add-on. It is the foundational constraint.
Any custody framework that cannot meet these requirements simultaneously is unlikely to support institutionally tokenized securities operations at scale.
Safeguarding Digital Ownership. A security token is only as secure as the private key controlling it. In traditional custody, the custodian manages access to the asset, and liability is well defined. With security tokens, whoever controls the private key controls the asset, and there is no reversal mechanism if that key is compromised or lost. This is a categorical security difference that rules out consumer-grade key management entirely. Institutional custody requires cryptographic key storage on hardware security modules or MPC frameworks, air-gapped systems isolated from internet-connected infrastructure, multi-party control so no single person can unilaterally authorise a transfer, and backup protocols that prevent key loss without creating new access vulnerabilities.
Institutional custody for security tokens uses three complementary security architectures. Multi-signature wallets require M-of-N approvals before any transaction executes, so compromising a single key is insufficient to move funds. Hardware security modules store key material in tamper-resistant hardware, physically isolated from networked systems. MPC frameworks, used by Liminal Custody, go further: key material is never assembled in one place. Cryptographic computation is distributed across multiple parties and locations, so there is no moment at which a complete key exists to be stolen. Each approach addresses a different attack vector; institutional-grade custody uses all three in combination.
Emergency access procedures are a custody requirement that is frequently overlooked during vendor selection. If a key shard is compromised, the custody infrastructure must enable rapid asset migration to new keys without requiring the compromised key holder’s cooperation, without creating a window during which asset control is ambiguous, and without breaking the audit trail that regulators require. Custody providers that cannot demonstrate tested emergency recovery procedures represent an operational risk that regulators increasingly scrutinise.
Governance and Access Control: An institution managing security tokens for multiple clients requires granular control over who can authorise transactions and under what conditions. Governance requirements vary by role, token type, and transaction context: a CFO authorising large outbound transfers, a compliance officer approving transfers to new counterparties, a risk manager enforcing daily volume limits, and automated rules blocking transfers outside approved hours or geographies. These workflows cannot be hardcoded at deployment. They must be configurable without on-chain transactions, auditable at every change, and enforceable at the infrastructure layer rather than relying on procedural compliance.
Operational governance for custody means role-based permissions that vary by token, by transaction type, and by circumstances. A wallet infrastructure that enforces only multi-signature approvals is insufficient. Governance must be policy-driven, updated without requiring new smart contracts or blockchain transactions, and auditable so compliance teams can verify that approvals were made in accordance with policy.
Liminal’s policy engine enforces governance at the infrastructure layer, allowing policy changes to take effect immediately without requiring on-chain transactions or development work. This flexibility helps institutions adapt to evolving regulatory requirements, internal governance standards, and client mandates.
Institutional governance requirements for tokenized securities custody include approval hierarchies with configurable thresholds per transaction type, role-based limits on transaction size and frequency, geographic restrictions on which approvers can authorise which transactions, time-based controls allowing approvals only during designated windows, and full audit trails recording approver identity, timestamp, and policy basis for every transaction.
Asset Segregation and Risk Management: Traditional custody segregates client assets from the custodian’s operational assets so that if the custodian fails, client assets are protected. Digital asset custody must do the same, but segregation happens at the wallet and key level. In practice this means each client operates in an isolated wallet structure with dedicated keys, separate governance policies, and no shared infrastructure at the signing layer. A compromise affecting one client’s key material cannot propagate to another client’s custody environment. That guarantee depends on architectural isolation, not procedural controls.
Managing segregated custody at scale requires a wallet architecture that is both isolated and operationally unified. An institutional custodian serving hundreds of clients must maintain separate key material and governance policies per client, while providing a single operational interface for monitoring, compliance reporting, and incident response. Systems that achieve isolation through operational silos, meaning separate instances and manual coordination between clients, fail at scale. Liminal’s architecture enforces per-client isolation at the key and policy layer while providing centralised monitoring and audit reporting across the entire custody operation.
Compliance and Auditability. Regulators reviewing tokenized securities custody require complete audit trails. Every transaction, minting, transfer, approval, and rejection must be recorded with timestamps, approver identities, and the basis for authorisation, not just the blockchain transaction hash, but also the institutional policy context that governed the decision. If a regulator questions whether a transfer was authorised correctly, the audit trail must provide clear evidence that it complied with established governance controls.
Blockchain transactions are immutable, which supports this requirement. Every transfer is recorded on-chain with signatures proving who authorised it. However, blockchain audit trails alone are insufficient. Regulators also want to understand why a transfer was approved or denied according to institutional policy. This requires a custody infrastructure that records policy decisions alongside blockchain transactions. Liminal Custody maintains detailed audit logs that connect every transaction to the policy framework that governed it, the approvers involved, and the basis for approval. These records can be exported in formats that support regulatory reporting and audit requirements across key digital asset jurisdictions, including Singapore (MAS), the UAE (VARA), and the European Union (MiCA).
Cybersecurity in Tokenized Infrastructure: Tokenized securities custody faces three primary attack vectors, each requiring distinct mitigation measures.
Key compromise through theft, social engineering, or physical access to key material is the highest-consequence risk because it directly enables asset theft. MPC architecture mitigates this by ensuring that no complete key ever exists in a single location. An attacker must compromise multiple independent parties simultaneously. Liminal’s MPC framework distributes key shards across geographically separated infrastructure, making coordinated compromise operationally implausible.
A transaction authorisation system compromise involves gaining access to the interfaces that approve and execute transfers, potentially bypassing key security controls entirely if the approval system is vulnerable. Liminal enforces least-privilege access to all approval interfaces, monitors for anomalous access patterns, and triggers automatic containment on unauthorised access attempts.
Infrastructure cross-contamination occurs when a breach in one system, such as trading infrastructure or client data systems, propagates into custody infrastructure. Liminal’s custody infrastructure operates in isolated environments with no direct connectivity to trading systems, client management platforms, or external data services.
Institutional Custody Providers: Building institutional-grade tokenized securities custody in-house requires cryptographic engineering, regulatory compliance expertise across multiple jurisdictions, operational governance architecture, and 24/7 security operations. This combination is both expensive and slow to achieve at a production scale. For most institutions, the build-versus-buy calculation resolves clearly in favour of a specialist custody provider.
Liminal Custody is purpose-built for institutional digital asset custody, with specific depth in tokenized securities infrastructure. The platform provides governance-focused wallet infrastructure with configurable role-based permissions, multi-signature and MPC-based key management, policy-driven transaction controls enforced at the infrastructure layer, and multi-client asset segregation at scale. ISO 27001, ISO 27701, and SOC 2 Type 2 certifications meet the security standards institutions require before committing significant capital. Liminal operates across APAC and MENA, with offices in Singapore, India, the UAE, and Taiwan, covering the primary institutional tokenisation markets.
Operational controls enforce asset segregation, maintain audit trails, and support compliance automation. This is the type of infrastructure institutions require before moving significant tokenized securities positions into production.
Settlement Infrastructure for tokenized securities
Traditional securities settlement takes two days (T+2). A trade happens on Monday, and settlement occurs on Wednesday. Between trade and settlement, counterparty risk exists. Settlement delays also mean institutions cannot use capital that is in settlement. If $100 million settles on Wednesday, that capital is unavailable until then, creating working-capital inefficiencies that scale across millions of trades.
Security tokens settle atomically on-chain: the ownership transfer is cryptographically final the moment the transaction is confirmed, typically within seconds. Both parties see the ownership change simultaneously, with no reconciliation required. There is no settlement delay, no counterparty risk window, and no capital locked in a pending settlement state.
Blockchain settlement enables native delivery-versus-payment (DvP): a smart contract holds both the token and the payment in escrow, and releases both simultaneously only when both conditions are met. This is DvP at the protocol layer, not enforced by a central clearinghouse. Settlement risk is eliminated structurally, not managed through counterparty agreements.
Instant Settlement Eliminates Reconciliation Overhead
Traditional settlement generates end-of-day reconciliation work: matching positions across custodians, processing confirmations, and investigating discrepancies that arise from T+2 delays. Blockchain settlement eliminates this entirely. Every transaction is confirmed on-chain in real time, positions are continuously accurate, and there are no end-of-day discrepancies to investigate. For institutions with high transaction volumes, eliminating reconciliation is a meaningful reduction in operational costs.
Regulatory and Compliance Considerations
Tokenized securities remain subject to the same regulatory requirements as traditional securities. Investor protection rules, licensing obligations, and compliance frameworks apply regardless of whether the security is traditional or tokenized. The operational implementation changes, but the regulatory obligation does not.
The SEC treats security tokens as securities subject to Securities Act and Exchange Act requirements. MiCA in Europe imposes requirements on token issuers and trading venues. Singapore’s Monetary Authority has approved tokenisation pilots and created compliant pathways. Hong Kong’s Securities and Futures Commission is developing tokenized securities frameworks. In the UAE, the Virtual Assets Regulatory Authority (VARA) is developing regulatory frameworks for digital assets and tokenized financial products.
Global regulatory development is converging on key requirements. Tokenized securities must be registered or exempted from registration under securities laws. Token issuers must disclose material information about the underlying asset. Trading venues must be licensed or regulated. Custody must meet institutional standards. Investor protection requirements must be embedded into the token or enforced by intermediaries. Institutions evaluating custody providers should verify that their provider maintains active engagement with regulators across its operating jurisdictions. Beyond compliance, established regulatory relationships can help reduce operational uncertainty as tokenisation frameworks continue to evolve.
Institutional market participation drives regulatory clarity. When JPMorgan issues a tokenized bond or Franklin Templeton launches a tokenized fund, the regulatory framework tightens around what works at scale. Regulators see real institutional use cases and clarify requirements based on operational reality. The DLT Pilot Regime in the European Union and similar regulatory sandboxes explicitly allow institutions to operate tokenisation projects under regulatory oversight, creating pathways for institutional deployment while regulators understand real-world implications.
Challenges limiting the adoption of tokenized securities
Despite regulatory clarity and institutional interest, the adoption of tokenized securities faces real obstacles.
Regulatory fragmentation remains a significant friction. A tokenized bond issued in Singapore might be structured one way. The same bond issued in the EU must be structured differently under MiCA. An issuer managing tokenized securities in multiple jurisdictions must maintain separate legal structures and compliance workflows. This adds cost and complexity. Custody providers operating across jurisdictions, such as Liminal, can reduce operational overhead by supporting compliance, governance, and reporting requirements across multiple regulatory environments. This allows institutions to accelerate deployment without having to build every operational framework from the ground up.
Infrastructure interoperability creates operational challenges. If a security token is issued on a permissioned blockchain, an investor cannot trade it on a different blockchain. Cross-chain bridges exist, but they introduce new risks and operational complexity. Institutions managing multiple tokenized positions across different blockchains must coordinate custody, settlement, and compliance across separate infrastructures, increasing operational overhead.
Custody infrastructure is still maturing. Not every institution has access to institutional-grade custody for tokenized securities. Building in-house custody is expensive and requires specialised expertise. The custody provider market is growing, but the gap between institutional-grade specialist providers and general-purpose digital asset custodians is significant. Selection criteria should prioritise tokenized securities-specific governance capabilities over general custody scale.
Smart contract risks are real. Code executes as written, not as intended. A bug in a smart contract governing dividend distributions could cause payments to fail or route payments incorrectly. Testing and auditing are necessary, but cannot eliminate all risks. Institutions must account for smart contract execution risk when moving significant capital into tokenized positions.
Institutional custody providers such as Liminal use smart contracts developed and audited to institutional standards, with formal verification where applicable, and maintain contractual liability frameworks that general-purpose custody providers may not offer.
Institutional hesitancy persists. Even when regulatory frameworks are clear and custody infrastructure exists, institutions move deliberately. Moving capital into new infrastructure requires board approval, risk assessment, operational testing, and regulatory coordination. This process takes time, and many institutions are waiting to see if tokenized securities become truly mainstream before committing resources.
Liquidity concerns remain. A tokenized security is only useful if investors can buy and sell it readily. Early tokenized securities have limited investor bases and thin trading volumes. As more issuers tokenise and more investors gain custody access, liquidity will improve. But for now, many tokenized securities trade infrequently, which deters institutions from allocating significant capital.
Institutions that move early into tokenized securities infrastructure position themselves to capture liquidity as secondary markets develop, rather than entering a mature market at commodity pricing.
The future of tokenized securities infrastructure
Institutional adoption of tokenized securities will accelerate as infrastructure matures. Three trends will shape this evolution.
First, convergence between traditional finance and blockchain infrastructure will deepen. Major financial institutions are building blockchain trading and settlement infrastructure, not because blockchain is novel, but because it is operationally superior to legacy systems.
JPMorgan’s blockchain payments platform and similar efforts are normalising blockchain infrastructure as an institutional standard rather than a fintech experiment. As traditional finance infrastructure incorporates blockchain settlement, the adoption of tokenized securities follows naturally. SWIFT’s blockchain integration pilots and the Bank of International Settlements’ Project mBridge signal that even the most conservative financial infrastructure is moving toward blockchain settlement. The timeline for institutional tokenisation is no longer speculative.
Second, real-world assets tokenisation will expand far beyond securities. Tokenized commodities, tokenized trade finance instruments, and tokenized derivatives are all emerging. As asset classes expand, institutional demand for custody and settlement infrastructure grows, driving investment in that infrastructure. This creates a positive feedback loop in which infrastructure maturity enables new asset tokenisation, which in turn drives further investment in infrastructure.
Third, scalable custody and settlement infrastructure specifically designed for institutional tokenisation will become standard. Custody providers will offer tokenized securities management as a core service, alongside traditional asset custody. Trading venues will support tokenized securities as naturally as they support traditional securities. Custody providers that are building this infrastructure now, with institutional governance, multi-jurisdiction compliance, and production-grade security, will be the default providers when the market reaches scale. Institutions that select custody partners based on current capability rather than current market size will have operational advantages as the market matures.
Compliance automation will become embedded rather than bolted on. This will reduce operational friction and institutional friction around tokenisation. Institutions will not need to make a special decision to adopt tokenized securities. They will migrate assets to a more efficient infrastructure.
Why choose Liminal Custody for tokenized securities?
General-purpose digital asset custody is not designed for tokenized securities. It lacks the governance layer, the jurisdiction-specific compliance automation, and the policy infrastructure that institutionally tokenized securities operations require. Liminal Custody is purpose-built for this use case.
Governance at the infrastructure layer. Liminal enforces role-based permissions, multi-signature approvals, and transaction policies at the custody infrastructure level, not as a workflow layer on top of general custody. Policy changes take effect immediately without on-chain transactions or development cycles. This operational requirement eliminates the gap between custody policy and custody execution.
MPC-based key management with no single point of failure. Key material is distributed across multiple parties and geographies. No complete key ever exists in one location. An attacker must simultaneously compromise multiple independent, geographically separated systems to access assets.
Multi-client segregation at scale. Liminal supports hundreds of client custody environments with isolated key material and independent governance policies, managed through a unified operational interface. Isolation is architectural, not procedural.
Jurisdiction-native compliance. Liminal maintains pre-built compliance frameworks for VARA in the UAE and other regulators in its operating footprint. Institutions operating across multiple jurisdictions do not need to build compliance infrastructure from scratch for each market.
Institutional security certification. ISO 27001, ISO 27701, and SOC 2 Type 2 certifications confirm that Liminal’s security controls meet the standards required before institutional capital allocation.
For institutions moving significant tokenized securities positions into production, the custody infrastructure decision is the constraint that determines operational viability. Liminal is built specifically for this constraint.
