> For the complete documentation index, see [llms.txt](https://docs.frequencychain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frequencychain.org/12.-energy-data-layer-integration/12.4-on-chain-data-anchoring.md).

# 12.4 On-Chain Data Anchoring

Once validated, the data is committed to the blockchain in a structured format. This process is referred to as data anchoring, where a representation of the data—often in the form of hashes or structured records—is stored on-chain.

This ensures that:

* data becomes immutable once recorded
* it can be referenced by smart contracts
* historical data can be audited and verified

From a technical standpoint, this anchoring process enables developers to build contracts that rely on verifiable external inputs, rather than assumptions or manual updates.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.frequencychain.org/12.-energy-data-layer-integration/12.4-on-chain-data-anchoring.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.