Live Protocol Demo

Prove who made the video. Even after the internet does its worst.

Deepfakes are everywhere. Metadata gets stripped on every upload. Attestik embeds cryptographic identity inside the video stream itself — so it survives re-encoding, re-muxing, and social platform processing. No plugins. No trust chain. Just math.

The Problem

Every existing solution breaks the moment someone shares your video.

Metadata gets stripped

YouTube, Twitter, Instagram, TikTok — every platform re-encodes uploads and strips container metadata. C2PA provenance data is gone before anyone sees it.

Deepfakes are cheap

Anyone can generate a convincing fake in minutes. Without a way to verify the original creator, there is no trust — just pixels.

Watermarks are fragile

Visual watermarks get cropped. Invisible watermarks break on transcoding. Neither proves who created the content or when.

How Attestik Works

Five layers of cryptographic binding, embedded at the codec level. No container dependency. No external service required at verification time.

1

Sign

Generate an Ed25519 keypair. Your entity ID is derived from your public key. Every video segment gets individually signed with your secret key.

120-800 bytes per segment. Orders of magnitude smaller than C2PA.

2

Bind

Content hashes at five levels (bitstream, codec, perceptual, spatial block grid, audio fingerprint) link your identity to the actual media. A hash chain links segments together.

L1-L3 detect global changes. L4 catches localized edits. L5 detects audio tampering.

3

Verify

Anyone can verify: extract the attestation, check the signature, and confirm the content binding. No API call needed — it's all in the stream.

Works offline. No phone-home. No trust chain to expire.

Who Needs This

Anyone who needs to prove a video is real, unaltered, and from who it claims.

Newsrooms & Journalists

Prove footage is authentic before publishing. Attestik identity survives the entire editorial pipeline — transcode for broadcast, upload to social, syndicate to partners. The cryptographic proof stays with the video.

Trust at the source

Creators & Studios

Protect your originals. When someone re-uploads your video, the attestation proves you made it first. Works across every platform because the identity lives inside the stream, not the container metadata.

Proof of authorship

Legal & Compliance

Bodycam footage. Depositions. Surveillance. Attestik provides a cryptographic chain of custody: who recorded it, when, and whether any frame has been altered since. Admissible proof, not just a filename.

Chain of custody

Platforms & CDNs

Verify content provenance at ingest without calling an external API. Flag AI-generated content, confirm creator identity, and surface trust signals to viewers — all from the stream itself.

Ingest verification

Under the Hood

The technical details for developers and security teams.

5-Level Binding

L1 bitstream, L2 codec, L3 perceptual, L4 spatial block grid, L5 audio fingerprint. Each survives different transforms.

120-800 Bytes

Attestation frames are tiny. Embed identity in real-time streams with negligible bandwidth overhead.

Platform Resilient

Survives re-muxing, transcoding, and social upload. Identity travels inside the H.264/H.265 stream.

Ed25519 Signatures

Every segment individually signed. Hash chain links segments cryptographically. Offline verification.

Attestik vs. C2PA

C2PA stores provenance in the file container. Every platform in the delivery chain destroys it. Attestik binds identity to the content itself.

OperationC2PAAttestik
Re-mux (MP4 to MKV)Metadata destroyedL1 bitstream hash matches
Transcode to 720pMetadata destroyedL3 perceptual hash + L4 block grid survive
Upload to social platformMetadata destroyedL3 pHash + L4/L5 survive re-encode
Strip SEI NAL unitsMetadata destroyedIdentity signal deleted
CDN edge cachingOften stripped by CDNTravels inside the stream

Explore the Protocol

Interactive demos showcasing every layer of the Attestik protocol.

See it break. See it survive.

Upload a video, stamp it with your identity, then attack it — re-mux, transcode, simulate a social upload. Watch what happens to the attestation.

Try the Live Demo