MonteVIDEO Tech Summer Camp

Summer Projects 2027 · Weekly updates

Identity that travels with the video

Can a person’s licensed likeness keep its ID all the way from production to the player, through transcoding and ad insertion? Here is what happens every week.

← All Summer Projects 2027 · How it started, on the Qualabs blog

  • Will Kreth Will Kreth Proposed the project · HAND
  • David Hassoun David Hassoun Tech Sponsor · Qualabs
  • Nicolás Caballero Nicolás Caballero Staff Engineer · Qualabs
  • Maximiliano Pollinger Maximiliano Pollinger Staff Engineer · Qualabs

Week by week

What the project did, week by week

Every Thursday the Identity Metadata Track meets for an hour and keeps working async in between. Each entry sums up what was shown, what was agreed and what comes next, from the call notes. The first call was on Thursday 12 November. The newest week goes first.

Week 2 ·

The ID reaches the player through HLS

What happened

Serena Coduri and Serrana Garcia (Qualabs) presented the results of phase zero: tests on whether a HAND ID, the identifier of a person’s licensed likeness, survives the trip to the player. Putting the ID inside the MP4 file failed, because a standard transcode drops those tags. Carrying it in the HLS stream, in the playlist and in tags inside each segment, worked: the ID reached the player. Adding the ID to a C2PA content credential worked too, but transcoding removed the credential, so the team is testing two fixes: signing the new version with the original credential as its “ingredient”, and an invisible watermark in the pixels that points back to it.

Highlights

  • Phase one is about ads: SCTE-35 cues that carry the HAND ID into playlists and players, and a bridge from C2PA to the ad server, for server-side insertion (with AWS MediaTailor) and client-side insertion (with VAST). The ID already travels inside VAST extension tags.
  • Agreed: for the demo, the player checks the licensed-likeness ID (Type 2) against the HAND registry, and trusts the rest of the chain.
  • Checking permissions at every step of the chain is the most secure option, but it adds a request at every step. The proposal is to sign a hash where the data starts, so every later step can verify it was not altered.

Next steps

  • Maximiliano Pollinger builds the signed hash at the start of the flow.
  • No call on Thursday 26 November, for US Thanksgiving: updates go by email and on Discord, and the next call is on 3 December.

Week 1 ·

Mapping the HAND ID’s journey from content to ad

What happened

The first weekly call of the track. Will Kreth (HAND) presented the starting point: HAND gives public figures a persistent ID, with one type for the person and another for a licensed likeness of that person, such as a digital replica, linked by a recorded consent. The registry already holds about 2.7 million records. The rest of the call was about where that ID should enter the video and how it travels to the player and the ad server.

Highlights

  • The ID has to live in two places: in the content, with the people who appear in it, and in the ad, so the ad server can match the two.
  • Measurement is the point: knowing who appears in an ad, and for how long, is what makes it possible to pay people for the use of their likeness.
  • HAND provides the ID that goes inside the C2PA content credential; the signature comes from C2PA tools.
  • Agreed: keep the demo small, with a minimum goal and a reach goal.

Next steps

  • Build a first MP4 file that carries a HAND ID: a short real video of a team member and an AI variant of the same person.
  • Test ways to put the ID into the video and get it out again, for both content and ads.

Open to everyone

Join the weekly call

The Identity Metadata Track meets every Thursday at 12:00 Montevideo · 10:00 ET · 16:00 CET, until the end of January. Anyone can drop in: share what you know, or pick an issue and build. Between calls the team keeps working async on the Video Dev Discord, where the track has its own room.

Join the call → + Google Calendar + Apple / Outlook Video Dev Discord