> For the complete documentation index, see [llms.txt](https://mih.gitbook.io/mine-holdings/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mih.gitbook.io/mine-holdings/mih-whitepaper/solution/system-architecture.md).

# System Architecture

<figure><img src="/files/2GytshOUhbSvAJMAyD86" alt=""><figcaption></figcaption></figure>

### **hybrid system**

The MIH platform is designed as a hybrid system that integrates both on-chain and off-chain components.&#x20;

The on-chain layer consists of the blockchain network where $MIH and smart contracts operate. The off-chain layer includes the PG servers and databases responsible for real-time transaction processing and user authentication.

This dual-layer architecture ensures the trustlessness of decentralization while retaining the speed and performance of centralized systems.

<figure><img src="/files/pLaGAngdaiDy3Svk8s9P" alt=""><figcaption></figcaption></figure>

### **Multi-Chain Support**

MIH is built on the BNB Smart Chain (BSC), which is compatible with the Ethereum Virtual Machine (EVM). The native token, $MIH, is issued according to the BEP-20 token standard. To support multi-chain expansion, future plans include deployment on Ethereum Layer 2 networks as well.

On the blockchain, key DeFi functionalities—such as token issuance and burning, staking rewards—are implemented as smart contracts, providing full transparency. For example, when a user stakes $MIH, the reward is calculated and distributed automatically based on predefined contract rules, without any centralized involvement.

In actual retail or online merchant environments, off-chain components—particularly the PG server—play a critical role in processing $MIH payments. When a user initiates a transaction, the PG server facilitates blockchain interaction and, if necessary, pre-settles the payment using its internal liquidity while awaiting blockchain confirmation. This ensures a smooth user experience.

The typical payment process is as follows:

1. **Payment Request**: The user selects $MIH as the payment method at checkout. The PG server receives relevant information such as payment amount and wallet address.
2. **Price Conversion**: The PG server calculates the equivalent amount of $MIH in real time using a price oracle or exchange rate API.
3. **Balance Verification & Transaction Creation**: The server checks whether the user’s web wallet or linked wallet has sufficient balance. If so, it calls the appropriate smart contract to create a payment transaction (transferring $MIH from the user to the merchant’s wallet address).
4. **Blockchain Verification**: The transaction is broadcast to the blockchain network, validated by nodes, and included in a block. This ensures immutability and transparency. Initial confirmation is typically completed within a few seconds to tens of seconds.
5. **Confirmation & Notification**: After a sufficient number of confirmations, the transaction is deemed complete. The PG server then sends a callback or notification to the merchant, allowing them to proceed with fulfilling the order.
6. **Settlement Processing**: The merchant can choose to receive settlement either in fiat currency or in $MIH.<br>

<figure><img src="/files/ivwbiXVcLso2eeMJ48ff" alt=""><figcaption></figcaption></figure>

### **Supported Payment Currency**

Currently, payments using $MIH and USDC are supported, and future updates will include support for fiat currency payments as well.

<br>