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.

Sign up for GitHub

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

Jump to bottom

EIP-722: update introduction #4484

Merged
merged 1 commit into from
Nov 23, 2021
Merged

EIP-722: update introduction #4484

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion assets/eip-722/eip-722.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ Allow everyone migrate token URI

### Introduction

Hi, I see, I see almost NFT applications are using ERC721, so after the NFT start-up trend, there will be many companies that run out of capital and dissolve. At that time they will shutdown their servers and many of the images associated with the NFT will be inaccessible. Should we need create a contract that allows the holder to update the image URI.
Hi, I see almost NFT applications are using ERC721, so after the NFT start-up trend down, there will be many companies that run out of capital and dissolve. At that time they will shutdown their servers and many of the assets (images, videos, ...) associated with the NFT will be inaccessible. Should we need create a contract that allows the holder to update the image URI.

### Contract Interface

Expand Down