Suit Up · Asia's institutional desk on tokenisation

This playbook is for the operator inside a bank, asset manager, or new entrant who has been told "we are doing tokenisation" and now has to decide which asset gets tokenised first. The guidance is opinionated. Legal-wrapper readiness in your target jurisdiction is the first filter, secondary-market need is the second, and everything else (capital treatment, distribution match, internal alignment, operational readiness) is downstream of those two. Most institutions sequence wrong because they start from "what is hot" or "what is technically easy", which loses both quarters and political capital.

Decision frame

The wrong framings to avoid before reading any further. "We should tokenise everything" is not a roadmap. Sequencing matters because some asset classes have viable legal wrappers in your jurisdiction and others do not, and shipping the wrong one first burns the new product committee's appetite for the next two attempts. "We should pick whatever is hottest in the market" sounds market-aware but the hot asset class may be hot in a jurisdiction with no comparable legal infrastructure, or hot through a distribution channel you do not own. "We should pick whatever is easiest technically" is the trap that kills the most pilots: technical ease is rarely the binding constraint. Legal wrapper, capital treatment, and distribution match are. "Let's just do an internal pilot and figure it out" is budget waste if the pilot has no path-to-production from day one. If risk, compliance, and legal are not aligned on the production answer before the pilot starts, the pilot is a presentation, not a product.

The right framing is to treat this as a screening problem. Run each candidate asset class through the criteria below in order of how binding they are. Stop at the first one that disqualifies a candidate. The asset class that survives the screen is the one to tokenise first.

The screening framework

The criteria are listed in the order they bind. Do not reorder.

Legal-wrapper readiness in your target jurisdiction. Per Chapter I, Part 3, genuine tokenisation requires the chain entry to be the legally operative record. Some asset classes have that pathway in some jurisdictions and not others. The US has UCC Article 12 in most states from 2024-2025, which gives controllable electronic records a recognisable property characterisation. The UK has the Property (Digital Assets etc) Bill consolidating the Law Commission's third-category recommendation. Singapore has a substantively similar control test through SFA recognition of electronic securities plus trust law overlay. Hong Kong is the least codified of the four major financial-jurisdiction tokenisation venues, with reliance on contractual designation and common-law trust principles. If your jurisdiction's legal infrastructure for the specific asset class is not ready, you are shipping a wrapped derivative, not a tokenised asset, and your legal team will eventually flag that you mis-described the product.

Distribution channel match. Will your existing distribution rail actually move the tokenised version. If you are a private bank and your tokenised product needs DeFi liquidity to work, you have a distribution problem dressed up as a product. If you are a wealth manager with a regulated-fund distribution channel, tokenised MMFs and tokenised funds slot in cleanly because the wrapper is one your distribution already knows how to handle. If you are a sell-side desk and your tokenised product is a bond, you have an existing fixed-income franchise to lean on. The match between the tokenised wrapper and the channel that will actually carry it is non-negotiable.

Secondary market need. Does the asset NEED secondary liquidity to be useful. MMFs are primary-market-only by design (subscribe / redeem against the fund) and a tokenised MMF inherits that profile. The on-chain transferability is a nice-to-have, not the value driver. Bonds need secondary liquidity for any institutional buyer to size into a position. Private credit does not need secondary, but a tokenised wrapper might unlock new collateral use cases that the conventional structure cannot. Decide whether you are trying to ship a primary-market product (MMFs, private credit, project finance) or one where secondary trading is the value driver (bonds, equities, repo). The two require completely different platform choices and operating disciplines, and conflating them is one of the most common pilot-design mistakes.

Balance-sheet and capital treatment. Basel SCO60 determines whether a tokenised asset is Group 1a (broadly the same capital as the underlying), Group 1b (weaker conditions, higher capital), or Group 2 (sharply higher capital with exposure cap). Group 1a is the gating condition for any bank to hold tokenised assets at viable capital cost, and the targeted review of SCO60 is the principal Basel-side process to track for any horizon longer than six months. If you are a bank, Group 1a viability for the asset class in question is a hard prerequisite. If you are an asset manager whose distribution counterparts are banks, the same concern applies one step removed: a tokenised product that the bank custody and balance-sheet stack treats as Group 2 is a product the bank channel cannot economically intermediate.

Internal stakeholder alignment. Compliance, risk, legal, operations, distribution, and the product committee all need to see the same upside. A pilot that risk hates because it bumps into the firm's crypto policy is a pilot that does not ship. A pilot that distribution does not own is a pilot whose results no one will buy. Map every internal stakeholder before naming the asset class, and make sure each can articulate why the chosen asset class is the right first move. If any one of them cannot, pick a different asset class, or rebuild the internal case before naming the asset class publicly.

Operational readiness. Do you have, or can you license, the transfer-agent capability, custody, on-chain accounting, and reconciliation discipline. See Evaluating custody providers and Evaluating issuance platforms (sister playbooks; cross-link freely). The operational stack tends to be solvable through partnerships (Securitize for transfer agency, Anchorage or comparable for custody, established issuance platforms for the on-chain wrapper) but the partnership choices need to match the asset class. A platform optimised for tokenised funds is not the same platform you would pick for a tokenised bond programme, and a custody provider strong on tokenised cash is not necessarily the right counterparty for tokenised private credit.

Asset-class scorecards

One short read on the current readiness of each major asset class, with the worked example.

Tokenised MMFs. High readiness in the US (BUIDL via BlackRock + Securitize, FOBXX via Franklin Templeton, OUSG via Ondo Finance) and in Singapore through Project Guardian's asset-and-wealth workstream. The cleanest first asset class for an asset manager because the legal wrapper (3(c)(7) qualified-purchaser for the US examples, VCC or unit-trust for Singapore) is well understood, the distribution rail (private-bank wealth, qualified-investor channels, treasury-management for corporates) is already buying tokenised MMFs from US issuers, and the secondary-market need is structurally low. The reference architecture is mapped in BUIDL as reference architecture.

Tokenised bonds. High readiness in Hong Kong (HSBC Orion, the HKSAR multi-currency green bond series including the 2025 USD 1.3bn-equivalent issuance), the UK (the DIGIT pilot mandated to HSBC Orion in December 2025, the first G7 sovereign digital-bond programme of its scale), and Singapore (the Project Guardian Fixed Income workstream and the November 2025 ICMA addendum on tokenised-bond DvP and custody). Strong fit for sovereign, supranational, and FI issuers needing primary issuance with secondary trading, and for sell-side desks whose existing fixed-income franchise can absorb the tokenised wrapper. The worked example to read first is HSBC Orion + DIGIT.

Tokenised private credit. High readiness in the EU and US via SPV-plus-tokenisation patterns. Centrifuge is the worked-example platform; Janus Henderson's JAAA, Apollo's ACRED, and the broader Securitize-issued mandate set are the live products. Good fit for asset managers with credit franchises and an appetite for DeFi-curious institutional distribution. The composability story (Aave Horizon's institutional-DeFi RWA work in particular) is layering venue-level KYC on top of the existing fund wrappers, which is the partial-resolution pattern tracked in the institutional composability paradox page.

Tokenised deposits. High readiness for the BANK ITSELF as issuer (JPMorgan Kinexys / JPMD, DBS Token Services, Wells Fargo Digital Cash, Standard Chartered + Ant International Whale rail going live with HKD, CNH, USD, SGD in December 2025). Not for asset managers; you cannot issue a deposit liability without a bank charter. The right answer for a bank looking at "tokenised cash" use cases, particularly where the cash leg is the binding constraint on tokenised-asset settlement (tokenised-bond DvP, tokenised-FX-swap settlement, intercompany treasury netting). The category page is Tokenised deposits, defined.

Tokenised equities. Low readiness. Most jurisdictions have not changed company law to recognise on-chain share registers as the operative ownership record, which has pushed the live programmes (Robinhood EU's wrapped equities, Ondo Global Markets) into a derivative-reference structure where the on-chain instrument is a contractual claim referencing the underlying equity, not the equity itself. Fine if your reader's product is the wrapper itself and the wrapper distribution is the value proposition. Not fine if the brief is true legal-record-on-chain. The asset-class regulatory treatment page tracks the legal-control gap by jurisdiction.

Tokenised real-estate beneficial interests. Moderate readiness, sharply jurisdictional. Japan has the Progmat ST trust-route under FIEA, which is the most-developed live framework for tokenised beneficial interests in real estate (Progmat architecture). Most other jurisdictions lack the legal structure for the on-chain entry to be the operative beneficial-interest record, which sends the wrapper back into derivative-reference territory. Fine for a Japan-domiciled product with a Japanese distribution channel; harder elsewhere.

Tokenised commodities. Moderate. Gold tokenisation has well-trodden patterns (PAXG and the broader physical-gold-backed token category, HSBC's tokenised gold programme). Most other commodities sit in wrapper-only or warehouse-receipt-bridge territory, with the operative legal record still off-chain. Acceptable as a niche programme, not strong as a first move for a generalist institution.

Worked example

A Singapore-domiciled asset manager has both an MMF franchise (institutional cash management for corporate treasury and private-bank distribution) and a private-credit franchise (Asia direct lending, mid-market). The product committee asks which to tokenise first.

Run the screen on the MMF.

Legal wrapper. Singapore has a workable VCC and unit-trust regime for the on-chain fund interest. MAS Project Guardian asset-and-wealth workstream has been running comparable patterns for two years. Pass.
Distribution. Existing private-bank wealth channel is already buying tokenised MMFs from US issuers (BUIDL via Standard Chartered participation, FOBXX via various distributor relationships). Pass.
Secondary market need. MMF is primary-market by structure. The tokenised wrapper does not need to deliver secondary liquidity to be useful. Pass.
Capital treatment. Tokenised MMF holdings on a bank-counterparty balance sheet route through the underlying fund's capital treatment, with SCO60 Group 1a viability the operating discipline. Achievable.
Internal alignment. Risk, compliance, and legal are familiar with the underlying fund regulatory perimeter; the tokenisation-specific delta is the on-chain wrapper and the transfer-agent integration. Manageable.
Operational readiness. Achievable in 6-9 months by partnering with an established platform plus transfer-agent counterparty. Pass.

Run the screen on the private credit franchise.

Legal wrapper. Workable through Cayman or Singapore-domiciled SPV structure, but requires SPV restructuring of the existing fund, which is a multi-quarter project before any tokenisation work begins.
Distribution. The existing private-credit distribution is institutional LP relationships rather than a tokenisation-ready channel. The DeFi-curious institutional channel (Aave Horizon-style venue-KYC arrangements) is a different distribution play that the firm does not currently operate.
Secondary market need. Private credit does not need secondary liquidity, but the value of the tokenisation wrapper for this asset class is collateral mobility, which requires the venue integrations the firm does not yet have.
Operational readiness. Higher complexity (SPV restructuring, reconciliation discipline against the underlying credit cadence, integration with non-traditional distribution) than the MMF path.

Recommendation: tokenise the MMF first. The wrapper is ready, the distribution channel is matched, the secondary-market need is low, the capital treatment is clean, and the path to production is 6-9 months. Defer the private-credit tokenisation to phase 2 because the operational lift is materially higher and the distribution play is different (DeFi-curious institutional rather than the existing wealth distribution). The phase 2 work can begin in parallel as an architecture exercise; it should not be the firm's first shipping tokenisation product.

Red flags

Chasing tokenisation for marketing reasons. The press release is the deliverable, not the product. Fine for a stock-pump narrative; bad for a product strategy. The institutions that ship are the ones that treat the press release as a by-product.
Picking an asset class with no secondary-market need then over-engineering for liquidity that will not arrive. A tokenised MMF does not need a secondary market; building one and waiting for institutional volume to show up is months of platform time wasted.
Ignoring the legal-wrapper question and shipping a derivative-reference structure while calling it tokenised. Your legal team will eventually flag this. Better to flag it yourself, decide whether the derivative structure is the right product anyway, and brand it accordingly.
Going public-chain when your distribution is private-bank-only. The on-chain composability is wasted because no permissionless protocol will ever touch the whitelisted token. A permissioned ledger gives you the same auditability with fewer compliance questions and a smaller surface area for the new product committee.
Tokenising your weakest product first because it is "low-stakes". The weak product gets tokenised, fails on its own merits, gets blamed on tokenisation, and kills the broader programme. The right pilot is a strong product where tokenisation adds a measurable benefit, not a weak product where tokenisation is being blamed for the underlying.

[Suit Up]

What to tokenise first: an asset-class screening playbook