Add EIP: Content Consent for AI/ML Data Mining

[bafu]

Note from an EIP Editor (@Pandapip1)

Please provide feedback at https://ethereum-magicians.org/t/eip-7517-content-consent-for-ai-ml-data-mining/15755. DO NOT provide feedback as a comment of this Pull Request. Feedback should include specifics: what is good about the proposal? What needs changing? Generic messages expressing approval or disapproval may be removed.

---

A proposal adding "miningPreference" in the metadata to preserve the digital content's original intent and respect creator’s rights.

---

This EIP proposes a standardized approach to declaring mining preferences for digital media content on the EVM-compatible blockchains. This extends digital media metadata standards like ERC-7053 and NFT metadata standards like ERC-721 and ERC-1155, allowing asset creators to specify how their assets are used in data mining, AI training, and machine learning workflows.

Motivation

As digital assets become increasingly utilized in AI and machine learning workflows, it is critical that the rights and preferences of asset creators and license owners are respected, and the AI/ML creators can check and collect data easily and safely. Similar to robot.txt to websites, content owners and creators are looking for more direct control over how their creativities are used.

This proposal aims to propose a standardized method of declaring these preferences. Adding "miningPreference" in the content metadata allows creators to include the information about how they want their work whether the asset may be used as part of a data mining or AI/ML training workflow. This ensures the original intent of the content is maintained.

For AI-focused applications, this information serves as a guideline, facilitating the ethical and efficient use of content while respecting the creator's rights and building a sustainable data mining and AI/ML environment.

[eth-bot]

File EIPS/eip-7517.md

Requires 1 more reviewers from @axic, @Pandapip1, @SamWilsn, @xinbenlv

[github-actions]

The commit bab62bd (as a parent of d5ddf3b) contains errors.
Please inspect the Run Summary for details.

[Pandapip1]

This EIP should specify which metadata standards are being extended.

[Pandapip1]

Internal links should be [XXX](./yyy), not [XXX](yyy)

[tammyyang]

Suggest an update for the description to make it more clear.

[bafu]

This EIP should specify which metadata standards are being extended.

@Pandapip1 Thank you for the input. The idea is to make the proposal applicable to any metadata that can describe the ownership and/or copyright of the digital media content, and make the proposal flexible to adopt.

For EIP-721 and EIP-1055, NFT can be used to represent the ownership or license of the associated content (ownership NFT and license NFT). For EIP-7053, onchain registration record can be used to represent the provenance.

Will you suggest mentioning the idea more clearly, or should I narrow it down to the specific EIPs?

[Pandapip1]

This is not the place to provide feedback, and feedback should include specifics: what is good about the proposal? What needs changing?

All of the recent comments are spam; hiding messages. Future feedback messages that don't follow the above requirements will be manually deleted. Future feedback meessages that do follow the above requirements should not be posted here, and instead at the EIP's discussions-to link.

[SamWilsn]

This all reads like Motivation. The Rationale section should justify specific technical choices made within the proposal itself (eg. why you differentiate different types of training, or why your schema permits having the same permission in both allowed and notAllowed). The Motivation section justifies the EIP as a whole.

---

I don't think you need to move this content to motivation, rather update it so that it's clear you're talking about the naming of things, or whatever else has been imported from C2PA.

[Pandapip1]

Also, it's worth noting that C2PA is very flawed--it's been promoted as a digital 'proof of truth', while it's actually just a centralized web of trust that allows governments to have control over what is digitally considered 'true', and the ability to track individuals by which files they edit and share. C2PA's standard is straight up incompatible with Ethereum; I'd highly recommend using another source (this is not a requirement; just a recommendation).

[ProphetZX]

Please remember that in almost every jurisdiction nowadays, a person has the right to their personal data. They may decide to revoke consent to process it, may request their personal data/data porting, may ask for correcting false data or to erase any personal data (e.g. under GDPR/EU law or most cyber law). I myself would never allow for my personal data, out of blockchain data collections for example, to be processed by AI/ML data mining, so not sure this is really fashionable. Just saying…

[ProphetZX]

Any comments or feedback on this?

[SamWilsn]

I am closing this pull request because we are in the process of separating EIPs and ERCs into distinct repositories. Unfortunately, as far as we are aware, GitHub does not provide any tools to ease this migration, so every pull request will need to be re-opened manually.

As this is a PR to create / modify an ERC, I will kindly ask you to redirect this to the new repository at ethereum/ERCs. We have prepared a guide to help with the process.

If there is relevant history here, please link to this PR from the new pull request.

On behalf of the EIP Editors, I apologize for this inconvenience.