Skip to content

1.0 Executive Summary

The Malaysia Blockchain Infrastructure (MBI) is a modular, multi-tenant platform that enables developers and organizations to discover, deploy, and manage blockchain-enabled services. It provides a managed technology stack that spans the Application, Platform, Blockchain, and Infrastructure layers, supported by an integrated Marketplace and unified APIs.

1.1 Who Should Read This Document

This document is intended for:

👨🏻‍💻 Application Developers

Application Developers (Application as a Service provider - Application Layer) who want to integrate their applications with the MBI service layer to connect to blockchain networks and become 'blockchain-enabled'.

⛓️ Blockchain Developers

Blockchain Developers (Blockchain as a Service provider - Blockchain layer) who want to integrate their blockchain with the MBI service layer to enable anyone to connect to their product.

🏗️ System Architects and Engineers

System architects and engineers who need to understand the high-level design, architecture, and infrastructure setup.

💼 Business & Product Teams

Business & Product Teams who require clarity on the modules, their purposes, and the charging or metering methods.

🛠 Operations & Support Teams

Operations & Support Teams who will manage deployment, monitoring, and issue resolution.

🔒 Security & Compliance Teams

Security & Compliance Teams who need to review authentication, authorization, wallet management, and data integrity processes.

1.2 Purpose of This Document

The purpose of this document is to provide a technical reference for the MBI service layer. It explains:
  • The architecture of MBI and how different modules interact.
  • The functional scope of each module and its intended use.
  • The integration process for application developers, including API usage.
  • The infrastructure and deployment setup across environments.
  • The security measures in place to ensure safe and reliable operations.
  • The business model, covering charging, and metering.

This ensures that all stakeholders, whether technical or non-technical, have a clear, unified understanding of how MBI works and how it can be adopted.

1.3 MBI Scope

The scope of MBI is to provide a service layer that enables organizations to connect their applications to blockchain networks in a secure, scalable, and standardized way.

At a high level, MBI focuses on:

📐 Architecture & Design

Delivering a clear framework for how applications can interact with blockchain through MBI.

📎 Core Modules

Providing key building blocks such as wallet management, transaction handling, and smart contract support.

🏗️ Infrastructure & Operations

Ensuring that deployments run smoothly across different environments.

� Data Management

Supporting both on-chain and off-chain data flows to balance efficiency with integrity.

� APIs & Integration

Offering simple, well-documented APIs so that developers can integrate quickly and consistently.

� Security & Compliance

Safeguarding digital assets and ensuring that operations meet enterprise and regulatory standards.

� Business Enablement

Supporting billing, metering, and reporting so that blockchain services can be offered commercially.

In short, MBI acts as a bridge between applications and blockchain, making blockchain adoption easier, safer, and more practical for real-world use cases.

1.4 High-Level Architecture Overview

MBI Architecture Diagram
Figure 1: High-Level MBI Stack Diagram

MBI is organized into four primary layers. The explanation of each layer is as below:

🧩 Application as a Service Layer

Purpose:

This layer represents all the applications and services that operate on top of the MBI platform.

Who it's for:

Application developers, businesses, or organizations who want to build or connect their apps to blockchain through MBI.

Examples include:

  • Industry applications such as Supply Chain, Halal Tracking, Digital Circular Economy, or Health Tracking
  • App Partners or Verticals (e.g., financial, logistics, or sustainability sectors)
  • Mobile Apps or Web Applications connecting via APIs

How it works:

  • These apps act as resource suppliers (providing data or services) and resource consumers (using blockchain services).
  • They connect to MBI through the Application as a Service (AaaS) interface, using APIs or SDKs.
⚙️ Platform as a Service Layer

Purpose:

This is the core functional layer of MBI, where the main services, modules, and integrations operate.

Main Components:

  • App Gallery / BC (Blockchain) Gallery / Marketplace & Discovery: A centralized hub where developers can discover, publish, and integrate blockchain-based applications, services, and smart contracts.

  • Smart Contract & Device Modules: Enable automated logic execution and integration with IoT devices.

  • Framework & Interoperability: Ensures smooth communication across different modules, networks, and applications, enabling cross-chain interoperability.

  • Infrastructure / DePIN / Real-World Assets (RWA): Manages the connection between physical assets or IoT devices and blockchain (e.g., device identity, bridges, consensus mechanisms, tokenization, and data synchronization).

    • Device ID: Registers and authenticates IoT or asset devices.
    • Device-to-BC Bridge: Connects real-world devices or data sources to blockchain networks.
    • Consensus Mechanism: Validates and secures blockchain transactions.
    • Tokenization: Converts real-world assets into digital tokens for traceability or trading.
    • Off-Chain & On-Chain Storage: Ensures balanced data handling, secure blockchain anchoring for integrity, and off-chain storage for efficiency.

  • Standardization, Governance & Enforcement (MBI Core): Defines compliance rules, operational standards, and governance policies for all ecosystem participants.

🔗 Blockchain as a Service Layer

Purpose:

This layer connects MBI to multiple blockchain networks, allowing interoperability and flexibility.

Partners / Examples:

  • Zetrix (MyEG)
  • MasChain (Masverse)
  • MyGovBC (JDN)
  • Other public or enterprise blockchains

Function:

MBI acts as a bridge between applications (from the upper layers) and these blockchain networks, handling:

  • Transaction routing and verification
  • Smart contract deployment
  • Data integrity and auditability

This ensures that MBI can work across different blockchain ecosystems while maintaining unified access for developers.

🔗 Infrastructure as a Service Layer

Purpose:

This is the foundation that powers the entire MBI platform, providing the computing, storage, and networking resources.

Partners / Examples:

  • Azure, AWS, TM, PDSA, IPServerOne, and other infrastructure providers.

Function:

  • Delivers cloud computing and data center capabilities for scalability and uptime.
  • Supports Infrastructure-as-a-Service (IaaS) for container orchestration (e.g., Kubernetes clusters).
  • Ensures system reliability, security, and redundancy across environments.

1.5 Public Chain Integration Plan

Public Chain Integration Flow
Figure 1.1: Public Chain Integration Flow

The Public Chain Integration Plan defines how applications connect to blockchain through the MBI service layer, ensuring secure wallet management, smart contract deployment, and transaction processing.

Application Layer: MBI Digital Asset

  • Route & Storage:
  • Files and data from applications are routed into MBI.

  • A hash is generated for integrity validation before the data is stored.

  • Transaction Trigger:

  • When CRUD operations occur, a transaction is created.
  • This transaction is then linked with a subscription ID to ensure proper tracking and access control.

Public Chain Integration Plan

💳 Wallet Creation
  • A wallet is created by invoking the Create Wallet API.
  • Each wallet is assigned a public key (pKey) and private key (gKey), stored securely in the Vault.
  • A wallet_subscription table records wallet ownership and subscriptions.
  • The Vault signs data to produce a Signed Blob, which can then be submitted to the blockchain.
🖥️ Blockchain Adapter
  • The Invoke component connects applications to the blockchain via smart contract addresses.
  • Before submission, the system performs a Fee Evaluation:
    • If fees exceed the user's limit, the system alerts the user.
    • If fees are acceptable, the system builds a transaction blob and submits it to the blockchain.
  • All transactions are logged in the transaction table for monitoring and audit.
📜 Smart Contract Deployment
  • Upload & Security Scan: Developers upload smart contracts, which undergo a security scan.
  • Fee Evaluation:
    • The system evaluates the transaction fee.
    • If the fee exceeds user limits, an alert is triggered.
  • Build & Sign:
    • A transaction blob is built, signed by the Vault, and submitted to the blockchain.
  • Smart Contract Registry: Deployed contracts are recorded in the product_smart_contract table for reference and management.