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 an ERC721 contract intended to replace an existing bridged ERC721. A project in this scenario will have an existing Cadence-native NFT that has been onboarded to the bridge and desire to update the bridged ERC721 association with their own ERC721 implementation. The end result is their Cadence-native NFT will be bridged as their self-deployed ERC721 and vice versa.
The text was updated successfully, but these errors were encountered:
This guide should cover the planning, development, deployment and registration of an ERC721 contract intended to replace an existing bridged ERC721. A project in this scenario will have an existing Cadence-native NFT that has been onboarded to the bridge and desire to update the bridged ERC721 association with their own ERC721 implementation. The end result is their Cadence-native NFT will be bridged as their self-deployed ERC721 and vice versa.
The text was updated successfully, but these errors were encountered: