> For the complete documentation index, see [llms.txt](https://docs.teranode.group/nchain-event/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.teranode.group/nchain-event/independent-records/functional-description/verify-record-+.md).

# Verify Record †

The Verify Record [**†**](/nchain-event/overview/configuration-symbols.md) operation enables you to get nChain Event to verify whether the local copy of your record matches the one on the blockchain. It provides proof of what was written to the blockchain and when it was published (using the timestamp of the block containing the transaction).

Anyone who has the original record and its location on the blockchain can find out whether there is any discrepancy. This may be just be the record creator or any third-party, depending on the use case.

If there is a discrepancy, this is a good indication that the local record has become altered or corrupted and must be recovered from its backup.

<figure><img src="/files/UjSXX3Qf0fG2j3uCNeQx" alt="" width="375"><figcaption></figcaption></figure>


---

# 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.teranode.group/nchain-event/independent-records/functional-description/verify-record-+.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.