

The Media Platform
Key Features
-
Single Substrate of Active Content (Media, Metadata, Code)
Media, metadata and code are automatically linked into a single content object structure, a single point of truth that can be streamed and serviced upon ingest via reference
- A provable chain of record controls access to content and tracks changes
- Native ML tagging of content occurs automatically within the fabric (people, place, objects, and activities) at the frame and scene level
-
Streaming/Servicing from Source, Just-in-Time
- Ultra-low latency, high quality video delivery is enabled (no re-buffer), without a CDN, that supports H.264, H.265, multi-format ABR DASH and HLS with DRM, and existing players/platforms
- Video is playable upon ingest with configurable output offerings (streaming, file delivery) and dynamic content
- In-network transport and transcoding occur natively on an A/V pipeline that transcodes, packages, and intelligently routes video in real time
- Different digital outputs are built dynamically from the same source objects such as language versions, watermarked versions, DRM’d packages, personalized insertions, clips, starting points, branching story games and render, and more
-
Re-use and Re-versioning of Source Video without File Copies
- Re-use and re-versioning of video assets and metadata is enabled without re-creating, re-publishing, re-transcoding or re-distributing the content or supporting metadata
- Inter-Object Linking allows for static URLs and dynamic presentation that resolves, at serving time, to images, metadata, playable video, playlists, and more
-
Access Control and Rights Control Built-in
- Every media asset is backed by a built-in, blockchain contract that controls authorization and access to the content
- Content’s life cycle, from audience reporting to rightsmanagement to version history, are realizable directly in the platform, recorded in its ledger, provable, and tamper free
-
Content Security Does Not Trust the Infrastructure
- A zero-trust encryption structure protects content from the infrastructure from ingest through playout (end-to-end)
- Content objects are backed by contracts with parts encrypted with Content (AES) and Owner (AFGH) keys, instead of passing keys across “secured” infrastructure
- Proxy re-encryption on access includes new cryptographic primitive; multiple ‘access windows’ for multiple portals (or people) operating on the same content; and re-encryption to DRM keyspace for consumers