Support NFT collections minted in both Ethereum Layer 1 and Loopring Layer 2
Last updated
Was this helpful?
Last updated
Was this helpful?
A full set of NFTs is typically associated with a smart contract, but if the contract is customizable, the interface IL2MintableNFT is required to support minting from both Ethereum L1 and Loopring L2. (for example, one batch of NFTs will be minted from L1, and the other batch will be minted from L2).
The collection_metadata field in the NFT metadata part needs to be implemented correctly to ensure the NFT (whether it's minted directly from Loopring L2 or minted from Ethereum L1 and then deposited to Loopring L2) can be properly categorized in the desired collection in Loopring L2.
For more information regarding collections on L2, please refer to .
Meanwhile, unlike Opensea, which binds the creator's royalty information in the collection in Ethereum L1, the royalty information is expected to bind with NFT metadata directly in Loopring L2. For NFTs listed and sold in Loopring L2, the Loopring relayer will automatically distribute the royalty fee to the creator's L2 account for each NFT traded. So, in order for the creator to receive a royalty fee when the NFT is traded on Loopring L2, the creator must ensure
Include the royalty percentage field in the NFT metadata.
Activate the Loopring L2 account of the creator wallet.
Please refer to a detailed explanation of the metadata standard used in Loopring L2 .
Note, if the NFT is an ERC721 token, the user may mint one NFT in L1 while still being able to mint the same NFT (same tokenID) in L2; and vice versa. Since there is already one NFT in L1, the one in L2 will not be able to withdraw to L1. This is referred to as "twin coexistence".
It is the responsibility of the NFT project owner to ensure that this does not occur, or else the NFT owner will suffer asset loss.