The network, layer by layer.
This page describes the proposed design of the MUICOOIN blockchain. None of it is running yet. Anything that hasn't been decided is marked as pending, with no placeholder numbers.
Our engineers are in the final stage of building the core software.
The MUICOOIN software development team is close to completing development of the network's core components. Each component then goes through internal testing and an independent security audit. It is marked completed in the table below only after that, and before any public testnet opens.
- 01DevelopmentFinal stage · now
- 02Internal testingNext
- 03Independent security auditThen
- 04Public testnetAfter the audit
Current status
Where each component stands today.
This table is updated as work moves forward. A component is marked completed only once it has been built, tested and independently verified.
| Component | What it is | Status |
|---|---|---|
| Architecture specification | Technical design of the network, published through the whitepaper | In development |
| Node software | Software that runs the network, stores the ledger and relays transactions | Proposed |
| Proof-of-Stake consensus | Rules by which validators agree on new blocks | Proposed |
| Validator tooling | Software and guides for independent validator operators | Proposed |
| MUI issuance logic | Protocol rules that create MUI and enforce the supply cap | Proposed |
| Public testnet | Open test network using coins with no value | Proposed |
| Blockchain explorer | Public website for viewing blocks and transactions | Proposed |
| Security audits | Independent third-party review of protocol and wallets | Not started |
| Mainnet | The live production network | Not launched |
Architecture
Five layers, one chain.
Open a layer to see what has been decided and what is still open. The animation is a conceptual model only.
Decided: MUICOOIN will run its own peer-to-peer network of nodes, independent of any other blockchain.
Pending: networking protocol, node discovery method and hardware requirements for full nodes.Decided: consensus will be based on Proof-of-Stake, with validators staking MUI.
Pending: the specific algorithm, the finality model, block interval, validator set size and slashing rules.Decided: a public ledger in which every confirmed transfer can be inspected.
Pending: the account model, the transaction format, the fee mechanism and whether general-purpose smart contracts will be supported.Decided: MUI is the native coin, and a proposed maximum supply of 100,000,000 MUI will be enforced by the protocol.
Pending: decimal precision, genesis distribution mechanics and any staking reward model that keeps within the cap.Decided: official wallets and a public explorer will be built on public node interfaces.
Pending: API specification, SDKs and the merchant integration standard.
Why so many "pending" items? Because choosing them properly takes engineering work that isn't finished. Publishing guesses as specifications would mislead the people evaluating the project. The whitepaper will be versioned as each decision is made.
Consensus
How Proof-of-Stake is intended to work.
This is the general model. MUICOOIN's specific parameters are pending.
1. Staking. Validators lock an amount of MUI as a security deposit. It is their stake in the network behaving honestly.
2. Proposal. For each block, one validator is chosen to collect pending transactions and propose the next block.
3. Attestation. Other validators independently check that the block follows the rules and sign their approval.
4. Finality. Once enough of the total stake has approved it, the block is treated as final and cannot be reversed.
5. Accountability. A validator that signs conflicting blocks or otherwise breaks the rules can lose part of its stake (slashing).
| Parameter | Value |
|---|---|
| Algorithm family | Proof-of-Stake (planned) |
| Specific protocol | Pending specification |
| Block interval | Pending specification |
| Finality threshold | Pending specification |
| Minimum validator stake | Pending specification |
| Slashing conditions | Pending specification |
| Staking rewards | Pending specification |
Validators
Security that isn't held by one party.
A network secured only by its founders isn't really independent. The aim is a validator set run by many unrelated operators.
- Independent operatorsValidators are intended to be run by organisations and individuals who are not part of MUICOOIN.
- Open documentationHardware, software and operational requirements will be published before the testnet opens.
- Testnet firstProspective validators can rehearse on the public testnet before mainnet.
- Transparent setThe active validator set and each validator's stake would be visible in the explorer.
A payment, step by step
From tap to final.
How a MUI payment would travel through the network once it's operational.
- 01
Sign
The sender's wallet creates the payment and signs it with a private key that never leaves the device.
- 02
Broadcast
The signed transaction is sent to MUICOOIN nodes, which check it and pass it along the network.
- 03
Include
The selected validator includes the transaction in a proposed block.
- 04
Finalise
Validators attest to the block. Once it's final, the payment can't be reversed.
- 05
Confirm
Both wallets show the payment as confirmed, and it is visible in the public explorer.
Security approach
What has to happen before mainnet.
These are commitments about process, not claims about results. No audit has taken place yet.
| Measure | Description | Status |
|---|---|---|
| Public testnet | An extended period of open testing, including by independent validators | Proposed |
| Protocol audit | Independent third-party review of consensus and node software. The report will be published. | Not started |
| Wallet audit | Independent review of key handling in all official wallets | Not started |
| Bug bounty | Rewards for responsibly disclosed vulnerabilities | Proposed |
| Performance testing | Measured, reproducible results under load, published with the method used | Proposed |

