Making account authorization and behavior programmable, enabling features such as alternative authentication, recovery policies, batching, and sponsored execution.

Checking randomly selected pieces of encoded block data to gain confidence that enough data is available for reconstruction without downloading every piece.

A protocol path for submitting a transaction through a settlement layer or alternative queue when a rollup sequencer does not include it normally.

The ability of chains and apps to pass assets and messages without a trusted spreadsheet in the middle.

The common request format for Ethereum-style node APIs.

The time from broadcast to a usable confirmation, distinct from theoretical throughput.

Bitcoin's payment-channel network for cheap, fast transfers that settle back to L1 when channels close.

An assurance about a transaction's expected inclusion, ordering, or execution given before the blockchain's ordinary confirmation or finality process completes.

A scaling system that executes transactions outside its settlement chain and publishes commitments plus sufficient data, using fraud proofs or validity proofs to enforce state-transition rules.

Remote procedure call. The API wallets and apps use to read chain state and broadcast transactions.

The layer that makes transfers final and resolves disputes. For many L2s that layer is Ethereum.

Splitting state or execution across many committees so the network scales beyond one machine.

How many transactions a network can settle per second under its current limits.

A proof that a statement is true without revealing the secret that makes it true.

A rollup that posts a validity proof so L1 can check the new state without re-executing every trade.

A succinct zero-knowledge proof used by Zcash and many ZK rollups to prove a statement without revealing inputs.