Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Guide for deploying a non-native EVM contract & updating legacy association #161

Open
sisyphusSmiling opened this issue Jan 27, 2025 · 0 comments
Assignees
Labels
Documentation Improvements or additions to documentation

Comments

@sisyphusSmiling
Copy link
Contributor

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.

@sisyphusSmiling sisyphusSmiling added the Documentation Improvements or additions to documentation label Jan 27, 2025
@sisyphusSmiling sisyphusSmiling self-assigned this Jan 27, 2025
@sisyphusSmiling sisyphusSmiling moved this to 🧊 Backlog in 🌊 Flow 4D Jan 29, 2025
@sisyphusSmiling sisyphusSmiling moved this from 🧊 Backlog to ✋ Blocked in 🌊 Flow 4D Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation Improvements or additions to documentation
Projects
Status: Todo
Status: ✋ Blocked
Development

No branches or pull requests

1 participant