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
Add the two views proposed in FLIP 318 - EVMPointer and EVMBytesMetadata.
Since adding these views to the standard MetadataViews would result in a circular dependency (EVM > MetadataViews > FlowToken > EVM), these views will need to be added to an alternate contract. While unfortunate and might normally result in reduced adoption, these views are ultimately only used by the bridge when moving NFTs between Cadence & EVM. Since the implementation of these views are a hard requirement for metadata to be passed into EVM, they will be leveraged in any documentation, guides and examples demonstrating dual VM deployment and can be assumed developers would see their documented use in the process of writing their contracts.
The text was updated successfully, but these errors were encountered:
Related: onflow/flips#318
Description
Add the two views proposed in FLIP 318 -
EVMPointer
andEVMBytesMetadata
.Since adding these views to the standard
MetadataViews
would result in a circular dependency (EVM > MetadataViews > FlowToken > EVM
), these views will need to be added to an alternate contract. While unfortunate and might normally result in reduced adoption, these views are ultimately only used by the bridge when moving NFTs between Cadence & EVM. Since the implementation of these views are a hard requirement for metadata to be passed into EVM, they will be leveraged in any documentation, guides and examples demonstrating dual VM deployment and can be assumed developers would see their documented use in the process of writing their contracts.The text was updated successfully, but these errors were encountered: