Dual-State Ledger Architecture
A mathematical and architectural overview of MOSOO's sovereign consensus, zero-knowledge note commitment tree, and native dual-address derivation.
1. Dual-Address Derivation & State Partitioning
Rather than forcing all transactions into an inefficient privacy layer or a fully surveillance-prone transparent ledger, MOSOO natively partitions account state into two complementary cryptographic domains:
Transparent Layer (soo1...)
PUBLICOptimized for public decentralized exchanges, automated market makers (AMMs), liquidity pools, and smart contracts where global state readability is required.
Shielded Layer (mosoo1...)
CONFIDENTIALEncrypted notes protected by zero-knowledge commitments. Account balances and transaction amounts remain hidden from external observers and public explorers.
2. ZK Commitments & Nullifier Registry
When an asset is shielded on MOSOO, it is minted as a cryptographic commitment:
SHIELD_COMMITMENT
Transparent $SOO is locked into the sovereign privacy vault and converted into a blinded cryptographic note. The validator records the commitment hash into the state tree without storing the note value.
UNSHIELD_NOTE & Nullifiers
When unshielding back to transparent state, the owner presents the secret blinding factor to generate a unique Nullifier: Hash(PrivateKey || NoteID). The network registers this nullifier into an immutable registry, preventing the note from ever being redeemed twice.
3. High-Throughput BFT Consensus Loop
MOSOO runs a Byzantine Fault Tolerant consensus engine operating across geo-distributed cloud nodes. Blocks are produced deterministically every 2000 milliseconds. Transactions submitted to the mempool trigger proactive block generation, ensuring sub-second settlement for real-world merchant payments and interactive DeFi.