> For the complete documentation index, see [llms.txt](https://polarischain-1.gitbook.io/polarischain/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://polarischain-1.gitbook.io/polarischain/6.-transaction-model/6.2-transaction-lifecycle-and-finality.md).

# 6.2 - Transaction Lifecycle & Finality

Transaction processing follows a strict, deterministic pipeline:

1. **Client Preparation:** Wallet assembles payload (sender, receiver, amount, nonce, type-specific fields).
2. **Pre-Hashing:** Payload is hashed via `BLAKE2b-256`.
3. **Signing:** Hash is signed with sender’s `CRYSTALS-Dilithium2` private key.
4. **Submission:** Signed transaction is routed to a validator via REST API or dedicated TCP listener.
5. **Local Queuing:** Validator enqueues transaction into its local consensus channel (no global mempool gossip).
6. **DAG Inclusion:** Validator includes pending transactions as statements in its next consensus block.
7. **Consensus Commitment:** Block propagates through Mysticeti waves; committed when anchor achieves `2f+1` certified support.
8. **Linearization & Execution:** Committed transactions are extracted into total order; blockchain manager updates balances, asset registries, and identity records.
9. **True Finality:** Once the anchor is committed, all included transactions are cryptographically irrevocable. No probabilistic confirmations.

<br>


---

# 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://polarischain-1.gitbook.io/polarischain/6.-transaction-model/6.2-transaction-lifecycle-and-finality.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.