Topics · Domain workflow

Creators and rights

Rights reviewers can compare circulating material to the signed creation record and see whether the later file still belongs to that trail.

Concrete scenario

What this looks like in practice

An illustrator releases a work online. Months later a model output closely matches the style and composition. The illustrator still has the project file but the platform post was deleted. They need a signed record of the original version and terms — not a screen shot battle.

Problem

What breaks today

Creative work now travels straight into remix systems, training sets, and repost networks. Artists need proof that a specific version existed before the copy, scrape, or model output arrived.

Mechanism

How ZK-SNAP responds

Creation events mint receipts binding version roots, rights claims, fingerprints, and optional disclosure paths at publish time. Portable credentials and on-log recognition can compose when profiles require governed witness without publishing full source files or studio internals.

Verifiable outcome

What a verifier can check

Creation-time fingerprint matches the archived or circulating candidate file.
Rights and licensing claims are part of the signed inputs_root commitment.
Offline validity holds even if the publishing platform account is gone.
On-log recognition is verified only when Chain inclusion evidence is supplied.

Related profiles and labels

Creation recordMedia trailPortable proof

Scope boundary

What a receipt does not replace

Receipts document signed creation facts — not automatic copyright registration, platform takedown enforcement, or legal outcomes without applicable law and process.

Go deeper

Try the workflow, then read the spec.

Use Cases tells the story with cards. Proof Lab runs create and verify locally. Protocol holds the normative reference.

Use Cases Proof Lab How it works