top of page
Both FZ LLC in Dubai

SAVX

A next-gen container for owned, provable, monetizable media

What it is. SAVX is a new ISOBMFF-family media container that ships every article, image, video, or post as a static visual surface + a procedural audio-domain verification stream. The verification stream is inaudible to humans and carries a rolling bothX® acoustic signature—ID, UTC time/date, and optional location—emitted live at render time. Each emission is cryptographically bound to what’s on screen (viewport-hash attestation) and produces a signed receipt. Result: the asset proves its origin, authorship, time, and viewing/playing events from the media signal itself, on any platform, online or offline.

SPECS

The problem SAVX solves

  1. Ownership & authorship. The bothX® mark in SAVX ties every published unit to a creator ID and issuance moment. Receipts minted during consumption form an append-only, court-credible chain of custody.

  2. Verifiability & accountability. Because the proof rides inside the audio domain and is linked to the current viewport, SAVX establishes who/when/what was rendered—not just “a URL was hit” or “a file was downloaded.”

  3. Fraud and deepfakes. Reuploads, edits, or broadcast captures still verify from the embedded signal. Attempts to forge time/location fail the rolling-mark and lane-hop checks by design.

  4. Monetization on verified attention. Platforms and publishers can settle ads/subscriptions on signed time slices (e.g., per 3-minute blocks) rather than logs, cutting IVT and replay padding. Creators get clean attribution and payout triggers that travel with the asset.

  5. Control over AI training. SAVX does not rely on robots.txt. It binds license terms to a provable render flow (receipts). Distribution endpoints can require valid SAVX receipts to expose plaintext or high-res assets. If a corpus contains your work without corresponding receipts, you have strong, machine-detectable evidence of unauthorized copying/usage. This changes the economics of “free training” and makes enforcement practical at scale.

Provable mechanics

  • Two synchronized tracks

    • Visual: deterministic, scroll-native layout (or a static raster) rendered to the display.

    • Verification: a parametric ultrasonic stream (not PCM) defined by compact atoms {slot_time, lane_index, f_center, phase, envelope_id, duration}. A tiny bitrate (≈10²–10³ bps) reconstructs the exact bothX® waveform pre-DAC during playback; no creative audio is stored or transmitted in receipts.

  • Viewport-hash attestation
    On each slot, the player computes a canonical viewport hash of what is actually visible and commits it into the emitted acoustic payload and the signed receipt. This proves what was shown while the mark emitted.

  • Receipts, not recordings
    Every N seconds the verifier emits a signed record (ID, UTC, slot audit: SNR/CFO/margins, viewport hash commit, device attestation, verdict). By default, no consumer content (text/audio/video) leaves the device—only receipts.

  • Forensics and interoperability
    Post-hoc, a batch/file verifier (or even a mic capture of a rebroadcast) can decode the rolling mark, reconstruct the viewport commitments from the file, and confirm integrity. SAVX is designed as an ISOBMFF profile and can be registered via MP4RA (e.g., brand SAV1, sample entry savp, config box savC) for broad toolchain compatibility.

Changes for the ecosystem

  • Journalism & books: “Articles as media.” Reading time and excerpts become provable events; archives self-attest decades later. Quotes and reprints inherit traceable authorship.

  • Creators & DSPs: Plays/views are receipt-counted across platforms, ending screenshot wars. Portable attribution and pay-per-attention work the same for podcasts, reels, shorts, and long-reads.

  • Programmatic & OTT: Settlement is tied to media-embedded proofs rather than logs; silent autoplay or muted padding no longer counts.

  • Enterprises & public sector: Briefings, memos, and public notices gain tamper-evident provenance with optional location; disputes resolve from the file itself.

Security, privacy, and practicality

  • Security: The rolling signature uses robust high-frequency lanes with pilot lock; verification gates (SNR, frequency offset, timing) and lane-hop validation prevent spoofing.

  • Privacy: Default mode stores only receipts (no creative content). Optional dual-custody forensics (bit-split device/cloud, warrant-gated reassembly) is available for regulated workflows.

  • Compatibility: SAVX plays everywhere as ordinary media; legacy players ignore the verification track and still render the visual. SAVX-aware players synthesize/verify and emit receipts.

  • Efficiency: Parametric verification is orders of magnitude smaller than PCM and far lighter than “static video + audio,” reducing egress while increasing evidentiary value.

What creators and platforms get on day one

  • A container that proves ownership (ID/time/place) and who consumed it when—from the media itself.

  • Monetization levers tied to verified attention and portable attribution.

  • A defensible stance against unconsented AI training: license-gated access based on receipts, plus deterministic signals that make unauthorized ingestion detectable and enforceable.

  • An open verifier and conformance suite so anyone can check proofs without trusting a vendor.

SAVX turns digital content into a self-authenticating asset. It restores credit and economics to human creators, gives platforms hard evidence for settlement and safety, and provides a practical, enforceable line between public viewing and unlicensed machine ingestion—without breaking today’s web and app stacks.

Contact

+971 5649 26565

bottom of page