iMULEiMULE
Public technical reference · registry version 1

DOCUMENTATION

This page is the human-readable source of truth for official iMULE chain representations. Contract code may preserve historical constants; this registry identifies the assets currently recognized by the ecosystem.

1. Identity

ProjectiMULE
Token symbolIMULE
Decimals8
Global maximum50,000,000,000 iMULE
OriginWaves
Active networksWaves and Unit0

2. Official networks

Waves

Asset ID: F96NaUxyBP8jWqDeL37KDDYBtja8ecLi9p2DjWqDqm6i
Mode: burn / reissue
Initial supply: 49,999,899,900
Reissuable: true

Unit0

Contract: 0x52Ae39A8CC74BCF8b8abfa372a817151DE5e870a
Chain ID: 88811
Mode: mint / burn
Initial accounted supply: 100,100

The Unit0 contract was deployed before the Waves migration. Its public constant names the legacy Waves asset, but that value is not used inside bridgeMint(). The official bridge service recognizes the new Waves Asset ID listed above.

3. Supply accounting

No network is independently entitled to issue 50 billion tokens. That number is a global ceiling. Every bridge creation must correspond to a confirmed destruction on another official network, except the documented initial Unit0 allocation.

49,999,899,900 Waves
       100,100 Unit0
--------------------
50,000,000,000 global initial total

4. Bridge architecture

Waves → Unit0: burn on Waves, verify transaction, call bridgeMint() on Unit0.

Unit0 → Waves: call bridgeBurn(), verify receipt, sign Waves reissue with the issuer account, then transfer to the recipient.

The current V1 bridge is operator-assisted. Users sign their burns; an authorized operator or controlled automation executes the destination-side issuance after validation.

5. Known security model

  • The Unit0 mint is restricted by BRIDGE_ROLE.
  • Processed Waves transaction IDs are recorded on-chain to prevent duplicate Unit0 minting.
  • The Unit0 contract is not upgradeable and does not include an on-chain pause mechanism.
  • The Waves recipient string is validated by the official interface and backend, not by the current Unit0 contract.
  • The bridge operator must protect both the Unit0 bridge key and the Waves issuer key.
  • Administrative roles should be moved away from personal hot wallets as the system matures.

6. NFT systems

Waves: compact iMULE codes stored in asset descriptions and rendered by IMULATOR.

Unit0: experimental Solidity NFT contracts for iMULE code, image bytes, chunks and external media. Unit0 is a research environment; supported formats may evolve.