Introduction
When Nigerian banks, development finance institutions, or regulated fintechs evaluate blockchain for asset tokenization, they are not evaluating Bitcoin or Ethereum. They are evaluating permissioned blockchain infrastructure — systems where participation is controlled, identity is known, and the rules of the network are set by the consortium operating it.
Hyperledger is the primary open-source framework for this category of blockchain deployment. Maintained by the Linux Foundation with contributions from IBM, Intel, and dozens of financial institutions globally, Hyperledger Fabric and Hyperledger Besu are the two most widely deployed permissioned blockchain platforms in financial services.
This article explains how they work, what they enable for asset tokenization, and what African financial institutions need to consider when evaluating them for deployment.
Permissioned vs permissionless: why it matters for financial institutions
Public blockchains like Bitcoin and Ethereum are permissionless — anyone can participate, validate transactions, and read the ledger. That openness is a feature for censorship resistance and decentralization. It is a problem for regulated financial institutions that need to know who they are transacting with, control who can access sensitive financial data, and comply with AML/KYC requirements.
Permissioned blockchains solve this by requiring all participants to be identified and approved before joining the network. Transaction validation is performed by a known set of organizations rather than anonymous miners or validators. Data visibility can be restricted to the parties involved in a transaction. The network rules are governed by the consortium rather than by open-source protocol upgrades.
For a Nigerian bank tokenizing trade finance receivables, or a development finance institution issuing digital bonds, or a central bank exploring a wholesale CBDC, the permissioned model is not a compromise — it is the appropriate architecture.
Hyperledger Fabric: the enterprise standard
Hyperledger Fabric is the most widely deployed enterprise blockchain platform globally. Its architecture is designed specifically for the requirements of financial institutions: modular consensus, private data collections, channel-based data isolation, and chaincode (smart contract) execution in isolated containers.
The key architectural features that matter for asset tokenization are channels and private data collections. Channels allow different subsets of network participants to maintain separate ledgers — a bank and its counterparty can transact on a channel that is invisible to other network members. Private data collections allow specific fields in a transaction to be shared only with designated parties while a hash of the data is recorded on the shared ledger for auditability.
For tokenizing assets like trade receivables, invoice financing instruments, or interbank settlement tokens, this granular data privacy is essential. The parties to a transaction need full visibility. Regulators need auditability. Competitors on the same network need neither.
Hyperledger Besu: EVM compatibility for regulated networks
Hyperledger Besu is an Ethereum client designed for enterprise use. It supports the full Ethereum Virtual Machine, which means Solidity smart contracts written for Ethereum can be deployed on a Besu network without modification. It supports permissioned network configurations, private transactions through the Tessera privacy manager, and multiple consensus algorithms suited to enterprise deployments.
The practical advantage of Besu for institutions that have already invested in Ethereum tooling and developer expertise is significant. The same smart contract code, the same development tools, and the same token standards (ERC-20, ERC-721, ERC-1400 for security tokens) work on a private Besu network as on public Ethereum — but with controlled participation, private transactions, and no gas market.
ERC-1400 is particularly relevant for asset tokenization in regulated markets. It is a security token standard that encodes transfer restrictions, compliance rules, and forced transfer capabilities directly into the token contract — enabling the kind of regulatory compliance that public Ethereum tokens cannot easily accommodate.
Asset tokenization use cases for African financial institutions
- Trade finance: tokenizing letters of credit, bills of lading, and trade receivables on a permissioned network shared by banks, importers, exporters, and logistics providers — reducing settlement time from weeks to hours
- Interbank settlement: replacing correspondent banking relationships with a shared settlement token on a central bank-operated Fabric network, enabling real-time gross settlement between member banks
- Digital bonds: issuing government or corporate bonds as tokens on a permissioned network, enabling fractional ownership, automated coupon payments through smart contracts, and secondary market trading among licensed participants
- Commodity-backed tokens: tokenizing warehouse receipts for agricultural commodities on a network shared by commodity exchanges, warehouses, banks, and traders — enabling instant financing against verified inventory
- Mortgage and property tokens: representing property ownership as tokens on a land registry network, enabling fractional investment and reducing the friction of property transfer
Deployment considerations for Africa
The technical deployment of Hyperledger Fabric or Besu is well-documented and supported by a mature ecosystem of system integrators. The harder challenges in African deployments are institutional and infrastructural.
- Consortium formation: a permissioned network requires multiple organizations to agree on governance, node operation responsibilities, and the rules for adding or removing participants. This is a legal and organizational challenge as much as a technical one.
- Node infrastructure: each participating organization needs to operate one or more nodes. In markets with unreliable power and connectivity, node uptime requirements need to be designed around realistic infrastructure constraints.
- Regulatory engagement: deploying a tokenization network that involves regulated financial instruments requires early and ongoing engagement with the SEC, CBN, or relevant regulatory body. The technology is ready; the regulatory framework is still developing.
- Interoperability: a tokenization network that cannot connect to existing core banking systems, payment rails, or other blockchain networks has limited utility. Integration with NIBSS, Paystack, or SWIFT should be part of the architecture from the start.
- Legal enforceability: the smart contract rules governing token transfers need to be legally enforceable in Nigerian courts. This requires careful drafting of the legal agreements that sit alongside the technical contracts.
The opportunity
African financial institutions are not behind on blockchain adoption because the technology is not ready. They are behind because the institutional coordination required to deploy permissioned networks is hard, and because the regulatory frameworks are still catching up to the technical possibilities.
Both of those constraints are loosening. The SEC Nigeria's digital asset framework, the CBN's engagement with digital currency infrastructure, and the growing number of African banks with dedicated blockchain teams all point toward a deployment window that is opening rather than closing.
The institutions that build the technical capability and regulatory relationships now — before the window is fully open — will be positioned to operate the infrastructure that others depend on. That is a structurally advantaged position in any market.