> 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/2.-architecture-overview/2.1-transaction-lifecycle.md).
# 2.1 Transaction Lifecycle
Understanding how transactions move through the network is essential for developers.
When a user submits a transaction, it is first broadcast to the network and collected by Cluster nodes. These nodes include the transaction in a candidate block and propose it for validation.
Sync nodes then independently validate the block by executing all transactions and verifying state changes. Once validated, Vault nodes perform cryptographic checks to ensure integrity and correctness before the block is finalized.
This multi-stage validation process ensures that every transaction undergoes independent verification across multiple layers, reinforcing both security and consistency.
---
# 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/2.-architecture-overview/2.1-transaction-lifecycle.md?ask=&goal=
```
`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.
