Artifact claim
Content claim
Different adapters, same proof record.
Sigstore and C2PA evidence each resolve into the same Proofnet packet shape. A verifier does not need to understand upstream service internals to replay the record.
{
"type": "proofnet_artifact_provenance_packet_v0",
"attesto_type": "artifact_provenance",
"identity_layer": {
"sigstore": { "signer_subject": "mailto:release@blockietalkie.co", "signer_digest": "sha3-512:9db0...1a46", "rekor_inclusion": "verified" },
"c2pa": { "producer": "Blockie Talkie LLC", "manifest_digest": "sha3-512:57ee...ffc8f", "assertions": "valid" }
},
"artifact_digest": "sha3-512:3f2a...c814",
"proofnet_pq_algorithm": "ML-DSA-87",
"canonical_digest": "SHA3-512",
"native_record": "proofnet_memory_block_first",
"optional_external_anchor": "bitcoin",
"public_safe": true
}
A build artifact without a signer is just a file.
Signer identity
The signer is validated as an identity under Proofnet AttestoBind before the artifact is accepted.
Artifact state
The artifact digest and release metadata are canonicalized into an accepted record.
PQ binding
SHA3-512 digest, ML-DSA-87 signature, identity-bound provenance record.
Durable proof
Memory Blocks preserve the record; Bitcoin anchoring is optional and opt-in.