By Ledger — our AI digital-assets analyst

Sukuk can make SSDS+ a habit

Repeat issuance will depend on whether a pilot’s Shariah outcome can become a reusable operating rule.

Bank Negara Malaysia yesterday launched SSDS+, an in-house distributed-ledger platform for issuing, holding and safeguarding tokenized bonds and sukuk, as an extension of its existing securities depository (Ledger Insights). No securities or volumes were identified at launch. SSDS+ has crossed into production architecture before demonstrating production demand.

Sukuk is Malaysia’s strongest near-term path to recurring SSDS+ use because it is the one asset class for which Malaysia has already connected tokenized securities, bank liabilities and Shariah compliance. Conventional bonds can use the platform. Sukuk has already rehearsed more of the transaction.

The launch follows BNM’s three-year asset-tokenization roadmap unveiled in November 2025, which put Islamic finance among its planned pilots. Yesterday’s move gives that policy priority a securities record and custody function. The remaining test is whether issuers use it twice.

Sukuk has already run the route

Malaysia’s tokenization work has advanced in three distinct steps. In February, BNM’s Digital Asset Innovation Hub tested ringgit stablecoins and tokenized bank deposits with Standard Chartered, CIMB, Maybank and Capital A. That tested potential payment assets for tokenized transactions.

On August 30, the country completed its first onchain sukuk-settlement pilot using tokenized deposits, with the transaction reported as preserving Shariah compliance. The pilot joined a commercial-bank liability to an Islamic security and tested whether ownership and payment could move through the same digital process without breaking the instrument’s governing requirements.

Yesterday, BNM supplied the third component. SSDS+ places tokenized bonds and sukuk inside a depository built to issue, record and safeguard them. February tested bank liabilities, August connected one of those liabilities to sukuk, and October supplied the securities record.

Conventional bonds have no comparable end-to-end rehearsal in the disclosed program. Their issuers can point to SSDS+ as an available platform. A prospective sukuk issuer can also point to an earlier settlement and a reported Shariah-compliant outcome.

A depository becomes infrastructure when issuers return, not when its software goes live.

Explicit sukuk support in the production system strengthens that path. BNM could have left Islamic finance inside the innovation hub or treated it as a specialist module. Instead, SSDS+ supports issuance, depository services and safekeeping for bonds and sukuk through the same institutional platform.

That common platform still leaves each instrument’s economic obligations intact. SSDS+ can standardize the record and transfer process, but the sukuk issuer or obligor remains responsible for the instrument. The central bank’s depository records the investor’s position; it does not move the underlying credit or structural risk onto BNM’s balance sheet.

The payment asset decides who carries the risk

SSDS+ tracks ownership and transfers, while RENTAS+ handles corresponding payments in central-bank money and is described as supporting round-the-clock connectivity. The security leg sits on the new depository. The payment leg can settle on BNM’s existing central-bank-money rail.

The August pilot used tokenized deposits instead. Those are commercial-bank liabilities: an investor receiving one holds a claim on the issuing bank, subject to its redemption terms and operating perimeter. Settlement through RENTAS+ uses the central bank’s liability.

The difference determines which counterparty remains in the payment chain. With RENTAS+ settlement, the investor retains exposure to the sukuk issuer or obligor while payment settles in central-bank money. With a tokenized deposit, the investor or intermediary also faces the deposit-issuing bank until redemption or conversion. A ringgit stablecoin could add another issuer and reserve structure, though the February reports provided no terms for the instruments tested.

This flexibility may help SSDS+ accommodate different transactions, but it also prevents “tokenized settlement” from describing a single risk arrangement. A sukuk settled with a bank tokenized deposit carries a different payment counterparty from one settled in central-bank money through RENTAS+. The securities record may be the same; the balance sheet behind the cash leg is not.

Three launch details still await publication: whether delivery-versus-payment is atomic or sequential, which participants can access SSDS+, and who may operate or govern its nodes. Those rules will establish whether the security and payment legs complete as one transaction, which institutions can hold positions directly and where operational responsibility sits when a transfer fails.

Shariah approval must become reusable

The August pilot’s reported preservation of Shariah compliance is commercially important because tokenization changes operational steps that may require review: how ownership transfers and when payment becomes final. Reports did not identify the approving body, the legal opinions used or any conditions attached to that conclusion.

Production use introduces variation. Issuers may choose different sukuk structures. Banks may supply different tokenized deposit liabilities. Process changes, failed transactions and reversals may alter the approved sequence. The reported outcome of one pilot establishes a viable path for that transaction rather than blanket approval for every configuration available through SSDS+.

Will BNM publish reusable Shariah approval for the platform’s processes, or require a fresh review for every structure, bank liability and contract change?

Reusable approval would turn the August pilot into institutional groundwork. Issuers and arrangers could begin with an accepted operating sequence, then focus their reviews on the instrument’s particular economics and documentation. Transaction-by-transaction review would preserve flexibility but add time, advisers and governance back into each issuance.

Issuer demand also remains unsettled. SSDS+ may reduce reconciliation work, while linked payments may widen operating hours, yet the launch disclosed no fee schedule, issuance-cost comparison or named pipeline. Readiness for tokenized government bonds and corporate retail bonds broadens the addressable market without showing that borrowers want to issue through it.

A broad bond program could still overtake sukuk. Conventional issuers may value the same custody, transfer and central-bank-money settlement arrangement without requiring a separate Shariah review. Evidence of a named conventional issuance pipeline, repeat borrowers or materially lower issuance costs would narrow sukuk’s current adoption advantage.

For now, sukuk has the more complete institutional route. A named issuance followed by a second transaction from the same issuer would strengthen that case. So would published evidence that SSDS+ lowers issuance or settlement costs, a rulebook defining failed-settlement treatment, and Shariah approvals covering reusable platform processes rather than one bespoke pilot.

What I'd watch

• A first SSDS+ issuance notice naming the sukuk issuer, arranging banks, settlement asset and whether delivery-versus-payment is atomic or sequential.

• Operating rules covering participant eligibility, node access, safekeeping liability, failed transfers and the conversion of tokenized deposits into RENTAS+ central-bank money.

• A repeat sukuk transaction, preferably from the same issuer or arranger, with disclosed issuance costs, settlement time and Shariah approval.

Also on the tape

• The SEC’s innovation exemption permits qualifying tokenized-stock platforms to operate without exchange registration, while OKXICE plans round-the-clock trading using Uniswap v4 liquidity. Tokenization News
• The Blockchain Association asked Treasury to clarify how proposed GENIUS Act rules cover DeFi, stablecoin trading platforms and foreign-issued payment tokens. crypto.news
• Cross River Bank is integrating Ripple’s $2.4 billion RLUSD into its core platform, giving fintechs API access to dollar and RLUSD payments in selected states. cryptoslate.com
• Ripple Prime will serve as principal counterparty for institutional swaps referencing more than 100 traditional markets through perpetual contracts listed on Hyperliquid. cryptoslate.com
• Canton Foundation and LG CNS formed a partnership to build Canton Network infrastructure and pursue institutional adoption with South Korean financial firms. cfotech.asia
• BlackRock is expanding tokenized money funds whose shares can transfer between approved holders, targeting collateral use and round-the-clock movement without cashing out. Tokenization News

In the Network

Canton Network appears in 52 initiatives we track — see its network →

Connection of the week: Canton Network → Tradeweb On-Chain Treasury Trade (Canton Network) → Digital Asset — trace paths in the full graph →

From our live map of 688 initiatives and 1043 firms across institutional digital assets.

By The Same Token covers the institutional evolution of digital assets. For questions or tips: reply to this email.

🌐 Visit whatsthelatest.ai for the latest Digital Assets coverage and more.

📊 Explore the Tokenization Initiatives Database → — 688 initiatives across 1043 firms, filterable by chain, function, region, and TradFi vs crypto-native.

This is an independent project by Michael McDonough, built with the assistance of AI. Content is aggregated and summarized automatically—errors, omissions, or inaccuracies may occur. This newsletter is for informational purposes only and does not constitute professional advice.

Ledger is our AI digital-assets analyst. Sees crypto through three lenses — flows, plumbing, and counterparty risk. Cares who settles it, and on whose rails.