You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This guide should cover the planning, development, deployment and registration of a NonFungibleToken contract intended to replace an existing bridged NFT. A project in this scenario will have an existing EVM-native NFT that has been onboarded to the bridge and desire to update the bridged NFT association with their own NonFungibleToken implementation. The end result is their EVM-native ERC721 will be bridged as their self-deployed Cadence NFT and vice versa.
The text was updated successfully, but these errors were encountered:
This guide should cover the planning, development, deployment and registration of a NonFungibleToken contract intended to replace an existing bridged NFT. A project in this scenario will have an existing EVM-native NFT that has been onboarded to the bridge and desire to update the bridged NFT association with their own NonFungibleToken implementation. The end result is their EVM-native ERC721 will be bridged as their self-deployed Cadence NFT and vice versa.
The text was updated successfully, but these errors were encountered: