Document MUI-WP · Draft 0.1
MUICOOIN Whitepaper
How to read this document. It describes a proposed design. No part of the MUICOOIN network is implemented or operational. Where a value or mechanism has not been decided, it is marked pending specification. No benchmarks, audits or completed milestones are claimed, because none exist yet. This document is not an offer of any kind.
01Executive Summary
MUICOOIN is a proposed independent Layer-1 blockchain designed for digital payments. Its native coin, MUI, would be used to pay network fees and, under the planned Proof-of-Stake model, staked by validators to secure the network. A maximum supply of 100,000,000 MUI is proposed and would be enforced by the protocol.
The project plans to deliver, in sequence: the base network, official mobile, desktop and merchant wallets, a public explorer, a public testnet with independent validators and security audits, and then, subject to audit results and legal clearance, a mainnet launch. Merchant adoption and international expansion follow from there.
The project is in its foundation phase. This draft sets out the design intent and the open questions that engineering work still has to answer.
02Introduction
Cross-border payments often involve multiple intermediaries, unpredictable fees and settlement that follows banking hours. Public blockchains have shown that value can be transferred directly between parties and recorded on a shared ledger. In practice, though, many digital assets are issued as tokens on general-purpose chains, where fees and capacity are set by unrelated activity on the host network.
MUICOOIN takes a different approach. It builds a dedicated network whose parameters can be tuned for payments. This brings clear trade-offs. A new network must attract independent validators, earn trust in its security and build its own tooling. This paper is written with those costs in view.
Scope
This paper covers network architecture, consensus, validators, the MUI coin, proposed coin economics and distribution, wallets, merchant infrastructure, security, the roadmap, regulation and risks. It does not cover any sale or investment arrangement.
03Project Vision
The vision is summed up in the project line: one coin, one wallet, global payments. Individuals, merchants and businesses would use one native coin, through a compatible family of wallets, on one public network, so that a payment works the same way wherever the two parties are.
- Individuals: hold MUI in self-custody and send it to any address.
- Merchants: accept MUI at the point of sale and online, with reconciliation built in.
- Businesses: settle cross-border invoices on a ledger both parties can verify.
Whether that vision is realised depends on technology delivery, user and merchant adoption and the law in each market. None of these is assured.
04Blockchain Architecture
The network is designed as a standalone Layer-1. It has its own peer-to-peer network, ledger, consensus and native coin, and it is neither secured by nor dependent on any other blockchain.
Components
- Nodes keep a copy of the ledger, validate transactions and blocks, and relay them to peers.
- Validators are nodes that have staked MUI and take part in producing and finalising blocks.
- The ledger is an append-only chain of blocks, each referencing the hash of the previous block.
- Public interfaces (RPC/API) let wallets, the explorer and third parties read the chain and submit transactions.
Design parameters
| Parameter | Value |
|---|---|
| Network type | Independent Layer-1 (decided) |
| State model (account / UTXO) | Pending specification |
| Transaction format & signature scheme | Pending specification |
| Smart contract support | Under evaluation |
| Block size / gas limits | Pending specification |
| Fee mechanism | Pending specification |
| Node hardware requirements | Pending specification |
| Implementation language / codebase | Pending specification |
A payment-focused chain puts predictable fees, fast finality and simple transfer semantics ahead of general computation. Whether to support general smart contracts is an open question, weighed against the extra attack surface they bring.
05Consensus Mechanism
MUICOOIN plans to use Proof-of-Stake (PoS). Validators lock MUI as stake. For each slot a validator is selected to propose a block, and other validators attest to its validity. A block is final once attestations representing a defined share of total stake have been collected. Validators that sign conflicting blocks or otherwise provably misbehave can have part of their stake removed (slashed).
Properties sought
- Deterministic finality. Once a payment is final it can't be reversed. Merchants need this.
- Accountable safety. Any safety violation should be attributable to specific validators.
- Liveness under partial failure. The network should keep producing blocks if a minority of validators go offline.
- Energy efficiency compared with Proof-of-Work.
Open decisions
| Protocol family (e.g. BFT-style vs. longest-chain with finality gadget) | Pending specification |
|---|---|
| Proposer selection method | Pending specification |
| Block interval and finality time | Pending specification |
| Finality threshold (share of stake) | Pending specification |
| Slashing conditions and penalties | Pending specification |
| Delegation (non-validators staking via validators) | Under evaluation |
06Validator Infrastructure
The network's independence depends on its validators being operated by many unrelated parties. The project intends to publish validator software, documentation and monitoring tools, and to bring outside operators onto the public testnet before mainnet.
Validator economics
Validators bear real costs: hardware, bandwidth, operations and the opportunity cost of locked stake. Rewards could come from transaction fees and/or a pre-allocated reward pool, because the hard supply cap rules out open-ended inflation. Which source is used, at what level and for how long is pending specification. Modelling of validator economics will be published before the testnet.
| Minimum stake | Pending specification |
|---|---|
| Active validator set size | Pending specification |
| Admission (permissionless / staged) | Pending specification |
| Unbonding period | Pending specification |
| Reward source and rate | Pending specification |
07Native MUI Coin
MUI is the native coin of the MUICOOIN network. It isn't a smart-contract token. Its balances and transfers are part of the base protocol.
- Fees: transaction fees are paid in MUI.
- Staking: validators stake MUI to take part in consensus (as proposed).
- Payments: MUI is the unit transferred between wallets and to merchants.
| Name / unit | MUI |
|---|---|
| Proposed maximum supply | 100,000,000 MUI |
| Divisibility (decimal places) | Pending specification |
| Issuance at genesis vs. over time | Pending specification |
08Coin Economics
The total supply is capped at a proposed 100,000,000 MUI and can't be increased once mainnet launches without a change to the protocol, which would be publicly visible. The proposed allocation is:
| Category | Share | Proposed amount |
|---|---|---|
| Merchant Ecosystem | 25% | 25,000,000 MUI |
| Exchange Liquidity | 20% | 20,000,000 MUI |
| Company Development | 15% | 15,000,000 MUI |
| Community Rewards | 15% | 15,000,000 MUI |
| Strategic Partnerships | 10% | 10,000,000 MUI |
| Treasury Reserve | 10% | 10,000,000 MUI |
| Founders and Team | 5% | 5,000,000 MUI |
| Total proposed maximum supply | 100% | 100,000,000 MUI |
Because supply is fixed, the economic design has to cover how validators are paid over the long term. That means balancing fee revenue against any reward allocation, and setting release schedules that keep circulating supply predictable. These schedules are pending specification.
09Proposed Distribution
The following principles are proposed to govern distribution:
- No distribution before mainnet, independent audits and legal review.
- Release schedules for every category are published in advance.
- Founders, team and any investor allocations vest over time. A 24-month vesting period is proposed for investor allocations, subject to final legal documentation.
- Allocation addresses are published and can be checked on-chain.
- Each allocation is used only for its stated purpose, and changes are disclosed before they take effect.
The mechanics of release (on-chain vesting contracts, protocol-level locks or custodial arrangements) are pending specification.
10Wallet Ecosystem
Three official wallets are planned: mobile (iOS, Android), desktop (Windows, macOS, Linux) and merchant. All are designed for self-custody. Private keys are generated and stored on the user's device and never held by MUICOOIN.
- Recovery phrase backup with verification.
- Transaction review screens showing amount, recipient and fee before signing.
- Device encryption, PIN and biometric locks.
- Staking support in the desktop wallet, subject to the final consensus design.
- Public node interfaces, so that third-party wallets can integrate.
The key derivation scheme, recovery phrase standard and hardware wallet support are pending specification.
11Merchant Payment Infrastructure
Merchant acceptance is planned in layers. The first is a merchant wallet with QR payment requests and confirmation once a payment is final. Then come reconciliation and accounting exports, and later e-commerce plug-ins and integrations with existing payment providers, where permitted.
The project expects that, in practice, merchants may need to price in local currency and manage exposure to MUI price movements. How conversion and settlement services might be offered, and by whom, depends on regulation and partners. No partners are in place. This section is pending specification.
12Security Considerations
New networks face particular risks. These include low initial stake making attacks cheaper, software bugs in new code, concentration of validators, and key compromise at the wallet level. The project's planned mitigations are:
- An extended public testnet with independent validators.
- Independent third-party audits of protocol and wallets before mainnet, with reports published.
- A responsible disclosure policy and a proposed bug bounty.
- Staged validator onboarding to avoid concentration.
- Secure key management and multi-party controls for project-held allocations.
No audit has been carried out yet. No claim of security is made for code that doesn't exist.
13Development Roadmap
Six proposed phases: (1) Foundation, (2) Blockchain development, (3) Wallet development, (4) Testing and security, (5) Mainnet launch, (6) Global expansion. Each phase has exit criteria rather than calendar dates. The full detail is on the Roadmap page. Phases are objectives, not guarantees.
14Regulatory Considerations
MUICOOIN intends to be based in the United Arab Emirates, where virtual asset activities are regulated under several regimes. These include federal virtual asset rules and the Securities and Commodities Authority (SCA); the Virtual Assets Regulatory Authority (VARA) under Dubai Law No. 4 of 2022; the Central Bank of the UAE (CBUAE) for payment tokens and stored value; and the ADGM FSRA and the DFSA within their free zones. Which regime applies depends on where the issuing entity is established and which activities it carries out.
- Issuance and distribution of MUI, and any fundraising, may require a licence or approval, and will not take place before UAE legal advice and any required approval.
- Marketing of virtual assets to UAE residents is regulated. This website is therefore informational only and contains no offer or promotion.
- Payments: under the CBUAE payment token framework, paying for goods and services in mainland UAE is generally limited to licensed dirham-backed payment tokens. Merchant use of MUI in the UAE may therefore be unavailable, or possible only through licensed intermediaries. The merchant roadmap will follow the law in each market.
- AML/CFT: KYC, source-of-funds checks and sanctions screening under Federal Decree-Law No. 20 of 2018 (as amended or replaced) would apply to any future participation.
- Data protection: personal data is handled under Federal Decree-Law No. 45 of 2021 (PDPL), or the ADGM/DIFC rules if applicable.
- Tax: UAE corporate tax and VAT treatment will be assessed with advisers.
MUICOOIN currently holds no regulatory approval, licence or authorisation in the UAE or elsewhere.
15Risk Factors
The material risks are set out in full in the Legal and Risk Disclosures. In summary, they include development risk, technology and security risk, regulatory risk, market and liquidity risk, adoption risk, key-person and funding risk, and the risk that MUI never has any value.
16Conclusion
MUICOOIN proposes a dedicated Layer-1 network for payments, with MUI as its native coin, a fixed proposed supply and a wallet family designed for self-custody and merchant use. The direction is set and many of the details are still open. This draft will be revised as each decision is made, and every revision will be published and versioned so readers can see what changed and why.

