# Overview

Arcology is a **parallel-execution blockchain** built for high-throughput, resource-intensive dApps. It leverages multi-core, multi-threaded architectures to process transactions concurrently with strict state consistency, achieving tens of thousands of TPS and surpassing existing high-performance blockchains.

Arcology also goes further beyond parallel execution. — it not only supports true parallel processing but also provides developer tools that make it easy to write conflict-free smart contracts that fully benefit from parallel execution (most existing contracts do not).

## Core Technologies

Parallel Processing is the most effective way to scale in computer science. Supercomputers, AI, quantum computing—every field scales with parallel processing. Blockchain should too. 

Arcology is a parallel network capable of processing multiple transactions simultaneously. It can handle tens of thousands of transactions per second, **outperforming all existing high-performance blockchains.**

Arcology has a parallel processing-focused architecture, a redesign of traditional, sequential-centric blockchain systems. It not only delivers deterministic parallel execution but also removes key Ethereum bottlenecks, such as slow storage access.

**For a deep dive, please check out the following topics:**

* [**Inter-EVM Parallel Execution**](https://doc.arcology.network/parallel-execution-design/eu/parallelize-evm) – EVM-equivalent and fully composable, enabling multiple EVM instances to run in parallel.
* [**Hybrid Concurrency Control** ](https://doc.arcology.network/parallel-execution-design/concurrency-control)– Blockchain-native concurrency control for parallel execution.
* [**Built-in Conflict Detection & Migration**](https://doc.arcology.network/parallel-execution-design/conflict-detection) – Identifies state conflicts in real time and moves conflicting transactions to later generations for resolution.
* [**Storage** ](https://doc.arcology.network/parallel-execution-design/storage)– How dual storage system with flattened database for execution and Merkle Patricia Trie for consensus, enabling fast reads, write and deterministic updates.
* [**Concurrent library for Developers**](https://doc.arcology.network/arcology-concurrent-programming-guide/overview) – APIs and data structures that help developers build contention-free smart contracts optimized for parallel execution.
* [**Event-Driven, Microservice-Based Architecture** ](https://doc.arcology.network/parallel-execution-design/in-node-horizontal-scaling)– Scale the nodes horizontally beyond a single machine.

### Comparison With Other L2s

Layer 2 solutions aim to overcome Ethereum’s scalability and cost challenges, but many still face limitations in throughput, fee stability, and security. Arcology redefines these benchmarks, delivering unmatched performance and efficiency.

| Network      | Gas Limit / sec   | TPS @21k gas/tx | Scaling Model                            |
| ------------ | ----------------- | --------------- | ---------------------------------------- |
| **Optimism** | \~2.5M            | \~119           | Single‑threaded, fixed block limit       |
| **Arbitrum** | \~7M              | \~333           | Single‑threaded, dynamic block limit     |
| **Arcology** | **2B+ @16 cores** | **10k–15k+**    | **Parallel, multi‑core & multi‑machine** |

### Comparison With Solana

Both achieve high throughput via parallel execution, but Arcology is Ethereum‑native, cluster‑scalable, and runs unmodified Solidity with **tools** to **eliminate contention entirely**.

| **Aspect**                           | **Arcology**                                                                                                                                | **Solana**                                                                                                                 |
| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| **Ethereum Compatibility**           | 100% EVM‑equivalent – works with Ethereum tooling and libraries.                                                                            | Not EVM‑compatible; requires rewrite to Solana’s model.                                                                    |
| **Parallel Execution Model**         | **Optimistic concurrency** – multiple unmodified EVM instances run in parallel; **conflicts detected *****after***** execution**. | **Pessimistic concurrency** – accounts declared and locked **before execution**. Out of scope access will cause reversion. |
| **Granularity of Conflict Tracking** | Storage‑slot level. With the **Concurrent Library**, even concurrent writes to the ***same***** variable** can be safe.                | **Account‑level** – any overlap in declared accounts causes a conflict.                                                    |
| **Determinism Guarantee**            | Guaranteed                                                                                                                                  | Guaranteed                                                                                                                 |
| **Developer Overhead**               | No need to predict access patterns; optional **Concurrent Library** lets devs eliminate contention entirely.                                | High – incorrect declarations fail execution and limit parallelism.                                                        |
| **Storage Architecture**             | Dual storage: parallelized execution storage + async‑updated Ethereum MPT.                                                                  | Account‑based storage model.                                                                                               |