iMULEiMULE
Burn · verify · mint or reissue

BRIDGE

The iMULE bridge moves supply instead of duplicating it. A confirmed burn on the origin network authorizes the corresponding creation on the destination network.

V1: assisted bridge with operator verification
WAVES → UNIT0

Burn then mint

  1. User burns official iMULE on WavesThe transaction must use asset F96NaUxy…Dqm6i.
  2. Bridge verifies the chain transactionAsset, sender, amount, destination and duplicate-processing protection are checked.
  3. Authorized Unit0 operator calls bridgeMint()The ERC-20 contract creates the exact atomic amount for the destination address.
  4. Request is completedThe Waves transaction ID is permanently marked as processed by the Unit0 contract.
UNIT0 → WAVES

Burn then reissue

  1. User calls bridgeBurn()Tokens are destroyed on Unit0 and the Waves recipient is recorded in the call.
  2. Bridge verifies the Unit0 receiptContract, burn event, amount and recipient data are decoded from the transaction.
  3. Waves issuer reissues the amountOnly the issuer account can sign a Waves reissue transaction.
  4. Reissued tokens are transferredThe issuer sends the exact amount to the user and the request is finalized.

What the contracts guarantee

Unit0 access control

Only an address holding BRIDGE_ROLE can call bridgeMint().

Duplicate protection

The same Waves transaction ID cannot authorize two Unit0 mints.

Local maximum

The Unit0 contract cannot exceed its encoded 50 billion local cap.

Public burns

Any holder can burn their own Unit0 tokens through bridgeBurn().

What remains off-chain

The Unit0 contract cannot read Waves directly, and Waves cannot read Unit0 directly. The bridge service verifies the other network, tracks each operation and enforces the global supply policy.

Important: the current Unit0 contract accepts the Waves recipient as a string and does not validate a Waves checksum on-chain. Use the official interface, which validates the address before submitting the irreversible burn.

Current operating model

  • User starts and signs the burn.
  • Public blockchain data is independently verified.
  • Mint/reissue uses a dedicated authorized wallet.
  • Each origin transaction is processed once.
  • Requests and destination hashes are recorded.
Open Bridge in App