Hacker News new | ask | show | jobs
by jrochkind1 1318 days ago
So, like I said, I'm an outsider, I don't know what ERC721 or EVM or Solidity are.

I'm just someone from the outside saying, from the actual current popular use cases of NFT, it seems really a mis-match between design and use-case not to have a digest fingerprint, right? What confuses me if that, from your comment it seems like the "community" does not agree... or perhaps thinks this is somehow an insoluble problem?

If it's totally arbitrary what the payload is, like it doesn't even have to be a URL, but URLs seem quite popular... okay, how about putting in eg `https://example.com/some/url#sha512=a1bd4ef`

Marketplaces could put a special tag on items that supplied digests, the marketplace could even check it and confirm it. No change to standard needed. (Since I know nothing about what I'm talking about, it's possible I have some details wrong, but surely something along these lines is possible? This does not seem like a sophisticated technological problem, to embed a digest in a recognizable way)

If it's not being done, it would seem like there isn't sufficient interest in it? That is what confuses me.

1 comments

OpenSea already does tag NFTs as having "Centralized" or "Frozen" metadata, verifying the URI as you say. ERC721 spec only deals with EVM and Solidity, where it would not make sense to try and force the token contract URI state to match a specific hosting protocol.