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
To support NFT migrations (in the case of an updated cross-VM association), this transaction will allow a signer to effectively swap a bridge-defined NFT for a project-defined NFT. This will require at least two transactions distinguished by the native VM of the underlying NFT.
In the case of a Cadence-native NFT where the signer owns the bridged ERC721, the transaction should bridge the ERC721 from EVM and back into EVM, resulting in the signer owning the project-specified ERC721.
On the other hand in the case of an EVM-native NFT where the signer owns the bridged Cadence NFT, the transaction should bridge the NFT to EVM and back from EVM, resulting in the signer owning the project-specified Cadence NFT.
The text was updated successfully, but these errors were encountered:
To support NFT migrations (in the case of an updated cross-VM association), this transaction will allow a signer to effectively swap a bridge-defined NFT for a project-defined NFT. This will require at least two transactions distinguished by the native VM of the underlying NFT.
In the case of a Cadence-native NFT where the signer owns the bridged ERC721, the transaction should bridge the ERC721 from EVM and back into EVM, resulting in the signer owning the project-specified ERC721.
On the other hand in the case of an EVM-native NFT where the signer owns the bridged Cadence NFT, the transaction should bridge the NFT to EVM and back from EVM, resulting in the signer owning the project-specified Cadence NFT.
The text was updated successfully, but these errors were encountered: