# Timestamp

### Overview

The Timestamp pallet allows the validators to set and validate a timestamp with each block.

It uses **`inherents`** for timestamp data, which is provided by the block author and validated/verified by other validators. The timestamp can be set only once per block and must be set each block. There could be a constraint on how much time must pass before setting the new timestamp.

### Dispatchable Calls

* **`set`** - sets the current time. When setting the new time, it must be greater than the last one (set into storage) with at least a MinimumPeriod

### Configuration

Timestamp requires to set following constants during the runtime initialisation:

* **`minimumPeriod`** - minimum period between timestamps. Also, minimal interval between two blocks.


---

# 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://subsembly.gitbook.io/subsembly/modules/pre-built/timestamp.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.
