Protocol Overview

The anitya protocol establishes attribution through comprehensive recording of the creative process. While traditional systems timestamp final outputs, the protocol captures the complete workflow: every modification, every tool interaction, every creative decision that proves human authorship.

How It Works

The protocol uses two capture methods depending on the environment:

Inside anitya Engine: Event sourcing captures the actual commands executed during creation - object transforms, material assignments, script changes. This produces lightweight, searchable logs that can be mathematically verified and replayed to reconstruct the exact scene.

Outside anitya Engine: Screen recording captures the visual creative process across any software. Smart recording activates only when creative tools are in focus, pauses during idle time, and compresses aggressively to minimize storage.

Both methods produce cryptographic proof anchored to the Solana blockchain automatically as you work.

The Proof Package

When registering work, the protocol bundles:

  1. Session proof - Event log or compressed video with hash chain

  2. Visual proof - Thumbnail of the final output

  3. Manifest - Dependencies, collaborators, timestamps

This package uploads to permanent storage (Arweave), generating an immutable record. Only hashes and metadata go onchain - raw recordings stay private unless the creator chooses to share them.

Continuous Anchoring

The protocol anchors proof automatically during creative sessions, independent of whether you've finished an asset. Every 10 minutes, the current proof hash commits to Solana.

If you work for 8 hours, you'll have ~48 onchain anchors proving continuous creative effort. This proves the process happened over time, not that you simply possess a finished file.

Lineage Tracking

When you use existing assets in your work, the protocol records the provenance link automatically. This builds a directed graph of attribution - derivative works point to their sources, enabling automatic royalty distribution across unlimited generations of remixes.

Identity Without Friction

The protocol uses custodial wallets managed via cloud-based HSM (Hardware Security Module). Users sign up with email or social login - no seed phrases, no wallet management. Private keys never leave the secure hardware.

Users who want full self-custody can export their keys at any time.

AI Contribution Tracking

Human work gets captured via event logs or screen recording. AI agents operating within anitya Engine report their contributions directly via MCP protocol - task executed, duration, assets modified. External AI tools (ChatGPT, Midjourney) appear in screen recordings, showing the human-AI collaboration process.

Both streams combine into unified attribution, enabling automatic compensation for creators and agent developers.

Verification

Anyone can verify attribution without creator involvement:

For anitya Engine assets, verification is mathematical - recalculate the hash chain, compare against the onchain record. The scene can even be replayed from the event log, reconstructing the creative process visually.

For screen recordings, verification compares video hashes against the onchain Merkle root, with the recording available for review.

What the Protocol Cannot Do

  1. Novelty verification: Cannot prove your work is globally original.

  2. Automatic infringement detection: Cannot monitor the internet for unauthorized use.

  3. Legal enforcement: Provides evidence, but courts still decide.

What it does provide: Comprehensive documentation that transforms "I claim I made this" into cryptographic proof of your creative process.

Last updated