Practical guide

Tokenised sukuk and smart contracts: technology versus rights

Code can help record holders, check transfer conditions and carry out payments. It cannot, by itself, establish what you own, who owes you money or what you can recover after a default. Read the sukuk documents and the digital system’s rules together.

G29 · Local educational explanation • checked 6 October 2026

Educational guide, checked 6 October 2026. The diagrams below are newly authored conceptual models, not the actual Danum pilot workflow or an available retail offer. No return, liquidity, eligibility or Shariah approval follows merely from tokenisation.

Start with the claim behind the token

A sukuk is a capital market instrument, not simply a crypto coin. In the SC retail guidelines, sukuk certificates evidence undivided ownership or investment in assets through endorsed Shariah principles. The precise asset interest, payment claim and recourse still need the issue documents. A token balance is not enough to conclude that you personally hold registered title to a building or can take it over.

Tokenisation places a digital representation on a programmable platform. A smart contract is code that executes defined conditions. Ask two separate questions: “What rights do the documents give me?” and “How does this system record or exercise them?” The SC FAQ says the fundamental characteristics must be retained; changed rights can change legal classification. Tokenised capital market products and the digital assets regulated under the separate digital-asset framework are distinct.

Sources: SC retail bonds and sukuk guidelines · SC tokenised-product FAQ · BIS tokenisation research

Figure 1. The sukuk structure and the digital register

Conceptual agency model • no quoted rate or launched retail product

Legal and economic layer — documents define the rights

  1. Investors → subscription moneyPay the issuer under the issue terms.
  2. Issuer / appointed investment agent → portfolioInvests under the agreed mandate; identify assets, custody and obligations.
  3. Portfolio proceeds → distributions / maturityPayments and realisation/redemption follow the documents; no automatic full recovery.

Reconcile the record with the documented entitlement

Digital layer — linked records and execution

  1. Holder registerIdentity and units recorded; legal authority must be established.
  2. Token / signing accessRecords and controls a permitted transfer; is not a property-title deed.
  3. Code / payment instructionUses valid inputs and funded settlement route; cannot create missing cash.
New teaching diagram informed by SC definitions, the tokenised-product FAQ and BIS Bulletin 72 (11 April 2023). The two layers describe different functions. Actual custody, asset title, default recourse and payment design require issue documents.

Sources: SC retail bonds and sukuk guidelines · SC tokenised-product FAQ · BIS tokenisation research

Full text alternative: Subscription money moves from investors to issuer/agent and into the agreed portfolio. Portfolio proceeds support payments under the documents. A linked register, token-access system and code record and execute defined events. Neither a token record nor control of a key establishes direct property title or guarantees payment.

What the Malaysian pilot actually establishes

On 28 April 2026, the SC and Khazanah announced successful pricing of a RM100 million tokenised sukuk pilot. The release identifies a one-year inaugural tranche within the Sukuk Danum Programme, an Islamic medium-term notes programme of up to RM20 billion, structured on wakalah bi al-istithmar (investment agency). It names institutional participants, including CGC, KWAP and OCBC Malaysia, and describes testing of operational and technical workflows.

That is evidence of a real pilot, beyond a proposed diagram. The checked announcement is not a retail prospectus: it does not establish a minimum purchase amount, retail eligibility, customer fees, secondary-market buyers or an individual holder’s legal recourse. We do not turn its “24/7 access to information” into a promise of 24/7 trading or immediate cash withdrawal.

BNM’s separate DAIH register, updated 30 July 2026, includes tokenised-deposit initiatives. Its FAQ says admission does not guarantee regulatory recognition and live launch requires further assessment. These entries do not identify the Danum pilot’s actual settlement asset. Do not combine separate initiatives into a retail product that no checked original offers.

Sources: SC–Khazanah pilot release, 28 April 2026 · BNM DAIH initiative register

Trace money, rights and obligations separately

Imagine Aina in Selangor reading about a fictional agency-based sukuk. Investors provide subscription money; the appointed agent invests in the agreed portfolio; realised proceeds fund distributions according to the documents. At maturity, the documented realisation, redemption and payment obligations determine what is due. This is a teaching sequence, not evidence of any named issuer’s execution.

The useful ownership question is more precise than “Is it asset-backed?” Identify the issuer, agent, assets or investment, trustee where applicable, and the party legally obliged to pay. Find the clauses governing asset interests, security, ranking, shortfalls and enforcement. A custodian holding a token or controlling a signing key need not be the person holding legal title to the underlying asset. Ask how the records are reconciled if a wallet record and the authoritative holder register disagree.

The SC retail framework contains trustee/documentation requirements; the trust-deed guidelines address payment covenants, default, trustee powers and meetings within their scope, with exemptions and special provisions. These are reasons to examine the actual deed, not a promise that every sukuk has identical security or recovery rights. A code audit cannot replace those documents.

Sources: SC Islamic capital market guidelines · SC retail bonds and sukuk guidelines · SC trust-deed guidelines · SC tokenised-product FAQ

What code can do — and its conditions

A digital workflow can be designed to create token records, restrict transfers to permitted holders, coordinate payment with transfer, calculate an agreed distribution and retire tokens after redemption. Each step depends on valid permissions, correct data and available money. Figure 2 shows possible automation, not features demonstrated in the Malaysian pilot.

For example, delivery-versus-payment means the final transfer of securities occurs if and only if the corresponding final payment occurs; neither side should settle alone. A design can aim to execute both together, but first establish the settlement asset, legal finality and connection to any bank system outside the platform. Updating a token record is not the same as confirming that the right recipient received ringgit. A successful code run also cannot make an issuer with insufficient funds pay in full.

Sources: BIS tokenisation research · BIS/CPMI governance report · CPMI–IOSCO settlement principle 12

Figure 2. What code can automate

Possible workflow • not demonstrated features of Danum

  1. Issuance recordCreate records after authorised documents and permissions.
  2. Allowed holder / transferApply programmed restrictions using verified identity inputs.
  3. SettlementFinal security transfer if and only if final payment occurs, where the systems and legal finality support that design.
  4. DistributionCalculate an agreed amount and instruct payment only with correct data and funds.
  5. RedemptionRecord redemption and retire tokens after the documented process.
Conceptual lifecycle, based on BIS tokenisation research (2023) and BIS/CPMI governance overview (21 October 2024). Code carries out defined conditions; it does not decide their legal validity or supply issuer funds. Read top to bottom. Settlement conditionality follows CPMI–IOSCO Principle 12 (principles published 16 April 2012).

Sources: BIS tokenisation research · BIS/CPMI governance report · CPMI–IOSCO settlement principle 12

Full text alternative: Read in order: authorised issuance records; permitted-holder and transfer checks; supported settlement where final security transfer occurs if and only if final payment occurs; funded distributions; documented redemption and token retirement. Each stage can fail if permissions, inputs or funding are wrong.

Who still has work to do?

The platform operator needs a documented process for incorrect transfers, lost keys, system outages and code changes. Ask who can pause, upgrade or reverse records, what approvals are required, and which record controls the legal claim. An external data feed, sometimes called an oracle, tells code about events outside its own system; someone must verify that input rather than treating it as truth merely because it reached the blockchain.

The issuer and appointed parties remain responsible for the underlying business and records. A trustee’s role, where appointed, comes from the law and deed; software does not automatically perform a meeting, investigate a default or obtain a court remedy. Risk management must also cover custodians, platform providers and connections between systems. The FSI summary concerns tokenised financial assets; it does not certify crypto yield products.

Sources: SC tokenised-product FAQ · SC trust-deed guidelines · BIS/CPMI governance report · FSI tokenisation-risk summary

Figure 3. Where automation still depends on people

Dependency map • simultaneous responsibilities, not a chronological sequence

  • Issuer / agentUnderlying investment, available cash and accurate reports.
  • Trustee / custodian where appointedDocumented holder rights, custody records and default response.
  • Data and code operatorsVerified external events, audit scope, change approval and recovery process.
  • Shariah / legal review and dispute routeActual structure and amendments, enforceability and remedies.
Editorial dependency map grounded in SC FAQ, trust-deed framework and BIS/CPMI governance. FSI’s 28 August 2025 summary addresses financial-asset tokenisation and excludes cryptoassets/CBDCs. No trustee, code audit or religious endorsement for a named product is authenticated by this map.

Sources: SC tokenised-product FAQ · SC trust-deed guidelines · BIS/CPMI governance report · FSI tokenisation-risk summary

Full text alternative: Four dependencies remain: issuer/agent supplies business performance and cash; trustee/custodian performs documented roles where appointed; data/code operators verify inputs and manage changes; Shariah/legal and dispute processes assess structure and enforce rights. No branch guarantees liquidity, access or approval.

Costs, exit and participation

Aina should ask for one complete cost schedule: any subscription or brokerage charge, custody/platform charge, transfer/network cost, spread on an early sale and taxes that apply to the actual transaction. Ask which costs reduce distributions and which are billed separately. The checked pilot release does not give customer charges or a retail minimum; we supply neither a guessed fee nor an invented return.

Liquidity means finding a permitted buyer at an acceptable price. Smaller token units may be technically possible, but an allowed transfer, venue, custody route and willing counterparty still matter. A maturity payment and an early sale are different exits. Tokenisation does not turn a term instrument into an on-demand deposit.

The Islamic structure does not itself make an offer exclusive to Muslim investors. For Muslim and non-Muslim readers alike, confirm the offer’s actual permitted investor category, identity checks, minimum holding and geographic restrictions. For a Muslim reader’s Shariah assessment, check the named structure, proceeds, rights, pronouncement and subsequent changes. The SC’s ringgit-sukuk rules require documented Shariah reasoning and address revisions with Shariah implications; the word “token” supplies none of that evidence.

Sources: SC–Khazanah pilot release, 28 April 2026 · SC tokenised-product FAQ · SC Islamic capital market guidelines

Six questions that reveal the real arrangement

If an advertisement stops at “blockchain + sukuk”, the information is incomplete. Use these questions to request documents and explanations, not to infer personal eligibility or a Shariah verdict.

  • Who issues the sukuk, who invests or uses the funds, and who must pay?
  • What asset interest or payment right does each unit represent, and which deed or terms creates it?
  • Which register is authoritative, who holds legal title, and who controls the signing keys?
  • What settles the cash leg, and what happens after a failed transfer or lost key?
  • Who may buy, what are all charges, and is early exit a sale rather than redemption?
  • What exact Shariah pronouncement and dispute/default process cover this version?

Sources: SC tokenised-product FAQ · SC Islamic capital market guidelines · SC trust-deed guidelines

References

Dates below distinguish publication, printed revision/effectiveness and access. The source titles identify the originals; all diagrams and reader explanations are new editorial work. Original documents are linked externally. No PDF is hosted here.

Search

Search guides, glossary entries, research and publications in English.