# What is Provenance

Provenance is the ability to trace the origin, history, and modifications of content and AI actions throughout their lifecycle. It serves as a foundational layer of trust, enabling transparency and accountability. By documenting each step taken—from creation to editing and decision-making—provenance ensures that the authenticity of content can be verified with confidence.

In simple terms, provenance allows us to answer critical questions such as:

Who created this content? How has it been modified? why did an AI agent make a particular decision?

Provenance provides a clear, auditable trail that connects the dots between the content's origin and its current state, empowering users to make informed decisions about the information they consume.


# Why Provenance Matters?

The world is undergoing a digital revolution driven by AI-generated content and autonomous AI agents. These advancements have reshaped how we create, interact with, and consume content. From hyper-realistic images to AI-authored narratives, the potential for innovation seems boundless. However, this rapid progress has given rise to a profound challenge: trust.

In an era where misinformation spreads faster than ever, distinguishing between original, edited, or AI-generated content is increasingly difficult. This crisis of authenticity undermines our ability to rely on the integrity of information, leaving us questioning everything from images and videos to news articles and decisions made by AI agents.

Autonomous AI agents like [@AI16z](https://elizaos.ai/) and [@AIXBT](https://x.com/aixbt_agent?lang=en) are influencing opinions, making financial decisions, and executing tasks with unprecedented precision. Platforms like Virtuals and frameworks like ELIZA and [G.A.M.E ](https://x.com/GAME_AgentAI)empower these agents to deliver deeply personalized experiences, pushing the boundaries of what AI can achieve. Yet, as these agents grow more sophisticated, so does their potential to manipulate reality and erode trust.

As AI-driven decisions and content increasingly shape the world around us, critical questions emerge:

How can we trust what we see? Who created a piece of content? What modifications were made, and why did an AI agent make a specific decision?

Without transparency and provenance, we risk living in a world where authenticity is a luxury rather than a guarantee. Provenance matters because it bridges this gap, ensuring that trust, accountability, and transparency remain cornerstones of the digital age.


# Why Hash Network Exists?

Organizations like the [C2PA](https://c2pa.org/) and the [Content Authenticity Initiative (CAI)](https://contentauthenticity.org/) have made significant progress in advancing provenance standards. They have developed tools and specifications to enable the creation, management, and updating of provenance data, paving the way for a more authentic and trustworthy digital ecosystem. These efforts have been instrumental in improving content authenticity. However, the way provenance is currently stored presents a critical limitation that must be addressed.

The Problem with Current Provenance Systems Most current systems, including those developed under the C2PA standards, store provenance data as metadata embedded directly in the content itself. While this approach works in controlled environments, it has significant vulnerabilities:

* Erasability: Metadata can be stripped away or overwritten, leaving the content without a traceable history.
* Tampering: Provenance data embedded in the content can be modified, undermining its integrity and trustworthiness.
* Limited Accessibility: Since the metadata is tied to the specific file, it is not universally accessible, making provenance verification cumbersome or impossible when the file is separated from its data.

The Adobe Content Credentials Cloud (ACCC): A Centralized Attempt: Adobe has recognized these limitations and introduced alternatives like the Adobe Content Credentials Cloud (ACCC). The ACCC provides a centralized, cloud-based storage system for provenance manifests, allowing attribution and history data to persist even if metadata is stripped from the content.

While this approach addresses some challenges, it introduces new problems:

* Centralization: The ACCC is proprietary and relies on Adobe’s infrastructure, making it vulnerable to central point-of-failure risks.
* Limited Ecosystem: Currently, the ACCC is only available to Adobe tools, restricting its usability for broader applications across diverse platforms.
* Not Open Source: The lack of openness makes it inaccessible to developers and organizations that prioritize open standards and community-driven solutions.
* Not Tamper-Proof: As a centralized system, it does not inherently guarantee the immutability and transparency needed to prevent unauthorized alterations.


# How Hash Network Solves These Problems?

Hash Network builds upon the strong foundation laid by the C2PA standards and leverages the tools created by the Content Authenticity Initiative (CAI) to redefine content provenance. By introducing a decentralized, on-chain approach, Hash Network addresses the vulnerabilities of current systems and offers a secure, tamper-proof, and universally accessible solution to the challenges of content authenticity.

#### Key Innovations

**1. Tamper-Proof On-Chain Provenance**

Every action—whether it’s a content edit, an AI-generated content, or an attribution— is securely recorded on-chain using Hash Network's Provenance SDK and Smart Contract.

* This approach ensures that provenance data is immutable and cannot be altered or tampered with, creating a trustworthy and auditable trail.
* Unlike current provenance systems, where provenance can be erased or overwritten, Hash Network guarantees that the history of content remains intact and verifiable.

**2. Decentralized Infrastructure with True Scalability**

Hash Network eliminates the reliance on any centralized systems by offering a decentralized, community-governed solution.

* Built on Arbitrum's OrbitStack, a modular Layer 3 blockchain, and settled on Base, this infrastructure combines scalability with resilience.
* By decoupling provenance from proprietary systems, Hash Network ensures universal access and enables anyone to independently verify provenance data without requiring specific tools or platforms.

**3. Global Provenance Chain**

Hash Network creates a universally accessible provenance chain that links content, its modifications, and any associated AI actions into a single, tamper-proof history.

* This approach ensures that the authenticity of content is always traceable, regardless of where it is stored or shared.
* The provenance chain enables users to distinguish between authentic and manipulated content, fostering trust and accountability across the digital ecosystem.

**4. C2PA Compliance for Interoperability**

Hash Network adheres to C2PA standards, ensuring that the provenance data it generates is compatible with existing systems and tools.

* This enables seamless integration into a wide range of content creation tools, AI platforms, and editing software, supporting a cross-platform ecosystem.
* Developers and platforms adopting Hash Network can confidently interoperate with other C2PA-compliant systems, providing continuity and consistency for end-users.

#### Hash Network vs. Adobe Content Credentials Cloud (ACCC)

| **Feature**      | **Hash Network**                                 | **ACCC (Adobe Content Credentials Cloud)**                |
| ---------------- | ------------------------------------------------ | --------------------------------------------------------- |
| Immutability     | Provenance stored on-chain, tamper-proof.        | Centralized storage vulnerable to tampering.              |
| Accessibility    | Universally accessible across platforms.         | Limited to Adobe tools and ecosystem.                     |
| Decentralization | Open, decentralized, and community-driven.       | Proprietary, tied to Adobe's infrastructure.              |
| Interoperability | Built on C2PA standards, open for all platforms. | Closed system, lacks interoperability beyond Adobe tools. |

\
The Result: A New Standard for Provenance

Hash Network doesn’t just address the vulnerabilities of current metadata-based systems; it redefines provenance. By combining C2PA standards, immutable on-chain storage, and decentralized infrastructure, Hash Network ensures that provenance is:

* Tamper-Proof: Immutable and protected from unauthorized alterations.
* Transparent: Universally accessible, enabling anyone to verify authenticity and history.
* Universal: Decoupled from specific content or platforms, ensuring interoperability across ecosystems.

Hash Network goes beyond existing systems like ACCC by solving the pain points of centralization and lack of accessibility. It embodies the ethos of Web3 by offering an open, decentralized, and resilient alternative for tracking and verifying content provenance.

<figure><img src="https://1594793363-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRKSWMBzM9uXdqpjmAlMd%2Fuploads%2FaWMN2Nw1ESUHXQRTQU6C%2Fimage.png?alt=media&amp;token=78f52f10-5f2d-4f69-9904-03a85332e8a8" alt=""><figcaption></figcaption></figure>

Through Hash Network, we can build a future where trust, transparency, and authenticity are no longer optional but integral to every piece of digital content and every decision made by AI.


# Use Cases


# Provenance For AI Agent Actions

In the era of AI-driven decision-making, understanding the reasoning behind an AI agent's actions or decisions is paramount. Hash Network's provenance system can track the lineage of decisions made by AI agents, documenting:

* **Decision Pathways:** Every action taken by an AI system, such as data input, model selection, and processing steps, is tracked and stored as immutable records on-chain.
* **Transparency in AI Behavior:** This enables a clear audit trail that explains why an AI agent arrived at a particular decision or conclusion, making the AI’s behavior understandable and traceable to both creators and users.
* **AI Accountability:** By embedding provenance in AI agent actions, Hash Network ensures that any mistakes or biased outputs from AI systems can be traced back to their source, allowing for corrective actions, accountability, and optimization of AI systems.
* **Compliance and Ethics:** For industries such as healthcare, finance, and law, tracking AI decision-making processes ensures compliance with regulatory standards, ethical guidelines, and fairness, reducing the risk of algorithmic bias.

Provenance for AI agents is essential for building trust in AI technologies, ensuring that their operations are transparent and their actions are well-documented and verifiable.


# Provenance In Camera

In the world of photography and videography, establishing the authenticity of visual media is critical, particularly for journalism, evidence gathering, and creative content. Hash Network provides provenance for images and videos captured by cameras by:

* **Device Authentication:** Every photo or video taken is linked to a specific device, ensuring that the device used is authenticated. The camera’s details—such as make, model, and unique identifiers—are stored on-chain.
* **Timestamping:** Each image or video is given an immutable timestamp, verifying exactly when the media was captured. This timestamp helps establish the content’s originality and validity, especially for legal and historical documentation.
* **Geolocation Provenance:** When available, geolocation data is recorded, ensuring the context of the content’s creation is verifiable. For journalists or investigators, this can provide crucial evidence of the content's origin and context.
* **Content Integrity:** Any edits or modifications to the visual content are recorded on-chain, preserving a transparent version history. This ensures that the original media can always be distinguished from manipulated versions.

Provenance in cameras ensures the authenticity of visual media, which is essential for maintaining trust in the documentation of real-world events and preventing the spread of manipulated or fake visuals.


# Provenance In Editing Tools

Content editing tools, whether for images, videos, or documents, are widely used across industries for producing high-quality digital content. However, the proliferation of editing tools has made it increasingly difficult to determine whether the content is original or modified. Hash Network can address this by integrating provenance tracking into editing tools:

* **Track Modifications:** Every modification made to a piece of content—whether an image, video, or text—is recorded on-chain. This includes cropping, color adjustments, text additions, or any other edits that alter the content’s integrity.
* **Version Control:** Hash Network’s provenance system ensures a transparent version history, where each change is linked to its predecessor. Users can trace the evolution of the content and see exactly how it was altered over time.
* **Attribution of Edits:** Editing tools can assign credits to users who made the changes, establishing clear accountability and attribution for the work.
* **Prevention of Misuse:** With a tamper-proof record of edits, creators can prove that their work has not been fraudulently altered. This is particularly useful in preventing deepfakes or manipulated media from spreading in the digital space.

Provenance in editing tools ensures that the integrity of the original content is preserved and provides a transparent history of all modifications, preventing content manipulation and ensuring proper attribution.


# AI Generated Content

The rise of AI-generated content, whether in the form of text, images, or videos, has introduced new challenges in determining content authenticity. AI systems can produce vast quantities of content, making it difficult to assess its origin and integrity. Hash Network’s provenance solution tackles this by ensuring that every piece of AI-generated content is traceable:

* **Traceability of AI Inputs:** Provenance for AI-generated content records the inputs (such as training data, AI prompts, or other influencing factors) and models used to generate the content. This provides a clear record of the content’s origins.
* **Creation Context:** Hash Network allows creators and consumers to view the history of an AI-generated piece, including the specific algorithms or neural networks used, the data it was trained on, and the decisions made during generation.
* **Preventing Misinformation:** By linking AI-generated content to its metadata and creation history, users can verify whether the content was artificially generated or human-authored, helping to combat misinformation and disinformation.
* **Ethical Usage and Licensing:** AI-generated content can be embedded with licensing terms on-chain, ensuring that creators retain control over how their work is used and preventing unauthorized distribution or modification.

AI-generated content provenance offers transparency and accountability, addressing ethical concerns and ensuring that the content is used in a fair and responsible manner.


# Other Use Cases

Beyond the use cases mentioned above, Hash Network’s provenance capabilities can be applied in a variety of other industries and scenarios:

* **Supply Chain Management:** Tracking the provenance of goods, from raw materials to finished products, ensures transparency and accountability in supply chains. It can help verify the ethical sourcing of materials and prevent fraud.
* **Intellectual Property:** Provenance can be used to protect intellectual property by ensuring that content creators retain ownership rights and that licensing terms are respected.
* **Academic Research:** For academic and scientific research, provenance ensures that data is verifiable and that the integrity of research findings is preserved. It helps prevent data manipulation and falsification.
* **Digital Art and NFTs:** Provenance is crucial in the world of digital art and NFTs, where it is necessary to establish the ownership and history of a digital asset. Hash Network provides a decentralized solution for verifying the authenticity and ownership of digital artwork and collectibles.

These use cases show how Hash Network’s immutable, transparent provenance system can be applied across multiple industries to ensure content integrity, protect creator rights, and foster trust in the digital ecosystem.


# Provenance SDK

The **Provenance SDK** by Hash Network empowers platforms to ensure transparency, authenticity, and traceability of digital content. Designed for AI-generated media, editing tools, cameras, and autonomous AI agents, it provides seamless provenance tracking across diverse applications.

Built on **C2PA standards**, the SDK ensures cross-platform compatibility while leveraging Hash Network's blockchain infrastructure for immutable and scalable provenance storage. It supports the lifecycle of content, from creation to modification, ensuring trust and transparency.

***

**Core Features**

1. **C2PA Compliance**
   * Creates provenance data adhering to C2PA standards for universal compatibility.
2. **Immutable On-Chain Storage**
   * Uses Hash Network’s Provenance Smart Contract on its Layer 3 chain for secure, scalable metadata storage.
3. **End-to-End Traceability**
   * Tracks content lifecycle details, including creation sources, editing parameters, and cryptographic signatures.
4. **Interoperability**
   * Ensures compatibility across diverse platforms and systems implementing C2PA standards.
5. **Wide Format Support**
   * Handles various content types, including images, videos, documents, and AI-generated outputs.

***

**How It Works**

1. **Content Capture**
   * SDK integrates with tools to record details like source, AI involvement, and edits.
2. **Provenance Metadata Creation**
   * Metadata is structured per C2PA standards for interoperability.
3. **On-Chain Storage**
   * Provenance data is securely stored on Hash Network’s blockchain via smart contracts.
4. **Verification**
   * Data can be queried through Hash Network APIs or verification tools to ensure authenticity.

<figure><img src="https://1594793363-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRKSWMBzM9uXdqpjmAlMd%2Fuploads%2FSZXJvGLavxyWL8A5rfTZ%2FHN%20SDK.png?alt=media&amp;token=35458cbc-cfc1-4ab7-856e-2ff10f53a9c7" alt=""><figcaption></figcaption></figure>

This streamlined flow ensures secure, tamper-proof provenance tracking, revolutionizing digital content transparency.


# Provenance Contract

The Provenance contract ensures data traceability by allowing authorized writers to create and modify provenance data. This contract is particularly useful for verifying the history and modifications of digital assets.

#### Key Features

* **Writer Management**: Only designated writers can create or modify provenance data.
* **Data Traceability**: Each provenance record links back to its original hash for complete transparency.
* **Modification Mapping**: Tracks updates made to existing provenance records.

#### Contract Details

**Constructor**

Initializes the contract by assigning the deployer as the owner and the first writer.

**Provenance Structure**

```
struct ProvenanceData {
    string provenance;
    address writer;
}
```

* `provenance`: The description or metadata of the asset.
* `writer`: The address of the entity that created or modified the record.

**Key Functions**

1. **getWriters**: Returns the list of all authorized writers.
2. **addWriterAddress**: Allows the owner to add new writers.
3. **removeWriterAddress**: Enables the owner to remove writers.
4. **createProvenance**: Allows a writer to create a new provenance record.
5. **updateProvenance**: Updates an existing provenance record and links it to the original hash.
6. **getProvenanceData**: Fetches the provenance data for a given hash.
7. **getOriginalHash**: Retrieves the original hash for a given modified hash.

#### Contract Deployed on the Hash Network Testnet at: [View Provenance Contract](https://hash-testnet.explorer.caldera.xyz/address/0x763Ac2f8DBeF3612D5a8C75DA3467E7eC0C7042f?tab=contract_code)


# Provenance Schema

The **Provenance Schema** used by Hash Network is based on the C2PA standards and serves as a structured framework for capturing key content metadata, ensuring the integrity and traceability of digital content. The schema is designed to track the lifecycle of content, from its creation to any modifications and actions that affect it. This allows for detailed provenance tracking, ensuring content authenticity and providing transparency.

The schema is structured into several components:

**ManifestStore**

* **active\_manifest**: This field holds the identifier of the currently active manifest, representing the most recent state of the content’s provenance.
* **manifests**: A collection of all manifests associated with the content. Each manifest is identified by a unique UUID.
* **validation\_status**: An array containing the validation status of each manifest, indicating whether it has been verified for authenticity and integrity.

**Manifest Details**

* **title**: A human-readable title for the content, typically the filename.
* **format**: The MIME type of the content file (e.g., image/png, application/pdf).
* **instance\_id**: A unique identifier for the specific content instance.
* **claim\_generator**: The tool or system that generated the provenance claim, identifying the software or platform used.
* **claim\_generator\_info**: Metadata about the claim generator, such as its version and other relevant details.
* **ingredients**: An array of source components (or Ingredients) that contribute to the content, such as raw images, videos, or audio files.
* **assertions**: Claims regarding the content, such as creation, modification, and other actions performed on the content.
* **signature\_info**: Cryptographic details ensuring the authenticity of the content, such as the signing algorithm, issuer information, and the certificate’s serial number.


# JSON Example

Here is an example of how the Provenance Schema is represented in JSON format. This example illustrates the structure of the `manifest_store`, with a sample manifest, actions, and assertions related to the content:

```
"manifest_store": {
    "active_manifest": "urn:uuid:064d517f-ef28-4990-9228-fbea133d4aa2",
    "manifests": {
      "urn:uuid:e7d7be8e-fe0f-48a3-888b-f739bd35e72a": {
        "claim_generator": "Hash-Network/c2pa-rs/0.40.0",
        "title": "dogs_walking.png",
        "format": "image/png",
        "instance_id": "xmp:iid:8a6c70bf-4ccc-4bb7-b2a0-a61ad41e3d02",
        "ingredients": [],
        "assertions": [
          {
            "label": "c2pa.actions.v2",
            "data": {
              "actions": [
                {
                  "action": "c2pa.created",
                  "softwareAgent": {
                    "name": "stability-ai/sdxl",
                    "version": "7762fd07cf82c948538e41f63f77d685e02b063e37e496e96eefd46c929f9bdc"
                  },
                  "parameters": {
                    "height": 1024,
                    "prompt": "Dogs walking Together",
                    "num_inference_steps": 50,
                    "width": 1024,
                    "refine": "no_refiner"
                  }
                }
              ]
            }
          }
        ],
        "signature_info": {
          "alg": "Ed25519",
          "issuer": "C2PA Test Signing Cert",
          "cert_serial_number": "638838410810235485828984295321338730070538954823"
        }
      }
    }
  }
}

```

**Explanation of the JSON Structure**:

* **manifest\_store**: This contains the active manifest and a collection of all manifests tied to the content.
* **active\_manifest**: This identifier points to the most recent manifest that holds the current state of the content’s provenance.
* **manifests**: The collection of manifests identified by their UUIDs. Each manifest contains metadata like the claim generator, content title, format, instance ID, ingredients, assertions, and signature information.
* **claim\_generator**: This shows the tool or system (e.g., Hash Network’s implementation) used to generate the provenance claims.
* **assertions**: These are the key claims related to actions performed on the content, such as creation actions that include the software used (e.g., Stability AI's SDXL model).
* **signature\_info**: This section holds cryptographic details, ensuring that the content’s authenticity and integrity are verifiable.

This JSON example showcases a simple but comprehensive structure for managing and verifying the provenance of digital content, in line with the C2PA standards.


# Verify SDK

The **Verify SDK** by Hash Network is a powerful toolkit designed for developers and publishing platforms to easily integrate content authenticity verification into their applications. It allows seamless validation of digital content provenance, ensuring that the media consumed by end-users is trustworthy.

Even in cases where content lacks embedded provenance metadata, the **Verify SDK** leverages perceptual hashing to reconstruct content origin and verify its authenticity. This means that, regardless of the platform or tool used to generate or modify content, the **Verify SDK** can independently verify its historical context and origins.

**Core Features of the Verify SDK:**

* **Content Provenance Verification**: Validate the authenticity of digital assets by inspecting their history, creation, and modification details.
* **Perceptual Hash Matching**: Use perceptual hashes to verify the origin of content, even without embedded metadata, ensuring trust in assets from decentralized platforms.
* **Cryptographic Integrity**: Ensure the integrity of content provenance records using cryptographic validation, verifying that the content has not been tampered with.

The **Verify SDK** allows developers to embed content verification features directly into their platforms, increasing user trust and transparency in the digital media they interact with.

**Endpoints and Additional Details: Coming Soon**


# Verify API

The **Verify API** by Hash Network offers a scalable, RESTful interface for validating content authenticity and reconstructing its provenance. Designed to integrate easily with platforms of all sizes, the **Verify API** enables direct HTTP requests to verify digital content, whether it is verified through embedded metadata or perceptual hashing.

The API provides a convenient, efficient way to authenticate content provenance and verify the integrity of digital assets without requiring complex integrations or extensive changes to an existing system. Whether it's for an AI platform, decentralized storage, or media platform, the **Verify API** offers an adaptable solution for ensuring transparency and trust in digital content.

**Core Features of the Verify API:**

* **Content Provenance Verification**: Inspect the origin, history, and modifications of digital assets to confirm their authenticity.
* **Perceptual Hash Search**: Reconstruct provenance for content without embedded metadata through perceptual hash matching, identifying and verifying similar assets across decentralized networks.
* **Cryptographic Validation**: Verify digital content signatures and detect any tampering or alterations to ensure integrity.

**Key Benefits:**

* **Scalability**: Seamlessly handle millions of asset verifications through API integrations.
* **Ease of Use**: A simple, RESTful interface for quick integration into existing systems.
* **Trust and Transparency**: Enhance user confidence by providing verifiable content provenance and reducing the risk of misinformation.

The **Verify API** will provide platforms with the flexibility and power needed to verify the authenticity of digital content at scale, ensuring content integrity and offering users trust in their interactions with digital media.

**Endpoints and Additional Details: Coming Soon**


# Architecture Overview

The Hash Network Provenance architecture ensures transparency and authenticity through a robust architecture:

1. **Hash Network Provenance SDK** integrates seamlessly with AI models (e.g., DALL-E 3, Suno AI, Heygen) and agents (e.g., Truth Terminal, AI16z, AixBT) to enable the creation and recording of provenance data.
2. **Provenance Smart Contracts** on the Hash Network store immutable provenance records, guaranteeing security and trust.
3. **HN Verify SDK** allows clients and external applications to fetch and verify provenance data directly from the Hash Network by interacting with the Provenance Smart Contracts.

This architecture enables real-time validation of AI-generated outputs, ensuring that provenance remains transparent and traceable across all layers.

<figure><img src="https://1594793363-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRKSWMBzM9uXdqpjmAlMd%2Fuploads%2FxqYSI37CpWms2PsUwvNv%2FPronance%20layer.png?alt=media&amp;token=bd4c646e-a825-4d66-b0f0-df5b14dea241" alt=""><figcaption></figcaption></figure>


# Supported Media Formats

The following table summarizes the supported media (asset) file formats. This information is based on what the Rust library supports; other libraries in the SDK support the same formats unless noted otherwise.

| Extensions    | MIME type                                                                      |
| ------------- | ------------------------------------------------------------------------------ |
| `avi`         | `video/msvideo`, `video/x-msvideo`, `video/avi`, `application/x-troff-msvideo` |
| `avif`        | `image/avif`                                                                   |
| `c2pa`        | `application/x-c2pa-manifest-store`                                            |
| `dng`         | `image/x-adobe-dng`                                                            |
| `gif`         | `image/gif`                                                                    |
| `heic`        | `image/heic`                                                                   |
| `heif`        | `image/heif`                                                                   |
| `jpg`, `jpeg` | `image/jpeg`                                                                   |
| `m4a`         | `audio/mp4`                                                                    |
| `mp3`         | `audio/mpeg`                                                                   |
| `mp4`         | `video/mp4`, `application/mp4` \*                                              |
| `mov`         | `video/quicktime`                                                              |
| `pdf`         | `application/pdf` \*\*                                                         |
| `png`         | `image/png`                                                                    |
| `svg`         | `image/svg+xml`                                                                |
| `tif`,`tiff`  | `image/tiff`                                                                   |
| `wav`         | `audio/wav`                                                                    |
| `webp`        | `image/webp`                                                                   |

NOTES:

\* Fragmented MP4 (DASH) is supported only for file-based operations from the Rust library.\
\*\* Read-only


# Reputation System

The **Reputation System** in Hash Network evaluates the authenticity and provenance of digital content by assigning two key scores:

1. **Trust Score** – Measures the authenticity and integrity of content based on its on-chain provenance.
2. **Verification Confidence** – Indicates how confidently Hash Network can verify a piece of content using available provenance data.

These two metrics provide a transparent way to assess content trustworthiness before interacting with it.

***

#### **Trust Score**

**Definition:**\
The **Trust Score** is a percentage-based rating that determines how much a piece of content can be trusted based on its provenance records.

**How It Works:**

* Content with a fully intact and verifiable provenance history receives a **higher Trust Score**.
* Content that has been modified frequently or has missing provenance records will have a **lower Trust Score**.

**Trust Score Breakdown:**

| **Score (%)**  | **Meaning**                                                      |
| -------------- | ---------------------------------------------------------------- |
| **90% - 100%** | Fully verified provenance, no detected alterations.              |
| **60% - 89%**  | Minor modifications recorded, but content is still verifiable.   |
| **20% - 59%**  | Significant changes detected, authenticity partially verifiable. |
| **Below 20%**  | No provenance found or major inconsistencies detected.           |

A higher Trust Score indicates stronger content authenticity.

***

#### **Verification Confidence**

**Definition**

The **Verification Confidence** score is a percentage-based rating that represents **how confidently Hash Network can verify content authenticity** based on its available on-chain data.

**How It Works**

* Content with **strong provenance records and metadata integrity** receives a **higher Verification Confidence**.
* Content with **incomplete, inconsistent, or unverifiable provenance data** will have a **lower Verification Confidence**.

**Verification Confidence Breakdown**

| **Score (%)**  | **Meaning**                                                                 |
| -------------- | --------------------------------------------------------------------------- |
| **90% - 100%** | Content verification is highly reliable with strong provenance data.        |
| **50% - 89%**  | Some provenance data exists, but verification has minor gaps.               |
| **20% - 49%**  | Limited provenance records, moderate confidence in verification.            |
| **Below 20%**  | Little or no provenance data available, confidence in verification is weak. |

A **higher Verification Confidence** means that Hash Network can verify the content’s authenticity with greater certainty.

***

#### **How Reputation System Works in Hash Network**

* Every piece of content registered on Hash Network is assigned both a Trust Score and Verification Confidence.
* These scores are calculated based on on-chain metadata, provenance history, and content modifications.
* Users can check these scores using:
  * **Hash Network Verify Tool**
  * **Hash Network Playground**
  * **Smart Contract Queries & API**

***

#### **Why Reputation System Matters**

* **Trust Assessment** – Users can quickly determine how reliable a content piece is.
* **Tamper Detection** – Detects unauthorized modifications and potential misinformation.
* **Fair Attribution** – Ensures original creators receive proper recognition.
* **Strengthening Web3 Transparency** – Provides a verifiable standard for digital content in AI-generated media, journalism, and NFTs.

The **Reputation System** in Hash Network is a foundational element in ensuring content authenticity, making trust verifiable rather than assumed.


# Hash Verify - Chrome Extension

The **Hash Verify Chrome Extension** is an innovative browser-based tool that brings the power of Hash Network’s verification systems directly to your fingertips. Designed for professionals, researchers, and Web3 enthusiasts, this extension enhances content transparency, trustworthiness, and usability.

**Key Features**

1. **Comprehensive Content Details**
   * Gain instant access to **Trust Scores** and **Verification Confidence** (expressed as percentages) to evaluate the authenticity and integrity of content at a glance.
   * Visual indicators and an intuitive color-coded scheme make it easier to interpret the data quickly.

<figure><img src="https://1594793363-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRKSWMBzM9uXdqpjmAlMd%2Fuploads%2FJWUF6dgKgr3QTySTNlzU%2FWhatsApp%20Image%202025-02-10%20at%2013.48.49.jpeg?alt=media&amp;token=93601093-b160-4b13-b698-4863ff274774" alt=""><figcaption></figcaption></figure>

1. **Provenance Tracking**
   * Explore the complete on-chain **provenance records** for any content piece.
   * View detailed modification history, including timestamps, types of changes (e.g., creation, deletion, or edits), and verification events logged on the Hash Network.
   * Navigate through these records seamlessly to verify the evolution of content in a transparent and secure manner.
2. **Export Functionality**
   * Effortlessly export the provenance records in a structured format for compliance, analysis, or record-keeping purposes.
   * This feature is ideal for creators, legal professionals, and researchers requiring permanent evidence of content integrity.

<figure><img src="https://1594793363-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRKSWMBzM9uXdqpjmAlMd%2Fuploads%2FPtTgzgAQlZqB3J5BaVvz%2FWhatsApp%20Image%202025-02-10%20at%2013.50.19.jpeg?alt=media&amp;token=f883145e-7132-4144-84a0-b6e279fb1474" alt=""><figcaption></figcaption></figure>

1. **User-Friendly Integration**
   * The extension integrates seamlessly with Hash Network’s verification ecosystem, offering real-time updates and results.
   * No additional setup is required—just install and start exploring content provenance with ease.

**Availability**

The **Hash Verify Chrome Extension** is currently under active development and will be released soon. Once launched, it will redefine how users interact with and validate content, setting a new standard for trust and transparency in the digital era.

Stay tuned for updates on the release timeline and upcoming features!


# Overview

The C2PA (Coalition for Content Provenance and Authenticity) standard is a vital initiative aimed at ensuring the transparent tracking of digital content’s provenance. By embedding metadata into digital assets, C2PA helps verify their authenticity and integrity throughout their lifecycle. As digital media becomes increasingly widespread, ensuring the traceability of content is crucial to combat misinformation and ensure trust in the digital ecosystem.

The C2PA standard consists of several components—Manifest, Assertion, Action, and Ingredient—that work together to provide a framework for tracking the origin, modifications, and usage of digital content. This standardized metadata allows content creators, businesses, and consumers to verify the content’s authenticity and trace its journey from creation to distribution.

Hash Network ensures compliance with the C2PA standard by leveraging its decentralized, blockchain-powered infrastructure to securely store and manage the metadata associated with content provenance. By utilizing a tamper-proof blockchain, Hash Network enables content authenticity verification in a decentralized, immutable manner.


# Manifest

A **manifest** is the central metadata structure that encapsulates all information about a digital asset, including its creation, history, and related cryptographic details. It serves as the primary container for provenance data, ensuring that the asset's authenticity can be verified at any stage of its lifecycle. Each manifest is uniquely tied to the content it represents and includes fields such as the file title, format, and instance ID, along with cryptographic signatures for validation.

**Example Manifest:**

```
{
  "manifest": {
    "title": "image.jpg",
    "format": "image/jpeg",
    "instance_id": "urn:uuid:abcdef1234567890",
    "claim_generator": "Hash-Network/c2pa-rs/1.0.0",
    "claim_generator_info": {
      "version": "1.0.0",
      "tool": "Hash Network C2PA SDK"
    },
    "ingredients": [
      {
        "title": "image_source.png",
        "format": "image/png",
        "checksum": "sha256:abcdef1234567890"
      }
    ],
    "assertions": [
      {
        "label": "c2pa.actions.created",
        "data": {
          "action": "created",
          "softwareAgent": {
            "name": "AI_Generator_v1",
            "version": "2.3.0"
          }
        }
      }
    ],
    "signature_info": {
      "alg": "Ed25519",
      "issuer": "Hash Network Signing Cert",
      "cert_serial_number": "1234567890"
    }
  }
}

```

The **manifest** is integral to the C2PA Standard as it consolidates all provenance-related data into a single structure. In Hash Network, manifests are stored on-chain to ensure that the metadata is immutable and verifiable. This approach guarantees that the content's history is protected against tampering or unauthorized changes.


# Assertion

An **assertion** is a claim or statement about the content, providing key details about actions or events in the asset’s lifecycle. Assertions allow creators and systems to document specific operations—such as content creation, editing, or distribution—making it possible to track the content's history transparently.

**Example Assertion:**

```
{
  "assertions": [
    {
      "label": "c2pa.actions.created",
      "data": {
        "action": "created",
        "softwareAgent": {
          "name": "content-creation-tool",
          "version": "1.0.1"
        },
        "parameters": {
          "height": 1024,
          "width": 1024
        }
      }
    }
  ]
}

```

Assertions are essential for documenting provenance, as they provide detailed information about every significant event in the content's lifecycle. By integrating the C2PA Standard, Hash Network ensures that assertions are cryptographically tied to the content and securely stored on the blockchain, enhancing transparency and trustworthiness.


# Action

An **action** records a specific operation performed on the content, such as its creation, modification, or distribution. Actions include metadata about the tools or software agents responsible for the operation, as well as contextual details such as timestamps and parameters.

**Example Action:**

```
  "actions": [
    {
      "action": "c2pa.created",
      "timestamp": "2024-12-28T10:00:00Z",
      "softwareAgent": {
        "name": "AI_Generator_v2",
        "version": "3.1.0"
      },
      "parameters": {
        "prompt": "Generate an image of a dog",
        "num_steps": 50,
        "model": "StableDiffusion_v4"
      }
    }
  ]
}

```

Actions provide traceability for every operation affecting the content, ensuring that its lifecycle is fully transparent. Hash Network leverages this principle to ensure that all actions related to content stored on its platform are cryptographically verifiable and securely recorded.


# Ingredient

An **ingredient** represents a source component or asset that contributes to the creation or modification of content. Ingredients are critical for understanding the dependencies and origins of complex digital assets, such as those created from multiple sources.

**Example Ingredient:**

```
{
  "actions": [
    {
      "action": "c2pa.created",
      "timestamp": "2024-12-28T10:00:00Z",
      "softwareAgent": {
        "name": "AI_Generator_v2",
        "version": "3.1.0"
      },
      "parameters": {
        "prompt": "Generate an image of a dog",
        "num_steps": 50,
        "model": "StableDiffusion_v4"
      }
    }
  ]
}

```

Ingredients offer a granular view of how content is built or modified. Hash Network stores ingredient data on-chain, enabling users to verify the origins and dependencies of content with complete transparency and security.


# Compatibility with Hash Network

While the C2PA Standard primarily defines how content provenance is managed and verified, Hash Network extends its utility by ensuring that this provenance data is securely stored on-chain. The platform’s decentralized architecture enhances the integrity of provenance records by making them tamper-proof and permanent. By aligning with C2PA, Hash Network offers a robust solution for developers and platforms seeking a compliant and transparent provenance framework for their digital assets.


# Provenance for AI generated Content

The Hash Network Playground allows users to explore the provenance of AI-generated content in real-time. Here’s how it works:

* **Step 1: Generate an AI Image**\
  Start by entering a descriptive prompt in the "Generate" tab. For example, "A woman having dinner in a restaurant." Once you click on "Generate Image," the AI model (e.g., Stability AI) will create an image based on the prompt.

<figure><img src="https://1594793363-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRKSWMBzM9uXdqpjmAlMd%2Fuploads%2F7o7UzxLgYGw9oAyIt7pN%2FScreenshot%202024-12-29%20at%2011.35.02%E2%80%AFAM.png?alt=media&amp;token=a0ff77c5-9c7a-49a9-9dfa-301b90268de8" alt=""><figcaption><p>Hash Network Playground</p></figcaption></figure>

* **Step 2: View Provenance Details**\
  After generating the image, the provenance details will appear on the right-hand side. These details include:
  * **App or Device used**
  * **Issuer Information**
  * **AI tool used**
  * **Actions**
  * **Credentials**

<figure><img src="https://1594793363-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRKSWMBzM9uXdqpjmAlMd%2Fuploads%2FF28TlNtTnNcl0RxeBVCi%2FScreenshot%202024-12-29%20at%2011.37.30%E2%80%AFAM.png?alt=media&amp;token=8a859372-2d7a-45b2-b3a5-30e7eb3c2e66" alt=""><figcaption><p>Provenance Generation</p></figcaption></figure>

* **Step 3: Check On-Chain Transaction**\
  To verify the provenance on-chain, click the "Check Transaction" button. This provides a direct link to the transaction recorded on the Hash Network testnet, ensuring transparency and immutability of the provenance data.

<figure><img src="https://1594793363-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRKSWMBzM9uXdqpjmAlMd%2Fuploads%2FFrW0AE46IDCR8Y8JlvNm%2FScreenshot%202024-12-29%20at%2011.39.30%E2%80%AFAM.png?alt=media&amp;token=2381478c-46ae-494b-8c3e-d480f170423a" alt=""><figcaption><p>Check Transaction Onchain</p></figcaption></figure>

* **Step 4: Update Provenance**\
  Users can update the generated image and see the provenance automatically updated to reflect the modifications. This showcases the dynamic nature of the provenance data stored both on-chain and within the asset metadata.


# Register Content's Provenance Onchain

The Hash Network Playground allows users to upload their content and register its provenance on-chain. Here’s how it works:

* **Step 1: Upload Content**\
  Navigate to the "Upload" tab. Select the file you wish to upload (e.g., an image or document). This step lets you register the content's provenance, even if it wasn’t created within the playground.

<figure><img src="https://1594793363-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRKSWMBzM9uXdqpjmAlMd%2Fuploads%2F8gD8aZ3Vv2OzsNUzGEvm%2FScreenshot%202024-12-29%20at%201.33.08%E2%80%AFPM.png?alt=media&amp;token=d8ab95bf-566e-4657-9eb3-3dccf1e37cbe" alt=""><figcaption></figcaption></figure>

* **Step 2: View Provenance Details**\
  After uploading, the provenance details will appear on the right-hand side. Similar to AI-generated content, this includes:
  * **App or Device Used**
  * **Issuer Information**
  * I**ngredient**
  * **Issued By**

<figure><img src="https://1594793363-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRKSWMBzM9uXdqpjmAlMd%2Fuploads%2FfF9FtixtYs7GySjcGQMj%2FScreenshot%202024-12-29%20at%201.33.47%E2%80%AFPM.png?alt=media&amp;token=64495ca3-00b8-4fe9-99b0-56fe404ffcfc" alt=""><figcaption></figcaption></figure>

* **Step 3: Check On-Chain Transaction**\
  Once the content is uploaded, click the "Check Transaction" button to verify its registration on-chain. The transaction will provide an immutable record of the provenance data stored on the Hash Network testnet.


# Verify provenance of content

The playground also allows users to verify the provenance of any content uploaded to the Hash Network. Here’s how it works:

* **Step 1: Use the Verify Tab**\
  Navigate to the "Verify" tab. Upload the content for which you want to check provenance. This could be an image, document, or any media asset previously registered on the network.

<figure><img src="https://1594793363-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRKSWMBzM9uXdqpjmAlMd%2Fuploads%2F6NXDaN7ynUdZMqwnUuLe%2FScreenshot%202024-12-29%20at%2012.28.37%E2%80%AFPM.png?alt=media&amp;token=6feb15ee-1b56-4eea-a267-77f75e2bc4b7" alt=""><figcaption></figcaption></figure>

* **Step 2: View Provenance Details**\
  Once uploaded, the system cross-references the content with the provenance data stored on-chain. The right-hand panel will display all the details of the image/content uploaded.

<figure><img src="https://1594793363-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRKSWMBzM9uXdqpjmAlMd%2Fuploads%2FMphot7DkEK6SQuo2S4LD%2FScreenshot%202024-12-29%20at%2012.29.30%E2%80%AFPM.png?alt=media&amp;token=7a821120-620b-4c76-ba18-5751f45ca3f9" alt=""><figcaption></figcaption></figure>


# Network Information

* **Testnet Details**:
  * **Network Name**: Hash Network Testnet
  * **RPC (HTTP)**: `https://hash-testnet.rpc.caldera.xyz/http`
  * **RPC (WS)**: `wss://hash-testnet.rpc.caldera.xyz/ws`
  * **Chain ID**: 4274
  * **Currency Symbol**: HASH
  * **Block Explorer URL**: <https://hash-testnet.explorer.caldera.xyz/>


# Adding Network To Metamask

To interact with the Hash Network Chain, you must add it to your MetaMask wallet.

* **Step 1**: Open MetaMask and navigate to **Settings > Networks > Add Network**.
* **Step 2**: Enter the following details:
  * **Network Name**: Hash Network Testnet
  * **RPC URL (HTTP)**: `https://hash-testnet.rpc.caldera.xyz/http`
  * **Chain ID**: `4274`
  * **Currency Symbol**: HASH
  * **Explorer URL**: <https://hash-testnet.explorer.caldera.xyz/>
* **Step 3**: Save the network. Your MetaMask is now configured to interact with the Hash Network Testnet.


# Contracts

The **Contracts** section outlines the core components and token bridge systems that power the Hash Network ecosystem. These contracts facilitate critical functionalities, including rollup management, bridging, and upgrade execution, across Layer 2 (L2) and Layer 3 (L3).

***

**Core Contracts**

These contracts form the backbone of the Hash Network's infrastructure, enabling seamless operations across the ecosystem:

| **Contract**             | **Address**                                  |
| ------------------------ | -------------------------------------------- |
| Rollup                   | `0x0Ecc426De0511D31F0893dfa72DF881A71ecDBc2` |
| Inbox                    | `0xA669c6e22ba7b459dC7BE6df4A7f68866420f570` |
| Outbox                   | `0x603641BEe7a1d47fA3086Db2663142279C5988A5` |
| Admin Proxy              | `0x294458fc127e3b74790E30818cCCf57Ff986b128` |
| Sequencer Inbox          | `0x9E2Fa1709327719d729d30B960e67379F2712dc6` |
| Bridge                   | `0x8f4b86807499A8696Fa8579C23D16973F11259Dd` |
| Utils                    | `0x29A2405241806531B84A5677A371144f67202bE6` |
| Validator Wallet Creator | `0x4fA05Eddf1A1cb077F66C6a7C130c53De81651A9` |
| Upgrade Executor         | `0xDBe52B4E3223e97E1509f22bB11f3581db599C63` |
| Upgrade Executor L2      | `0x27E03238818439A2297421Be8D0d3c83F6C12a3c` |

***

**L2 Token Bridge Contracts**

The **Layer 2 Token Bridge Contracts** facilitate asset transfers and other bridging operations between the primary and secondary layers.

| **Contract**     | **Address**                                  |
| ---------------- | -------------------------------------------- |
| Custom Gateway   | `0xe35250F5b17CB2C34b531675A5A5740527b754d2` |
| Multicall        | `0x9890A2d94A3fAB71f667A5deA7180A39262D700D` |
| Proxy Admin      | `0x294458fc127e3b74790E30818cCCf57Ff986b128` |
| Router           | `0xad849914530aD8038D239420BbF596518dA831F8` |
| Standard Gateway | `0xABe5C767c3a1652D351C8d5d2F3FABf432D48e0E` |

***

**L3 Token Bridge Contracts**

The **Layer 3 Token Bridge Contracts** extend the token bridging capabilities to the tertiary layer, offering more granular scalability and functionality.

| **Contract**     | **Address**                                  |
| ---------------- | -------------------------------------------- |
| Custom Gateway   | `0x92997BC501AcB606d18B32e5676E369Ddf911Aa6` |
| Multicall        | `0x70D9d170C5C6dA983010B31Cb34dAF6C798ad4eD` |
| Proxy Admin      | `0x9380Fc0C4D6e789934E7cdc4E94d5B099440CBde` |
| Router           | `0xd23b707B4F5B6e5D736f088D38ea1515A7955287` |
| Standard Gateway | `0x9416a00aBdDA5dDbD956985e64b9962bF904A748` |


# Bridges

The **Hash Network Bridge** allows seamless transfer of assets between Hash Network Testnet and other blockchains, enabling interoperability for dApps and users.

**Key Details:**

* **Bridge URL**: [Hash Network Bridge](https://hash-testnet.bridge.caldera.xyz/)
* **Supported Chains**:
  * Base

**How to Use:**

1. Visit the [Hash Network Bridge](https://hash-testnet.bridge.caldera.xyz/).
2. Connect your wallet (e.g., MetaMask).
3. Select the source and destination chains.
4. Choose the asset to transfer and specify the amount.
5. Approve the transaction and complete the bridging process.

**Important Notes:**

* Ensure you have sufficient test tokens for gas fees on both chains.
* Use the **Faucet** to get test HASH tokens if needed.
* Transactions typically take a few minutes to complete, depending on the network load.


# Block Explorer

The **Hash Network Block Explorer** provides a detailed view of on-chain activities on the Hash Network Testnet, including transactions, contract interactions, and wallet balances.

**Explorer URL:**

[Hash Network Block Explorer](https://hash-testnet.explorer.caldera.xyz/)

**Features:**

* **Search**: Look up transactions, blocks, or wallet addresses.
* **Live Updates**: Monitor real-time transaction activity.
* **Contract Verification**: Explore deployed smart contracts and their details.
* **Chain Metrics**: Check network performance and statistics.

**How to Use:**

1. Visit the [Block Explorer](https://hash-testnet.explorer.caldera.xyz/).
2. Enter the transaction hash, block number, or wallet address in the search bar.
3. View detailed information, including timestamps, gas fees, and contract interactions.


# Faucet

Get free test HASH tokens for testing on the Hash Network.

* **How to Use**:
  * Visit the faucet at <https://hash-testnet.hub.caldera.xyz/>
  * Enter your wallet address and click **Request Tokens**.
  * Tokens will be sent to your wallet for use on the testnet.

The faucet ensures you have enough test tokens to try out features like deploying contracts or bridging assets.


