AltLayer Documentation
  • đź‘‹Welcome
    • Overview
  • Restaked Rollups
    • VITAL for Decentralised Verification
      • Tier-1 Finality
      • Tier-2 Finality
      • Tier-3 Finality
    • MACH for Faster Finality
      • Interoperability via MACH
    • SQUAD for Decentralised Sequencing
    • Staking of dApp Token
  • Wizard
    • Introduction
    • Technical overview
    • Create AVS
    • Manage AVS
    • Operator management
    • Hosted operator API (BLS based)
    • Custom AVS specification
      • Constructor specification requirements
      • Import Externally-Deployed AVS
    • Report bug or submit a feature request
  • Autonome
    • Deploy AI Agent
    • Autonome API guide
    • Uploading your own agent framework
    • Twitter/X login troubleshooting guide
  • ♾️AltLayer-Facilitated Actively Validated Services
    • Overview
    • AltLayer MACH AVS
      • Operator Guide
      • User Delegation Guide
    • Cyber MACH AVS for Cyber L2
      • Operator Guide
      • User Delegation Guide
    • DODOchain MACH AVS for DODO Chain
      • Operator Guide
      • User Delegation Guide
    • Fast Finality Layer for Soneium
      • Operator Guide
      • User Delegation Guide
    • Xterio MACH AVS for Xterio Chain
      • Operator Guide
      • User Delegation Guide
  • Upgrade Guide
  • 🥩ALT Restaking
    • Staking Info & Parameters
    • Restake ALT
    • Delegating reALT
    • Check and Claim Staking Rewards
    • Unstake ALT
    • Migration from Xterio (Legacy) ALT Pool to Xterio Restaked ALT Pool
    • Testnet reALT faucet
  • Rollup-as-a-Service
    • What is Rollup-as-a-Service (RaaS)?
    • AltLayer's RaaS Offering
    • RaaS Onboarding Guide
      • Optimism Rollup FAQ
      • Arbitrum Rollup FAQ
    • AltLayer Ecosystem
    • Clients in the Spotlight
    • Pricing Model
  • External Integrations
    • Account Abstraction using Biconomy
    • Enabling permissionless interoperability on AltLayer Rollup with Hyperlane
      • Deplying Hyperlane Warp Routes for ERC20 Token Bridging
      • Running Off-chain Agents
      • Setting up the bridging UI
    • Cross-chain Interoperability using Celer
      • Fungible Token Bridging
      • Non-fungible Token Bridging
      • Generic Message Passing
      • cBridge SDK
  • AltLayer's In-House Rollup Stack in Depth
    • How does AltLayer's in-house rollup stack work?
    • Decentralized Sequencer Set
    • Security via Fraud Proof
  • Rollup Types
    • Flash Layer Rollups
      • Example Use cases
        • NFT Mint Events
        • Games
        • Event Ticketing
    • Persistent Rollups
  • Core Features of AltLayer's In-House Rollup Stack
    • Modular
    • Elastic
    • Multi-VM Support
    • Fraud Proofs
    • Decentralized Sequencers
    • Tiered-Finality
  • FlashLayer Showcase
    • AltLayer's POAP NFTs Collection Mint
      • Performance Test in the Wild
    • Dark Forest Community Round
    • Oh Ottie! NFT Collection Mint
    • Dark Forest Community Round for Jump Crypto's Pit Event
    • Ottie 2048
    • Other demos
      • Fraud Proof Demo
      • Flash Layer Demo
      • Rollup Launchpad Demo
      • FlashGPT Demo
  • Implementation Status
    • Roadmap
    • Development Status
  • Community & Support
    • Community
    • Support
Powered by GitBook
On this page
  • Pegged NFT Bridge
  • Multi-Chain Native (MCN) NFT Bridge
  • Bridging Fee Structure
  1. External Integrations
  2. Cross-chain Interoperability using Celer

Non-fungible Token Bridging

PreviousFungible Token BridgingNextGeneric Message Passing

Last updated 1 year ago

Pegged NFT Bridge

This is intended for existing NFTs that have an origin chain. The architecture is:

  • The contract is deployed on the origin chain, and the contract is deployed on the destination chain.

  • NFTBridge: to lock or release the original NFT

  • PegNFT: to mint or burn the pegged NFT

  • Relayers will be deployed on both the source chain and the destination chain in order to fetch the SGN’s multisig attestations and call the NFTBridge and PegNFT contracts.

When transferring an NFT from the origin chain to the destination chain, the bridge mints a "copy" of the NFT on the destination chain that is pegged to the original NFT on the source chain. In the same style as in Scenario 1 and Scenario 2 of the fungible token transfer, the Pegged NFT bridge process is supported by the Lock-and-Mint and Burn-and-Release models.

Multi-Chain Native (MCN) NFT Bridge

  • Celer’s State Guardian Network (SGN) serves as a message router for cross-chain transfers. It is a Proof-of-Stake (PoS) blockchain built on Tendermint. Validator nodes must stake $CELR to join the consensus process of the SGN.

  • Relayers will be deployed on all chains to fetch the SGN’s multisig attestations and call the MCNNFT contract.

When transferring an MCN NFT from one chain to another, the bridge process is supported by a Burn-and-Mint model. In this way, there is always only one unique and native NFT existing across all chains.

Bridging Fee Structure

This is the same as the Fungible Token Bridging model, the Non-Fungible Token Bridging Fee = Base Fee + Protocol Fee, whereas Base Fee is to cover the destination chain gas cost for minting the NFT and the Protocol Fee is paid to the State Guardian Network (SGN) validators and stakers in return for their services of relaying the bridging message that is passed across the chains. The Protocol Fee is proportional to the message size, determined by the NFT token’s address, the token ID, and the token URL length. In most cases, the Protocol Fee is very low.

Different from the Pegged NFT, the MCN NFT does not have the notion of an “origin chain” or "original NFT". The MCN NFT Bridge only applies to newly deployed NFTs that follow. The architecture is:

The contract is deployed on all chains you would like to bridge the NFT to, this is to burn or mint the NFT.

this template
MCNNFT
NFTBridge
PegNFT