Skip to content

Guide for deploying a non-native Cadence contract & updating legacy association #162

Description

@sisyphusSmiling

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.

Metadata

Metadata

Labels

DocumentationImprovements or additions to documentation

Type

Projects

Status
✋ Blocked
Status
Todo

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions