BUG: Original NFT data is modified after IBC transfers about gon-evidence HOT 2 OPEN

Another case: NFT not updatable, can be modified via ICS721

An NFT from a collection created with --update-restricted=true, cannot be modified, if you try to edit (iris tx nft edit), you receive the error message:

failed to execute message; message index: 0: nobody can update the NFT under this denom disperze02: unauthorized

but if you transfer to custom remote chain, you can return new data, and modify the original NFT.

from gon-evidence.

Another case: NFT not updatable, can be modified using ICS721

An NFT from a collection created with --update-restricted=true, cannot be modified, if you try to edit (iris tx nft edit), you receive the error message:

failed to execute message; message index: 0: nobody can update the NFT under this denom disperze02: unauthorized

but if you transfer to custom remote chain, you can return new data, and modify the original NFT.

First of all many thanks, this issue is known.

1. For the ics721 protocol, it does not stipulate whether the data of nft can be modified, which depends on the application layer implemented.
2. From the perspective of iris, --update-restricted=true, it is true that the data of nft should not be modified. At that time, only things at the ics721 protocol level were considered. Therefore, in the subsequent release of the main network, this should be implement.

from gon-evidence.