Skip to content
ShivaVault Shiva by Blackfish
How it works

One video, from upload to a traced leak

Say a film distributor wants forty festival programmers to watch a new film before it is released. Here is what happens with ShivaVault, step by step.

  1. 1

    The film is uploaded once

    The distributor uploads the film in the console (or their own systems send it). ShivaVault prepares it for streaming, in several sizes so it plays smoothly on a laptop, a tablet or a phone, on a slow or a fast connection.

    At that moment ShivaVault also records a fingerprint of each file it produced and seals it with a timestamp on Ethereum, a public blockchain. Months later, that seal proves exactly which file existed and when, without anyone having to trust ShivaVault's word. (Today the seals go on Ethereum's test network; the permanent network replaces it before the first customer.)

  2. 2

    Each programmer gets their own link

    The distributor creates one viewing per person: who it is for (for example their email address), the text to show on the picture, and how long it stays open, from an hour to a week. Each person receives a link that belongs to them alone.

    The link can also be bound to the person: before playing, it asks for a code sent to their email, and from then on it plays only on the device that entered the code. If they forward it, it plays nothing for anyone else.

  3. 3

    Everyone watches a copy made just for them

    There is no master copy sent to everyone. As each programmer presses play, ShivaVault makes their copy on the fly, a few seconds at a time:

    • their name is written across the picture, so a screen recording shows whose it was;
    • a hidden mark that nobody can see is woven into every frame (on by default), so a copy with the name cut out still says whose it was;
    • tiny variations every two seconds follow a pattern unique to them (on by default, with the hidden mark), so even several copies mixed together point back at the people who mixed them;
    • and, when it is turned on, the stream is encrypted, so what travels over the internet is useless on its own.

    The distributor sees every viewing live: who watched, when, from which places and on which devices.

  4. 4

    Someone tries to copy it, and is noticed

    Downloading a film looks different from watching it: it goes faster than the film itself, grabs every size at once, or uses a download tool. ShivaVault slows any viewing down to a pace that makes copying tedious, notices the signs, tells the distributor in plain words why the viewing looks suspicious and, if the distributor asked for it, switches that viewing off on the spot.

  5. 5

    A copy turns up online, and leads back to one person

    Weeks later, a clip appears on a website. The distributor downloads it and uploads it in the console. ShivaVault looks for its hidden mark and its pattern, without needing the original film, and names the viewing it came from.

    The case file holds the evidence: who the viewing was for, when and from where it was watched, and the Ethereum proof that the viewing existed before the leak was found. From there, the distributor can switch off every viewing that person still has in one click, and take it up with them under their contract.

What it cannot do

  • Nothing stops someone filming a screen with a phone. What ShivaVault does is make that copy lead back to them.
  • A very short or badly damaged clip may not carry enough of the mark to name anyone with confidence. ShivaVault then says so instead of guessing.
  • Viewings play in web browsers today, in our console or in your own website. Phone and TV apps are not supported yet.
  • Some protections are still being completed. The Security page lists each one and how far it is built.

For your technical team

The same journey, in the words engineers use

Upload and encoding
A REST API (v1) with idempotent job creation and signed webhooks; uploads go straight to storage with short-lived write-only grants. Outputs: an HLS ladder, MP4 and snapshots, each with its SHA-256.
Per-viewer delivery
LiveWatermark sessions: each segment is watermarked for its viewer as it is requested, with, on by default, a per-frame forensic mark and A/B variants per 2 s segment. Playback tokens are stored only as SHA-256 hashes and can be revoked within seconds.
Your own player
Shaka Player is verified, and any HLS web player can play an open link, on the origins you allow for each viewing; a small recipient SDK signs the requests of recipient-bound links.
DRM
CMAF with CENC cbcs, a key per viewing, packaged after the watermarks, behind a pluggable licence service; no multi-DRM licence provider is connected yet, and ClearKey stands in on the demo.
Ripping alerts
Explainable rules over the access trail, a per-viewing rate limit, optional automatic revocation and a signed lw.session.flagged webhook.
Anchoring
Every share becomes a salted leaf in a Merkle tree; one root per 10-minute batch goes on Ethereum. Proofs can be verified independently of ShivaVault.
Hosting
Run by Blackfish on Azure, shared or dedicated to you; or installed in your own cloud account. Customer-owned storage (Azure Blob, Amazon S3, Google Cloud Storage, with federated identity and no stored secrets) is planned, not built yet.

More detail on each protection is on the Security page. For integration documents, write to info@blackfishweb.com.

Want to see it with your own video?

Write to us for a demo, or sign in if you already have an account.