# Content timestamping

<figure><img src="/files/Mhxhi7LldVuxx9R7ccrG" alt=""><figcaption></figcaption></figure>

*Cryptographic hashes are secured on servers or on-chain*

Another approach to potentially tamper-proof authenticity and integrity of digital media is to timestamp the content by hashing the media asset and storing the resulting cryptographic hash on an immutable ledger or in any other trusted storage.

However, despite assertions to the contrary, timestamping cryptographic hashes on public blockchains neither provides information about ownership or attribution, nor does it express a copyright or the possession of any right to the content. It also does not “protect” the copyright of rightsholders. Timestamping only proves access to a hash by the declaring party, which proves the existence of this hash, and subsequently, the existence of the media asset, at a given point in time.

Managing and linking the hash is a difficult task in itself. Cryptographic hashes work securely and reliably in technical environments and systems that are in control of the user or application offering the service. However, they are too sensitive and fragile to be used as a reliable form of content identification or recognition in online media environments with highly incentivized adversaries that can easily manipulate content. The same applies to online platforms that compress, convert, modify or strip metadata from the media files.

Most timestamping services pursue a centralised approach to replicate the identical environment for creation and verification of the cryptographic hash, and thereby ensuring a replication of conditions with no single pixel or character of the asset being changed.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.liccium.com/documentation/context/complementary-solutions/content-timestamping.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.