The Local Blockchain
Local Protocol separates execution from finality, enabling parallel execution across many environments while preserving a single canonical ledger.
Local Protocol separates execution (where transactions happen) from finality (what the network agrees on). This allows parallel execution across many environments while preserving a single canonical set of ledger facts and canonical snapshot roots for graph-based mechanisms.
Execution architecture
Local Protocol is specified as a single-chain, EVM-compatible appchain with fast Byzantine finality.
Scaling comes from:
- implementation-level parallelism (multi-threaded execution, indexing, batching),
- keeping diffusion computation off the validator critical path (see Optimistic Diffusion Claims and Validator Audits & Penalties),
- committing canonical epoch snapshot roots so claims and audits share one reference frame (see Graph Commitments & Epoch Snapshots).
Markets as logical domains
Markets are policy + accounting domains derived from execution. A marketId (or domainId) is used for policy routing (maturity rules, caps, proof multipliers), accounting, and indexing, while consensus and asset state remain global so claims across markets reference the same canonical epoch commitments.
See: Market Registry
Next Steps
In the next sections, we’ll cover: