> For the complete documentation index, see [llms.txt](https://docs.creditcoin.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.creditcoin.org/staking/eras-and-sessions.md).

# Eras and Sessions

In Creditcoin's Nominated Proof-of-Stake blockchain, time is organized using three distinct units: blocks, epochs, and eras.

Validator elections are run at the end of each **era**. An era is a period of **24 hours** during which an **active set** of validators is producing blocks and performing other actions on the chain. Not all validators are in the active set and such set changes between eras.

Each era is divided into two **12 hour epochs**, during which validators are assigned as block producers to specific time frames or **slots**. This means that validators know the slots when they will be required to produce a block within a specific epoch, but they do not know all the slots within a specific era. Having epochs adds a layer of security because it decreases the chance of having multiple validators assigned to a slot colluding to harm the network.

Ideally, each slot should produce one **block** every **15 seconds**. A block is the smallest time unit in the Creditcoin blockchain.

| **Unit** | **Time**               | **Reward** |
| -------- | ---------------------- | ---------- |
| Block    | 15 seconds             | 2 CTC      |
| Epoch    | 12 hours (2880 blocks) | 5760 CTC   |
| Era      | 24 hours (2 epochs)    | 11520 CTC  |


---

# 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.creditcoin.org/staking/eras-and-sessions.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.