TokenBridge
GitHubSmart Contracts
Search…
Welcome
About TokenBridge
Features, Definitions and Modes
Components
Use Cases
Security Audits
Roadmap
Arbitrary Message Bridge (AMB)
About the AMB
Arbitrary Message Bridge Deployment
Development of a cross-chain application
ERC677 to ERC677 AMB bridge extension
😸
CryptoKitties AMB bridge extension Demo
Create a Burner Wallet plugin for your AMB bridge extension
xDai Bridge
About the xDai Bridge
Using the xDai Bridge
xDai Bridge Contracts Management
xDai Bridge oracle maintenance
Trial bridge
ETH-XDAI AMB
About the ETH-xDai AMB
🌉
OmniBridge Extension
NFT OmniBridge extension
ERC20-to-ERC20 extension linked with a particular token
BSC-xDai AMB
About the BSC-xDai AMB
OmniBridge Extension
RINKEBY-XDAI AMB
About the Rinkeby-xDai AMB
AMB Live Monitoring application
MOON bridge extension
BRICK bridge extension
NFT OmniBridge extension
POA-XDAI AMB
About the POA-xDai AMB
OmniBridge Extension
Kovan-Sokol AMB
About the Kovan-Sokol AMB
OmniBridge extension (testing)
NFT extension (testing)
Native-to-ERC20 bridge extension
ETH-BSC AMB
About the ETH-BSC AMB
OmniBridge Extension
ETH-POA AMB
About the ETH-POA AMB
ETH-ETC AMB
About the ETH-ETC AMB
WETC AMB extension
ETH-QDAI AMB
About the qDai chain
About the ETH-qDai AMB
qDai bridge extension
Using the qDai Bridge
ETH-BNC Bridge
About ETH-BNC bridge
Demo: ETH-BNC bridge
Creating a Local Binance DEX Testnet
Media
Contact Us
Media Kit
Social Media
Powered By GitBook
NFT OmniBridge extension
Technical details about the NFT OmniBridge AMB extension deployed on top of AMB between the Rinkeby testnet and the xDai chain
This is a beta version of the NFT OmniBridge AMB extension. The extension allows users to transfer any non-fungible tokens implemented through ERC721 and EIP1155 compatible token contracts from one chain to another.
The main idea of this bridge is to allow owners of NFTs on the xDai chain to test compatibility of the tokens on test version of the market place OpenSea.

Technical details

The extension works with tokens originally deployed on either side of the bridge. It uses the mirroring concept:
  1. 1.
    A non-fungible token is locked on one side of the bridge - the OmniBridge mediator contract becomes the owner of the token. For EIP1155 tokens it is possible to send several tokens at once.
  2. 2.
    The new token is minted on the other side of the bridge with the same Token ID and TokenURI. The owner of the new token is by default set to the same account that sent the token to the bridge in the originating transaction (an alternative receiver feature can be used to specify another token owner). The only thing that can be changed in the bridged token is the owner. No other data like the Token URI can be updated on chain.
  3. 3.
    If the token is bridged back, it is burned and the token with the corresponding Token ID is unlocked on that side of the bridge where the token originated.
A bridged NFTs uniqueness is provided by making a correspondence between the originating token contract and the contact which appears during the transfer of the first token from this contract. An example:
  • Consider an ERC721 contract A that has an NFT with ID 1. The bridging of this token causes the deployment of a new contract A* and minting of an NFT with ID 1. If later the token with the ID 1 of another ERC721 contract B is transferred through the bridge, a contract B* will be deployed so the token 1 of the contract A* and the token 1 of the contract B* maintain their uniqueness.

Deployment information

RINKEBY-XDAI AMB - Previous
BRICK bridge extension
Next - POA-XDAI AMB
About the POA-xDai AMB
Last modified 5mo ago
Export as PDF
Copy link
Contents
Technical details
Deployment information