Overview

A Short Overview of Arcology's Core Technologies

What is Arcology

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 Ethereum rollup 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:

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.

Execution Model

Optimistic concurrency – multiple unmodified EVM instances run in parallel; conflicts detected after execution.

Pessimistic concurrency – accounts declared and locked before execution.

Conflict Handling

Detects conflicts post‑execution; rolls back and retries/reschedules only the conflicting transactions.

Aborts immediately if undeclared account is accessed; no retry.

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

Programming Model

EVM‑equivalent – existing Solidity contracts run without changes; using the Concurrent Library can eliminate all contention.

Solana VM — requires programs to explicitly declare all accounts they will access; undeclared accesses fail.

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.

Horizontal Scaling

multi‑core + multi‑machine cluster. Built‑in multi‑machine per node for scaling.

single‑machine execution per validator.

MEV Protection

Parallel execution removes transaction ordering manipulation → eliminates sandwich MEV.

MEV possible if ordering not neutralized before execution.

Last updated