Each track encoded by SynthCamp carries a tamper-proof cryptographic signature that proves three things at once: it really came from SynthCamp, it was uploaded by the named artist, and the Creative Credits the artist declared at attestation time match what you're hearing.
1. Platform key
SynthCamp publishes one Ed25519 public key (with rotation over time). Anyone can fetch the registry and use the key to validate signatures we emit. The platform key is the trust anchor. Without it, nothing below verifies.
2. Artist attestation (per release)
Before a release ships, the artist signs an attestation listing the human contributions and AI tools used. That declaration is timestamped and bound to the release. Changing any of it later invalidates the prior signature and forces the artist to re-sign.
3. Signature on the public preview
When a track is encoded, its public preview MP3 gets an ID3 frame with the signed payload: release and track identifiers, credit category, human contributions, declared AI tools, any upstream C2PA reference, the attestation timestamp, the encode time and the signing key id. The preview is signed again each time the artist signs. Credits are signed for the whole release, even when entered track by track. The signature proves what the artist declared. Whether it is true stays the artist's word. To check one, drop the preview on synthcamp.net/verify, or follow the spec below with any Ed25519 library. The full stream is encrypted: check the preview. SynthCamp does not offer downloads. Playback is streaming-only with DRM.
As a buyer, the green check tells you the track in your library is the same audio the artist signed for. If anyone claimed differently, the signature would catch it.
As a journalist or auditor, you can independently confirm that an audio file came from SynthCamp without trusting our word. Given any SynthCamp-encoded audio in your hands, extract the embedded frame, fetch our public key registry, and verify the signature with any standard Ed25519 library.
As an AI Act conformity check, the embedded marking satisfies article 50 paragraph 2's requirement that AI-generated or AI-modified content be machine-readable.
The two technical artifacts you need are:
Both URLs are stable and intended for scripted access (curl, fetch). The Markdown is served as text/markdown so a verifier can pipe it through a renderer or read it raw.
Provenance is part of SynthCamp's commitment to honest AI attribution. Read the broader policy in our transparency report.