Documentation Index
Fetch the complete documentation index at: https://docs.plasma.org/llms.txt
Use this file to discover all available pages before exploring further.
Plasma’s architecture combines a high-performance consensus layer with Ethereum’s EVM execution model. This modular design gives developers the tools they expect from Ethereum, with performance designed for stablecoin payment workloads at global scale.
At its core, Plasma uses PlasmaBFT, a pipelined implementation of Fast HotStuff, as its consensus layer. Execution is handled by a Reth-based client, a modern Ethereum execution engine written in Rust. These two components communicate through the Engine API in a clean, loosely coupled architecture.
In this model:
- PlasmaBFT handles block sequencing and finality
- Reth handles state transition, transaction execution, and EVM logic
This separation allows Plasma to inherit full EVM compatibility without modification. Every contract, opcode, and call behaves exactly as it would on Ethereum mainnet. Developers can rely on existing tooling, libraries, and contract logic without compromise.
What changes is performance. PlasmaBFT can propose and finalize blocks in rapid succession without relying on slot-based finality or external gadgets. The consensus pipeline allows parallel processing of consensus steps, reducing latency and increasing throughput.
In the sections that follow, we’ll go deeper into each layer of the system (consensus and execution) and outline how Plasma evolves to support high-volume payment flows at scale. The Core Protocol roadmap describes the chain-level changes planned to extend this foundation for payments-specific workloads, including dedicated payment lanes, faster finality, and protocol-native account features.
