Summary

It is well explaind that the bridge is currently functional for only whitelisted NFTs and in future there is a possiblity that more NFT projects will get whitelisted, Implementing NFTs that comply with both ERC721 and ERC1155 standards can lead to functional conflicts due to differences in how these standards handle token transfers.

Vulnerability Details

A dual-standard NFT contract might mistakenly handle a token as ERC721 when it should use ERC1155 logic, especially for batch operations. This happens if the contract checks for ERC721 compliance before ERC1155, in a result detectInterface() function will return true but the token can be 1155.

Impact

This mismanagement could result in incomplete transactions or incorrect token handling or maybe tx failures.

Tools Used

Manual Code Review

Recommendations

To avoid such issues, always check for ERC1155 compliance first in your contracts when handling dual-standard tokens.