# Transaction Lifecycle

1. **Ingestion:** Transactions are pulled from the Data Availability layer.
2. **Interpretation:** Transactions are sent to the Interpreter and executed optimistically in parallel, generating a read/write set for each.
3. **Resolution:** The read/write sets are passed to the Resolver, which identifies instruction-level dependencies and conflicts.
4. **Coordination:** The Coordinator (OCCDA) schedules the transactions.
5. **Re-Execution:** Any instructions identified as conflicted are re-executed in parallel.
6. **Finalization:** The Coordinator finalizes the block's state transition.
7. **Settlement:** The final state root is published to the Settlement layer.
8. **State Management:** State management is handled entirely by the SSMT architecture. The state is not viewed as a single MPT on one machine but as a sharded, distributed database. Access is memory-first for speed, with the sharded cluster of SSDs providing persistence.
9. **Fault Tolerance:** Fault tolerance is built into the Storage (SSMT) layer. Each state shard is stored across different nodes, providing redundancy. The failure of a single node will not halt the network or result in data loss, as the state is replicated and can be recovered from other nodes in the cluster.

<figure><img src="/files/dNeFn4E0rdanGplkiZv0" alt=""><figcaption></figcaption></figure>


---

# 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://docs.altiuslabs.xyz/technical-overview/altius-architecture/transaction-lifecycle.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.