> For the complete documentation index, see [llms.txt](https://docs.arcology.network/arcology-architecture-overview/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arcology.network/arcology-architecture-overview/arbitrator.md).

# Arbitrator

Arbitrator collects all the transaction execution results generated from EUs and look for potential access conflicts. The transactions causing conflicts will be reverted together with all their state transitions.The whole process is completely deterministic.

![](/files/Ic4O7pK3D1NHCjRE9ydI)

Arbitrator determines conflict status based on the following the following conflict model. The Arbitrator service will also send the conflicting information back to the scheduler service.

| Operation                  | Conflict |
| -------------------------- | -------- |
| {Read, Read}               | **✓**    |
| {Read, Write}              | **✗**    |
| {Write, Write}             | **✗**    |
| {Delta Write, Delta Write} | **✓**    |
| {Read, Delta Write}        | **✗**    |
| {Write, Delta Write}       | **✗**    |

> In the best scenario, a fully parallelized program with no conflict point can lead to virtually unlimited speedup, which is only a matter of computational resources available. The key to achieve maximum parallelizability is to avoid conflicts wherever possible.


---

# 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://docs.arcology.network/arcology-architecture-overview/arbitrator.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.