> For the complete documentation index, see [llms.txt](https://pijschain.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pijschain.gitbook.io/whitepaper/system-architecture/consensus-mechanism-pos/time-structure.md).

# Time Structure

PIJSChain organizes time around three core units:

| Concept            | Description                                                                                               |
| ------------------ | --------------------------------------------------------------------------------------------------------- |
| Slot               | The minimum time unit, corresponding to one block                                                         |
| Aggregation Period | A fixed number of Slots during which heartbeat signatures are aggregated and the online bitmap is updated |
| Epoch              | A larger unit composed of multiple Slots, serving as the base cycle for reward settlement                 |

Within each Epoch, the protocol proceeds through a structured process:

1. Epoch Boundary\
   All key state variables from the previous epoch are frozen, including the staking-node set, staking data, online bitmap, and reward parameters. This creates an immutable settlement baseline.<br>
2. Reward Distribution Window\
   During the early part of the epoch, rewards from the previous epoch are computed and distributed in batches.<br>
3. Periodic Aggregation Points\
   At regular intervals, block producers aggregate staking-node heartbeat proofs and update the online bitmap.<br>
4. Normal Transaction Processing\
   During the remainder of the epoch, user transactions are processed as usual.<br>

This structure ensures that reward settlement is based on stable snapshots rather than continuously changing state.


---

# 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:

```
GET https://pijschain.gitbook.io/whitepaper/system-architecture/consensus-mechanism-pos/time-structure.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.