Cameras, phones and image generators increasingly embed C2PA Content Credentials in the files they produce. A credential is a signed manifest that records how a file was made, including whether it came from a camera or an AI model.
Almost every fediverse server re-encodes uploads, and re-encoding strips the manifest. By the time a post federates, the information is gone.
This proposal adds two properties to attachments: digitalSourceType, and a small contentCredentials summary of what the publishing server found when it validated the upload. It also describes how a server can sign its own resized copy so the chain survives for anyone who wants to check it themselves.
The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this specification are to be interpreted as described in [RFC-2119].
An attachment MAY have a digitalSourceType property. The value is a term URI from the IPTC Digital Source Type vocabulary [IPTC-DST], which is the vocabulary C2PA uses.
The value can come from a C2PA manifest or from the author. When it comes from a manifest, the publisher looks at the whole ingredient chain:
c2pa.created action has trainedAlgorithmicMedia, use trainedAlgorithmicMedia.compositeWithTrainedAlgorithmicMedia.c2pa.created action, if there is one.Receivers SHOULD show attachments with trainedAlgorithmicMedia as AI generated, and compositeWithTrainedAlgorithmicMedia as AI modified.
A receiver MUST NOT drop an AI label because contentCredentials is missing or Invalid. A wrong AI label costs little. A missing one is the problem this proposal exists to fix.
An attachment MAY have a contentCredentials object. It describes the C2PA manifest the publishing server validated on the original upload.
validationState (REQUIRED): Invalid, Valid or Trusted, following the validation states in [C2PA] section 14.3. Trusted means the signing certificate chained to the publisher’s trust list.signer (OPTIONAL): the issuer of the signing certificate, usually an organization name.claimGenerator (OPTIONAL): the name of the software that created the active manifest.A publisher MUST only include contentCredentials when it validated the manifest itself. It MUST NOT pass along a value it received from another server.
A receiver MUST treat contentCredentials as a claim made by the publishing server. What Trusted means depends on that server’s trust list.
Publishers SHOULD NOT copy anything else from the manifest. Manifests often carry EXIF with location data, and identity assertions that the author may not expect to be republished.
A server that re-encodes an upload MAY sign the new file with its own manifest. The manifest uses the original upload as its parentOf ingredient and records what changed, for example c2pa.resized and c2pa.transcoded. Because the parent manifest is embedded, validators can still see the camera or tool that made the original.
Before embedding the parent manifest, the server SHOULD redact assertions that can hold personal data, at least stds.exif and c2pa.metadata ([C2PA] section 6.8). A server that can’t redact SHOULD NOT embed a parent manifest that contains them.
A signed file MUST NOT be modified afterwards, for example by a lossless optimizer, since any change breaks the hard binding.
Receivers MAY fetch the attachment and validate the embedded manifest themselves. If they do, their own result replaces contentCredentials.
{
"@context": [
"https://www.w3.org/ns/activitystreams",
{
"digitalSourceType": {
"@id": "https://w3id.org/fep/5837#digitalSourceType",
"@type": "@id"
},
"contentCredentials": "https://w3id.org/fep/5837#contentCredentials",
"validationState": "https://w3id.org/fep/5837#validationState",
"signer": "https://w3id.org/fep/5837#signer",
"claimGenerator": "https://w3id.org/fep/5837#claimGenerator"
}
],
"id": "https://pixelfed.example/p/alice/123",
"type": "Note",
"attributedTo": "https://pixelfed.example/users/alice",
"content": "<p>Made with an image model, then cropped</p>",
"attachment": [
{
"type": "Document",
"mediaType": "image/jpeg",
"url": "https://pixelfed.example/storage/m/abc123.jpg",
"name": "A lighthouse at night",
"digitalSourceType": "http://cv.iptc.org/newscodes/digitalsourcetype/trainedAlgorithmicMedia",
"contentCredentials": {
"validationState": "Valid",
"signer": "Example Labs",
"claimGenerator": "Example Image Studio"
}
}
]
}
CC0 1.0 Universal (CC0 1.0) Public Domain Dedication
To the extent possible under law, the authors of this document have waived all copyright and related or neighboring rights to this work.