The NFT is only unique within the contract address. The whole contract can be trivially copied to another contract address and the whole collection can be cloned. It’s why opensea has checkmarks for “verified” collections. There are a unofficial BoredApe collections which are copies of the original one.
Completely agree, but the guy I responding to thinks the monkey jpeg is unique across the whole blockchain, when that isn’t true. The monkey jpeg can be copied. There’s no uniqueness enforced in a blockchain.
Right, it’s a link to the JPEG. Either way, the point still stands, there’s no mechanism in the blockchain to prevent duplicate content or enforce uniqueness of what the NFT points to. The NFT token is unique within its contract, sure, but that doesn’t stop someone from deploying a near-identical contract with the same media and metadata. That’s the issue, the blockchain doesn’t know or care if the same JPEG is being reused in other collections.
The NFT token is unique within its contract and since the contract had a unique address the NFT pointer is unique. Include chainID in the description and the NFT is globally unique.
That’s true, the (chainID, contractAddress, tokenID) can be globally unique. But that doesn’t solve the original concern, it doesn’t prevent content duplication.
The method for unique content is to reference the chainID, Address and token number in the content itself (I.e. in a metadata field). This approach works well for legal documentation, but could equally be applied to monkey pictures (although it usually isn’t).
Sure, you can establish a stronger tie between the token and the file by embedding the chain ID, contract address, and token number in the content or metadata, but there’s no way to enforce that tie at the blockchain level. Anyone can still mint a copy with different metadata on a different contract.
As for legal documents, while storing them on-chain might help with transparency or timestamping, the blockchain itself has no legal jurisdiction. It doesn’t have legal authority, and documents stored this way are not inherently compliant with local laws, so they’re unenforceable unless recognized by a traditional legal system.
The NFT is only unique within the contract address. The whole contract can be trivially copied to another contract address and the whole collection can be cloned. It’s why opensea has checkmarks for “verified” collections. There are a unofficial BoredApe collections which are copies of the original one.
Yes, the URI can point to the same monkey jpg. But a different contract address means it is a different NFT.
Completely agree, but the guy I responding to thinks the monkey jpeg is unique across the whole blockchain, when that isn’t true. The monkey jpeg can be copied. There’s no uniqueness enforced in a blockchain.
The key point is that the jpeg is not the NFT
Right, it’s a link to the JPEG. Either way, the point still stands, there’s no mechanism in the blockchain to prevent duplicate content or enforce uniqueness of what the NFT points to. The NFT token is unique within its contract, sure, but that doesn’t stop someone from deploying a near-identical contract with the same media and metadata. That’s the issue, the blockchain doesn’t know or care if the same JPEG is being reused in other collections.
The NFT token is unique within its contract and since the contract had a unique address the NFT pointer is unique. Include chainID in the description and the NFT is globally unique.
That’s true, the (chainID, contractAddress, tokenID) can be globally unique. But that doesn’t solve the original concern, it doesn’t prevent content duplication.
The method for unique content is to reference the chainID, Address and token number in the content itself (I.e. in a metadata field). This approach works well for legal documentation, but could equally be applied to monkey pictures (although it usually isn’t).
Sure, you can establish a stronger tie between the token and the file by embedding the chain ID, contract address, and token number in the content or metadata, but there’s no way to enforce that tie at the blockchain level. Anyone can still mint a copy with different metadata on a different contract.
As for legal documents, while storing them on-chain might help with transparency or timestamping, the blockchain itself has no legal jurisdiction. It doesn’t have legal authority, and documents stored this way are not inherently compliant with local laws, so they’re unenforceable unless recognized by a traditional legal system.