Skip to main content

Bridge Module

Bidirectional mapping and migration connecting legacy ecosystems to modern Avalanche architecture using threshold consensus.

The Migration Challenge​

Faded Monsuta operates an active, multi-year economy that originated on WAX. Moving an ecosystem of this scale (fungible tokens and 100,000+ unique NFTs) to a new settlement chain requires extremely highly available, decentralized, and un-ruggable bridging solutions.

The Bridge Module comprises two distinct, independently deployed systems:

  1. The Token Bridge: Facilitates the bidirectional transfer of fungible governance and economic tokens (THC).
  2. The NFT Bridge: Secures, maps, and translates complex non-fungible digital assets reliably between structurally different blockchain environments.

Token Bridge Architecture​

The Token bridge facilitates instantaneous migrations between WAX and Avalanche C-Chain. Because fungible tokens are essentially numbers on a ledger, this bridge operates safely via a classic Burn/Mint & Lock/Release dynamic depending on the direction.

The Flow​

  • WAX → Avalanche: Tokens are locked permanently in the origin WAX contract. An Oracle node detects the transaction, signs a strictly typed payload, and provides it to the player. The player calls claim() on Avalanche, which programmatically mints the exact amount to their wallet.
  • Avalanche → WAX: The player initiates a teleport() on Avalanche. The Avalanche contract actively burns the tokens from existence. An Oracle node watches for the Teleport event, waits for block finality, and then triggers the WAX contract to release matching locked tokens.

NFT Bridge Architecture​

Migrating 100k+ Player NFTs necessitates a completely different architectural approach. NFTs are inherently non-fungible — you cannot simply burn them on one chain and mint them on another without destroying their distinct historical data and generating immense risk if a cross-chain transmission drops.

The NFT Bridge leverages a Vault mechanism to solve this.

  • Vaulting: NFTs are strictly physically locked inside a bridge contract, functioning as an escrow vault. They are never burned.
  • Mirroring: The destination chain validates the locked asset and mints an absolute replica using specialized Bitwise numbering systems that mathematically map to the origin asset.
  • Returning: Should the player ever trigger a return bridging action, the mirrored asset is locked down, and the original asset is simply unlocked from the origin vault.

Read the full NFT migration architecture →

Oracle Consensus Network​

Both bridge modules reject centralized command structures. Relaying events and issuing minting attestations is handled by a detached Oracle cluster.

Currently running as Node.js PM2 processes, the cluster leverages asynchronous polling against both origin and destination nodes.

  1. oracle-eth.js / oracle-eos.js: Listens for fungible asset locks and burns. Triggers actions on the opposite chain.
  2. nft-oracle-wax.js / nft-oracle-avax.js: Listens for non-fungible asset locking, queries origin mapping registries, and dynamically generates the exact EIP-712 translation signature required to replicate the asset on Avalanche.

Enterprise Security Standard​

  • Both Token and NFT bridges operate under strict cryptographic Threshold Consensus. A single compromised oracle node cannot perform arbitrary mints.
  • The threshold config limits single points of failure, verifying payloads across $M$ out of $N$ actively registered signer addresses.
  • The DOMAIN_SEPARATOR parameter inherently prevents cross-chain replay attacks. A signature intended for Fuji Testnet evaluates as mathematically invalid on C-Chain Mainnet.