Architecture Overview

Matrix adopts a purely execution-oriented rollup architecture: BNB Chain is responsible for ordering and data availability, while Matrix focuses exclusively on execution. The system is intentionally minimal—there is no sequencer, no administrative control, and the entire state can be reconstructed directly from BNB.

A simplified overview of the pipeline is as follows:

L1: Users submit Matrix payloads as BNB transactions to the Inbox (an ownerless EOA). BNB handles transaction inclusion, ordering, and provides permanent data availability.

Matrix-node: Matrix-node reads BNB blocks, extracts Inbox calldata, derives the canonical Matrix input stream, and constructs L2 batches.

Matrix-geth: Matrix-geth executes all batches, maintains the full EVM state, and exposes a standard RPC interface to applications.

Because all inputs originate from BNB, and Matrix introduces no upgradable components or privileged roles, the system is fully replayable, censorship-resistant, and cannot be halted externally unless BNB itself ceases operation.