This guide uses one made-up example. Farah sells a batch of rice, stored in a warehouse, to Kumar. The example shows what a blockchain record can do and what it cannot do. The guide also explains what Bank Negara Malaysia (BNM) is testing. It does not tell you to use or invest in any blockchain product.
Words used on this page:
- Ledger: a record of transactions, like a bank statement or a shop’s account book.
- Blockchain: a ledger that groups transactions into “blocks” and links each block to the one before it.
- Token: an entry on a blockchain that stands for something, such as a coin, a claim on a company or a right to goods.
- Private key: a secret code used to sign (approve) actions on the network. Whoever has it can approve those actions.
- Validator: a computer that checks new transactions against the network’s rules.
- Smart contract: a program on the network that acts by itself when set conditions are met.
- Oracle: an outside data source that tells a smart contract what happened in the real world, such as “payment received”.
- Stablecoin: a token designed to keep a steady value, for example one linked to the ringgit.
A bank payment and a blockchain transfer
When you transfer ringgit from your bank account, the payment system and the banks’ records show who paid what. A blockchain transfer works differently. It updates the network’s shared record, called a ledger.1
So ask what that update actually moves. It could be one of three things:2
- a cryptoasset that belongs to the network itself, such as bitcoin on the Bitcoin network;
- a claim on the company that issued the token; or
- just information.
A ringgit payment through a bank and a token transfer can be two separate events.2
How the record is kept
A blockchain groups transactions into blocks. Each block is linked to the one before by a kind of digital fingerprint, called a hash. If someone changes an old entry, its fingerprint no longer matches, so the change shows up.1
Computers on the network check each transaction against the network’s rules. They then agree on which history to accept. This process is called consensus. Different networks reach consensus in different ways.1
The result is a record designed to make changes easy to spot and hard to make. Calling it “impossible to change” goes too far.1
Who controls the record?
In a normal set-up, users send instructions to one organisation. That organisation controls the main database. It can still keep copies and backups.
In a shared-ledger set-up, several computers keep and check the agreed record. But shared copies do not mean every customer can approve transactions. There may still be a powerful operator in charge.1
Networks also differ in who may take part:1
| Permissioned network | Public (permissionless) network | |
|---|---|---|
| Who can take part | Only people or organisations that have been admitted | Generally anyone, under the network’s rules |
| Different roles | Reading, sending and checking (validating) records can each need a different permission | Running a validator or publishing blocks can need resources, such as computers and money |
Even when a network is open to all, a service that gives you access to it can still ask you to prove who you are.1
One database or a shared ledger
A comparison of ideas. Both designs still need governance: clear rules on who decides and who is responsible.
One organisation controls the main record
- Users send requestsFarah, Kumar and the warehouse staff send instructions.
- The operator checks and updatesIts database, access rules and audit trail (a log of who changed what) record the change.
- Users get the resultCopies or backups can exist, but the operator is still responsible.
Several admitted organisations share a record
- Users send signed requestsFor example, Farah asks to transfer a receipt token.
- Member computers checkComputers on the warehouse side, the seller’s side and the buyer’s side apply the agreed network rules.
- The accepted history is copiedEach member’s record is updated. Rules on who is admitted and how disputes are settled still matter.
A made-up example: rice in a warehouse
Farah stores 100 bags of rice at a warehouse. She sells her rights under the warehouse receipt to Kumar. One token stands for the whole batch of 100 bags, not one bag. They agree a price of RM10,000. Kumar pays it by a separate bank transfer.
Farah, Kumar and these figures are made up. They show how the steps fit together. We are not describing a real warehouse product or its legal effect.
Each person has a job:
- Farah must transfer only the rights she agreed to sell, and only rights she actually has.
- Kumar must pay the agreed price.
- The warehouse must follow its agreement on storing and releasing the rice.
Before any token is created, someone must check four things:2
- that the batch really exists;
- its quality;
- who may transfer it; and
- whether someone else already has a claim on it.
The network cannot walk into the warehouse and look.
Signatures and keys
A digital signature shows that a particular signing key approved a message, under the system’s checks. On its own, it does not prove that the person using the key is the rightful owner of the rice.1
A private key is secret signing information. Whoever controls it can approve actions on the network. So keys must be kept safe. There must also be a reliable way to match each key to a real person.1
From request to record
Made-up example: 1 token stands for 100 bags of rice. The RM10,000 is paid separately through a bank.
The token record
- Farah signs a transfer requestHer signing key approves a message to move the token to Kumar’s address.
- The network applies its rulesIt checks the signature and that the token is available. A valid request can still carry false information from outside.
- The record is accepted and sharedOnce the network treats the transaction as final under its rules, Kumar’s address is shown as holding the token.
The payment and the goods (separate)
- Kumar pays Farah RM10,000The bank’s payment confirmation is outside this ledger.
- Both sides match the two eventsA token update alone does not prove that the bank payment went through.
- The warehouse releases the rice under its agreementDelivery, and rights that can be enforced, need checks and papers outside the blockchain.

The token and the rice are different things
The ledger may now show Kumar’s address holding the token. But the bags are still in the warehouse. Kumar’s right to collect them depends on:2
- the receipt that was issued;
- the transfer agreement between Farah and Kumar;
- the warehouse’s storage (custody) arrangements; and
- the law that applies.
Some problems stay real even if the token history is perfectly accurate. Examples are a copied or forged receipt, two people claiming the same rice, damaged goods, or a warehouse keeper that fails.2
When Kumar collects the rice, the token record and the warehouse’s records must be closed together. Otherwise the same batch could appear to be still available. In our made-up model, the system must be designed to do this.5
We have not looked at a signed Malaysian warehouse receipt, liens (other people’s legal claims on the goods), insurance or dispute papers. So this guide cannot tell you whether anyone would have a right to real goods that the law would enforce.
The record and the real asset
Made-up warehouse model: the token, the goods and the rights must stay linked.
On the ledger
- Token ID and holder’s addressShows the accepted digital record and the history of transfers.
- Transfer or closing updateStops the same token being used again, but only if the system and the people running it work as designed.
Links that people must keep up
- Issuer and data checkerMatch one token to the right batch. Check the quantity and any other claims.
- Signed terms and identityLink each address to a real person. Set out the rights to transfer, to redeem (collect the goods) and to settle disputes.
Outside the ledger
- The warehouse holds 100 bags of riceQuality, damage, storage charges and the actual release still need attention.
- Delivery and enforcementA warehouse keeper, bank or dispute body must actually carry out its duties.
What a smart contract can do
A smart contract is a program that carries out set actions when its coded conditions are met.1 Think of a vending machine. Put in the right money and it releases a drink, with no shopkeeper needed.
In the warehouse example, a smart contract could block the token transfer until an approved “payment received” message arrives. That message must come from an outside data source, such as a system that confirms the bank payment. In blockchain terms, this source is called an oracle. If the oracle sends wrong information, the code can still act on it and give the wrong result.3,5
Atomic settlement: both or neither
Atomic settlement means two linked transfers happen together, or neither happens. This works only within a set-up built to support it. It can lower the risk that one side hands over its part while the other side fails.3
In our example, the bank payment and the token transfer are separate. So they are not automatically atomic.
Calling a program a “contract” does not make it a contract that the law will enforce. It does not settle disputes over who owns what. It also does not give the deal Shariah approval.5

Costs, limits and when a database is enough
Compare the cost of the whole operation, not just the technology. This includes:1,5
- keeping the records up to date;
- connecting to banks and warehouses;
- security;
- inspecting the goods;
- safekeeping (custody);
- handling disputes; and
- helping users.
Public networks can also charge fees to process transactions. Who pays these fees, and how much, depends on how the system is built. This guide does not assume any fee rate or any cost saving. Also, not every blockchain uses “mining” that needs a lot of electricity.1
Do you really need a blockchain?
Start with one question. Do several independent parties really need to keep a shared history together?
- If one accountable organisation can do the job reliably, a database with access controls and an audit trail may be simpler.
- If the parties do need a shared ledger, compare four things before choosing a blockchain. How will it be governed? How private is the data? How much can it handle? How do mistakes get corrected?
This is our own comparison of designs. Neither system always wins.
What is BNM testing in Malaysia?
BNM runs the Digital Asset Innovation Hub (DAIH). Its list includes controlled tests of:4
- stablecoins linked to the ringgit; and
- tokenised deposits (bank deposits recorded as tokens).
The tests look at payments between businesses and at settling trades in securities, such as shares and bonds. They are not retail products. Members of the public cannot sign up for them.4
Being admitted to DAIH does not guarantee that regulators will recognise a product. A live launch needs further assessment by BNM. DAIH is open to:4
- regulated financial institutions;
- fintech companies; and
- other companies set up in Malaysia that are building relevant solutions.
Foreign companies can take part through a Malaysian partner. DAIH is not a scheme that consumers can apply to.4 BNM’s October 2025 discussion paper on tokenisation also says clearly that it does not set final regulatory positions.5
Who can use a blockchain service?
Three questions are separate. The word “blockchain” answers none of them.5
- The network decides who may take part in it.
- The service provider sets its own rules on who can be a customer.
- A Shariah assessment looks at the asset, the contract and the activity.
Here is a separate example of a provider’s customer rules. Luno Malaysia’s terms say users must:6
- be at least 18;
- be able to enter a contract;
- use their own account; and
- be able to complete identity checks.
The parts of the terms we read do not say users must be Muslim.6 Meeting these rules does not guarantee that your account will be accepted or that you can use every service. Luno is not part of the warehouse example above. To check whether a crypto asset or activity is Shariah-compliant, see our guide to crypto and Shariah.
Before you rely on a token record
Ask these six questions:
- What exactly does the token stand for, and who issued it?
- Who checks the goods or the outside data, and who pays for that check?
- Who controls the signing keys, decides who can join and corrects mistakes?
- Are the payment and the asset transfer linked? What happens if one of them fails?
- Which signed documents give you the right to delivery, to redeem the token or to compensation?
- What are the total fees, the custody risks, the privacy limits and the ways to settle a dispute?
References
We checked these sources on 6 October 2026 (Malaysia time). The technical basics come from NIST’s 2018 overview. The tokenisation points credit the named BIS authors and a speech by Christopher Waller. BNM’s October 2025 paper is for discussion only; the DAIH page includes an update from July 2026. The warehouse story and design comparisons are our own made-up models, not findings about any Malaysian product. Each outside document belongs to its publisher.
- Blockchain Technology Overview (October 2018)NIST; Dylan Yaga, Peter Mell, Nik Roby and Karen Scarfone · October 2018; NISTIR 8202Sections 2–4, 6–8
- The tokenisation continuum (11 April 2023)BIS; Iñaki Aldasoro, Sebastian Doerr, Leonardo Gambacorta, Rodney Garratt and Priscilla Koo Wilkens · 11 April 2023; BIS Bulletin 72pp. 1–6; platforms, ramps and legal challenges
- Innovation and the future of finance (event 20 April 2023)Christopher J Waller, Federal Reserve Board; hosted by BIS · Speech event 20 April 2023; BIS metadata 26 April 2023Tokenization; programmable transfers and atomic settlement
- Digital Asset Innovation Hub (DAIH) (update 30 July 2026)Bank Negara Malaysia · Initiatives updated 30 July 2026; FAQ undatedIntroduction; initiatives; FAQ 1, 2 and 4
- Asset Tokenisation in the Malaysian Financial Sector (October 2025 discussion)Bank Negara Malaysia · October 2025 discussion paperForeword; 4.3(ii), 5.28–5.30, 5.45
- Luno Malaysia Terms of use (updated 14 May 2026)Luno Malaysia Sdn Bhd · Last updated 14 May 2026; separate effective date not statedSections 3, 6, 7, 13–16
