The protocol distinguishes between the Immutable Logic (Submerged) and the Dynamic Interface (Surface).

• Submerged Layer: A recursive, N-level deep MLM tree. Each node is a standalone smart contract acting as a gateway.
• Surface Layer: One-page JavaScript/HTML applications or simple mobile App's ("The surface of Iceberg Summits, Roots") where users, Pinguins, interact with financial instruments (Minting/Burning) without needing to understand the underlying complex hierarchy.

Unlike traditional centralized MLM systems, the Iceberg Protocol utilizes a Non-Custodial Tree Model.

3.1 Recursive Deployment (The Sponsor Chain)

Every node is deployed by its "Sponsor" contract. During initialization, the upstream data of 6 ancestral levels is passed down, ensuring that rewards and data packets always have a verified path to the Root. This creates a chain of trust established at the moment of the WASM deployment.

3.2 Heartbeat & The Pruning Protocol

System hygiene is maintained through "Proof of Presence." Users must interact with their node to maintain its Active status.

• Notification Period: If a sponsor becomes inactive, a child node issues a "Wake-up" call via the on-chain messaging system.
• The Resolution Choice: After a 168-hour grace period, the child can choose to Support (pay the sponsor's storage rent to maintain hierarchy) or Prune (sever the link).
• Promotion to Root: Pruning results in the child node becoming a new "Root Node." It gains full governance over its own branch, including the right to set PID parameters and custom fee structures - a new Iceberg Summit.
• About inactive leafs: When a leaf becomes inactive, the process is similar, except that the sponsor is the awakener or absorber.
• Incentivized Activity: Active participation is rewarded, while dormant nodes risk losing their resources and hierarchical benefits.
• Decentralized Evolution: This mechanism allows the MLM tree to evolve organically, with active participants rising to leadership roles, ensuring a dynamic and self-sustaining ecosystem.

To achieve high scalability and modularity, we implement a Port-based Messaging System. Contracts do not call each other's functions directly in a rigid way; instead, they send standardized "Data Packets" to a Queue.

This architecture allows a "Plug-and-Play" approach:

• Vault Ports: For managing asset baskets and collateral.
• RWA Ports: For late-stage integration of audited physical assets.
• Third-Party Ports: External projects can hook into an Iceberg MLM tree by simply implementing the MessagePort interface.

The CYBERFORINT (CYF) asset is the native, dynamically-backed crypto-asset of the Iceberg ecosystem. The total supply of CYF is zero at launch; assets are introduced into circulation solely through the Minting process initiated by active Root Nodes and Pingvin users.

CYF Issuance & Stability: CYF is not pegged to any existing fiat currency. Its value is stabilized algorithmically by a digital PID (Proportional-Integral-Derivative) Controller implemented in fixed-point Rust math. This controller monitors the network's Mint/Burn velocity and adjusts the collateralization ratio in real-time, ensuring unique market dynamics based purely on internal ecosystem activity.

Resonance & Noise Filtering: Root nodes are responsible for setting the Alpha Filter for their respective branches. This parameter allows the Root to manage how aggressively their local market reacts to volatility, enabling a healthy competition for user stability.

The Iceberg Protocol is intended to be the "Gold Standard" for on-chain MLM structures. We encourage external developers to build their own "Icebergs" using our battle-tested messaging and pruning models.

Accessing the Infrastructure requires the ZSOZSO Utility Token:

To utilize the Iceberg MLM framework for external projects and access the core smart contract libraries, the ZSOZSO asset is required as the primary utility fuel. The ZSOZSO token acts as the key to:

• Initialize new hierarchical structures within the ecosystem.
• Authorize cross-contract messaging between independent MLM nodes.
• Finance core infrastructure development: Fees paid in ZSOZSO directly fund the continuous maintenance and auditing of the protocol's codebase.

By tethering the system to ZSOZSO (Issuer: GDZK...SSZJRQUC), we ensure a sustainable growth model for the protocol's maintainers and early adopters.

1. Phase 1: Deployment of the Core MLM & Pruning Engine (Soroban Mainnet).
2. Phase 2: Launch of the initial Asset-Basket Vaults and PID-regulated CYBERFORINT (CYF) Minting.
3. Phase 3: Public API for ZSOZSO-powered third-party MLM deployments.
4. Phase 4: Integration of audited Real-World Assets (RWA) as further collateral options for CYF.

CYF Minting Flowchart

1. Pingvin Request: User selects an iceberg and initiates Minting via SPA interface.
2. Message Queue: MLM Router identifies the target Iceberg & Port.
3. PID Engine: Calculates dynamic collateral ratio based on velocity.
4. Vault Lock: Collateral assets are secured in the Vault.
5. CYF Issuance: CYBERFORINT is minted to user's wallet.

Infrastructure Fuel: ZSOZSO

While CYF serves as the internal algorithmic asset, the entire framework is sustained by ZSOZSO. External developers and MLM projects utilizing this framework contribute to the project's development via ZSOZSO-based license fees, ensuring the ecosystem's continuous evolution.

ZSOZSO asset →

The Iceberg Protocol is implemented as a suite of 9 interconnected projects — 6 PWA applications and 3 shared Rust libraries — all compiled to WebAssembly via Dioxus. Every app runs offline-first in the browser as a Progressive Web App.

Note: All repositories are currently private. ZSOZSO holders will gain access once the Stellar network reaches 4,000 trustlines with a minimum of 2,000,000 ZSOZSO on each of those 4,000 accounts.

8.1 Shared Libraries

All 6 applications share the same foundation: three Rust libraries that handle the blockchain, database, and secure storage layers. All three use trait-based abstraction — apps depend on interfaces, not concrete implementations. Multi-language support (English, French, German, Hungarian, Spanish) is built into every library.

• ledger — Stellar blockchain abstraction layer. Handles Ed25519 keypair generation, XDR transaction building and submission via Horizon API, and Soroban smart contract integration (ZSOZSO locking/unlocking, Proof-of-Zsozso contract). Supports both Testnet and Mainnet.
• db — Abstraction layer for GUN.js, a decentralized real-time graph database. Provides interfaces for peer relay configuration, SEA cryptographic signing, and the NetworkGraph trait that manages the MLM parent/worker hierarchy. Offline-first with localStorage persistence.
• store — Secure encrypted storage for secret keys. Supports IndexedDB and localStorage backends, plus WebAuthn Passkey integration with PRF-based key derivation for layered encryption of secrets.

8.2 Applications

• cyf — PWA for burning and minting CYBERFORINT (CYF) tokens on Stellar. Displays balances, generates QR codes for public keys, and provides biometric/PIN-based key management.
• mlm — PWA for building the Iceberg Protocol's hierarchical MLM community ("Antarctica"). Manages the parent/worker relationship tree, visualizes the network hierarchy, and supports QR code-based worker recruitment.
• proof-of-zsozso — PWA for locking/unlocking ZSOZSO tokens via a Soroban smart contract. Generates protocol income. Mainnet-only operations with balance display for XLM, ZSOZSO, and locked amounts.
• merlin — The root node application for the Antarctica MLM network. Restricted access — requires the Merlin secret to start. Acts as the gateway/root for the entire MLM hierarchy.
• admin — Administrative dashboard for oversight of all Iceberg Protocol apps on a device. Provides diagnostics for the local MLM environment, in-app log buffer with save/dump/upload functionality, and remote log shipping to a Python backend.
• gun-connect — Utility PWA for connecting a GUN relay node to a device. Handles relay URL configuration, connection status monitoring, and GUN DB secret management.

8.3 Dependency Flow

All six apps import the same three libraries:

  cyf, mlm, proof-of-zsozso, merlin, admin, gun-connect
    |         |         |
    db      ledger    store
  (GUN)   (Stellar)  (secrets)

The apps are independent PWAs — each deployed separately — but they share data through the GUN graph database and the Stellar ledger.

8.4 Tech Stack

• Language: Rust, compiled to WebAssembly
• UI framework: Dioxus
• Blockchain: Stellar (Horizon API + Soroban smart contracts)
• Database: GUN.js (peer-to-peer, encrypted, real-time sync)
• Crypto: Ed25519, SHA-256, WebAuthn Passkey, SEA signing
• Storage: IndexedDB + Passkey PRF encryption
• Deployment: PWA (offline-capable, installable)
• Languages: English, French, German, Hungarian, Spanish

The source code will be opened to ZSOZSO holders when 4,000 Stellar accounts hold a trustline with at least 2,000,000 ZSOZSO each. Track the current trustline count on Stellar Explorer.