life-itself / life-itself/web3

NFT Authenticity vs Plagarism

Open
#106 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
1.9k
Forks
213
PR merge metrics
No merged PRs in 30d

Description

The NFT page states:

> Since multiple NFTs can be created that reference the same artwork there is n canonical guarantee of uniqueness that an NFT purchased is "authentic" and it remains unclear what "authentic" would mean regarding hyperlinks which are infinitely reproducible.```

This seems to be unaware of the paragraph immediately following, which acknowledges the source of such authenticity (by explaining the existence of NFTs which would be considered inauthentic):

> Given the duplication problem above, many artists have critized NFT sales that involve plagarized versions of art whereby a [pseudonymous](https://web3.lifeitself.us/concepts/pseudonymous.md) party will "steal" or reference the work of another when deploying the [smart contract](https://web3.lifeitself.us/concepts/smart-contracts.md) allowing the third party to potentially profit off the work of another with no attribution or royalties paid to the original artist.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the NFT page, especially the quoted authenticity paragraph and the paragraph immediately following it. Check whether the two paragraphs clearly explain how plagiarism and attribution relate to NFT authenticity, then revise the wording so that relationship is unambiguous. Done means the page accurately reflects the distinction without contradicting itself.

Written by the indexing model from the issue text.

Assessment

Tech stack
blockchain
Domain
blockchain, documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.