Verified viewing

A view count is a claim.
KAIRO gives you proof.

KAIRO checks that a video really played — at normal speed, start to finish, on one device, on a tab someone left open — and issues a signed record that anyone can verify without asking us. No screenshots, no trusting a dashboard, no “trust me”.

The problem we solve

Counts are self-reported

A “view” usually means the player started. It says nothing about whether the video played, or how much of it did.

Screenshots prove nothing

A screenshot is an image of a page. It can be edited, staged, or produced by a script in seconds.

Audits are slow

When completion matters — training, disclosure, sponsor reporting — someone ends up asking people what they watched.

What KAIRO does

Playback proof

It really played

The server watches the media position against its own clock. Skipping, idling, 1.5× and hidden tabs fail the check.

Two separate claims

Played vs. human

“Played” is reachable by a patient script. “Human” needs hardware attestation or recorded human input. We never sell one as the other.

Portable evidence

You can check it

The record is signed with a published key and included in a daily root timestamped into Bitcoin. Edit one number and it fails.

How it works

  1. You add one script tagYour page keeps its own player — a normal video, or a YouTube embed. KAIRO reads the playback position from it.
  2. Our server opens a sessionIt issues a signed token the page cannot invent, and starts its own clock. The browser is never trusted with the score.
  3. The page reports where the video isEvery couple of seconds it sends the position, plus whether the tab is visible and whether there is real mouse or keyboard activity.
  4. The server judges each reportMedia must advance between 40% and 125% of real time. Too fast is a seek or speed-up; too slow is a stall or an idle tab. One session per device.
  5. It issues a signed recordAt the end the score is recalculated from the stored reports and signed with our Ed25519 key: content, watched time, score, verdict, what it proves — and what it does not.
  6. Each day is anchoredAll of that day’s records are hashed into one root, published openly, and timestamped into Bitcoin. Even we cannot rewrite yesterday.

What the record proves — and what it does not

It proves

  • The media advanced at roughly real speed, start to finish.
  • It was not skipped, scrubbed, or played at 1.5×.
  • The tab stayed visible and in focus.
  • One device, one session — no parallel streams.
  • The figures have not changed since they were signed.

It does not prove

  • That someone was looking at the screen the whole time.
  • That a human was holding the device — unless attestation is on.
  • Anything about who that person is.
  • That the content is good, true, or useful.

We print both columns on every record. A verification product that hides its limits is not verification.

Who it is for

Training & compliance

Staff awareness, safety briefings, and supplier disclosure packs where you need evidence the video was completed.

Sponsors & campaigns

Proof a sponsored film was watched to the end, instead of a platform’s estimate.

Media & publishers

A portable record for a client or an auditor, without handing over a dashboard login.

Why you can check it yourself

Most “verified” products ask you to believe the vendor. KAIRO does not need to be believed:

Public key

The signing key is published at /api/v1/pubkey, with its fingerprint. Anyone can verify a signature.

Daily roots

Each day’s records are hashed into one root at /api/v1/roots, with an inclusion proof for every record.

Bitcoin timestamp

The root file is stamped with OpenTimestamps, so you can prove it existed before a given date. Free, no token, no wallet.

One command checks a record, its signature, and its place in the day’s root: node verify-evidence.mjs record.json --proof proof.json

Privacy

KAIRO stores a hashed device identifier, the playback positions, and whether the tab was visible — behavioural data, not identity data. We do not ask who the viewer is, and nothing about a viewer is written to a public chain. Records are kept for an agreed retention period, and a client can ask for them to be deleted.

Where this is going

Live

Signed records & daily Bitcoin anchor

Every record verifiable without us; every day rooted and timestamped.

In progress

Hardware attestation

Google Play Integrity and Apple App Attest, so “human” can be claimed at scale rather than inferred from input.

Planned

Verified credits — closed loop

An add-on to the service, not a separate product: finishing a video earns credits that can be spent on Airise services or a sponsor's voucher. Non-transferable, no cash-out, no trading, no yield — which keeps it an exempt virtual asset under VARA's issuance rulebook, so no licence is required. Not live yet.

Later

Transferable token

Only if credits ever need to move between people. Under VARA that is a Category 2 issuance — no licence of our own, but distribution through a licensed distributor — or Category 1 if it is pegged to a currency. It would sit on top of the proof, never replace it, and only after revenue and advice. No token is on sale.

Try the live demo Talk to us