Open hats-bug-reporter[bot] opened 2 months ago
Thank you for your report regarding the unchecked metadata. After review, we've determined that this is not an issue. The metadata you're referring to is intentionally stored off-chain. As such, the smart contracts cannot and are not designed to verify the content of this metadata. The responsibility for ensuring the validity and appropriateness of this content lies with the off-chain systems and users interacting with it. We appreciate your attention to potential vulnerabilities in our system. Your report helps us ensure that our design choices and their implications are clearly understood. Thank you for contributing to the security and transparency of our platform.
Github username: -- Twitter username: -- Submission hash (on-chain): 0x49d65c7b7540d979ae4e8f41c2f6a612ce0bd583ce027661ca848edd2f218e17 Severity: low
Description: Whenever a user calls
registerHuman
he is able to specify_metadataDigest
, as the function comments state:However when used, the function does not perform a check to make sure that the
_metadataDigest
follows the ERC1155 standard.This issue has previously been mentioned in this report:
And as per the EIP-1155 it states that the metadata MUST comply to certain bullet points.
As it stands now, registering a human with a metadata that is non-ERC1155 standard remains possible.
Recommendation
introduce some logic that prevents this