A rollup whose transaction sequencing is driven by the Layer 1 base chain's proposers rather than a dedicated centralized sequencer. L1 proposers permissionlessly include rollup blocks as part of L1 blocks, inheriting Ethereum's censorship resistance, liveness, and decentralization. The trade-off is higher latency (constrained by L1 block times), addressed through preconfirmation mechanisms.
Start with the shortest useful explanation before going deeper.
A rollup whose transaction sequencing is driven by the Layer 1 base chain's proposers rather than a dedicated centralized sequencer. L1 proposers permissionlessly include rollup blocks as part of L1 blocks, inheriting Ethereum's censorship resistance, liveness, and decentralization. The trade-off is higher latency (constrained by L1 block times), addressed through preconfirmation mechanisms.
Use the quick analogy first so the term is easier to reason about when you meet it in code, docs, or prompts.
Think of it as a building block that connects one definition to the larger Solana system around it.
Place the term inside its Solana layer so the definition is easier to reason about.
Shared crypto concepts that frame the broader ecosystem.
Turn the term from vocabulary into something operational for product and engineering work.
This term unlocks adjacent concepts quickly, so it works best when you treat it as a junction instead of an isolated definition.
Use this compact block when you want to give an agent or assistant grounded context without dumping the entire page.
Based Rollup (based-rollup) Category: Blockchain General Definition: A rollup whose transaction sequencing is driven by the Layer 1 base chain's proposers rather than a dedicated centralized sequencer. L1 proposers permissionlessly include rollup blocks as part of L1 blocks, inheriting Ethereum's censorship resistance, liveness, and decentralization. The trade-off is higher latency (constrained by L1 block times), addressed through preconfirmation mechanisms. Aliases: L1-Sequenced Rollup Related: Rollup, Sequencer, Preconfirmation
Use glossary context, relationships, mental models, and builder paths to get structured answers instead of generic chat output.
Optional: paste Anchor, Solana, or Rust code so the Copilot can map primitives back to glossary terms.
The Copilot will answer using the current term, related concepts, mental models, and the surrounding glossary graph.
These branches show which concepts this term touches directly and what sits one layer beyond them.
A Layer 2 scaling technique that executes transactions off-chain, bundles them, and posts compressed data back to L1. Optimistic rollups assume transactions are valid and use fraud proofs for disputes (7-day challenge period). ZK rollups generate cryptographic validity proofs for every batch. Rollups inherit L1 security while providing 10-100x throughput improvement.
The entity responsible for ordering, batching, and submitting transactions in a Layer 2 rollup. Most rollups currently use a single centralized sequencer operated by the rollup team. Decentralized and shared sequencer designs (Espresso, Astria) distribute this power across a network of operators, enabling cross-rollup atomic composability and reducing single points of failure.
A credible, collateral-backed promise from a block proposer or sequencer that a transaction will be included in a future block, providing near-instant soft confirmation before on-chain finality. Preconfirmations address latency in based rollups where Ethereum's 12-second block time is too slow for UX. Implementations achieve sub-10ms guarantees, secured by restaked ETH with slashing for broken commitments.
These are the next concepts worth opening if you want this term to make more sense inside a real Solana workflow.
These entries are easy to mix up when you are reading quickly, prompting an LLM, or onboarding into a new layer of Solana.
A Layer 2 scaling technique that executes transactions off-chain, bundles them, and posts compressed data back to L1. Optimistic rollups assume transactions are valid and use fraud proofs for disputes (7-day challenge period). ZK rollups generate cryptographic validity proofs for every batch. Rollups inherit L1 security while providing 10-100x throughput improvement.
Glossary entries become useful when they are connected. These links are the shortest path to adjacent ideas.
A Layer 2 scaling technique that executes transactions off-chain, bundles them, and posts compressed data back to L1. Optimistic rollups assume transactions are valid and use fraud proofs for disputes (7-day challenge period). ZK rollups generate cryptographic validity proofs for every batch. Rollups inherit L1 security while providing 10-100x throughput improvement.
The entity responsible for ordering, batching, and submitting transactions in a Layer 2 rollup. Most rollups currently use a single centralized sequencer operated by the rollup team. Decentralized and shared sequencer designs (Espresso, Astria) distribute this power across a network of operators, enabling cross-rollup atomic composability and reducing single points of failure.
A credible, collateral-backed promise from a block proposer or sequencer that a transaction will be included in a future block, providing near-instant soft confirmation before on-chain finality. Preconfirmations address latency in based rollups where Ethereum's 12-second block time is too slow for UX. Implementations achieve sub-10ms guarantees, secured by restaked ETH with slashing for broken commitments.
These entries live beside the current term and help the page feel like part of a larger knowledge graph instead of a dead end.
A distributed, append-only ledger that records transactions in cryptographically linked blocks. Each block contains a hash of the previous block, forming an immutable chain. Nodes in the network maintain copies of the ledger and reach agreement through consensus mechanisms. Blockchains enable trustless, decentralized record-keeping without a central authority.
The protocol by which nodes in a distributed network agree on the current state of the ledger. Common mechanisms include Proof of Work (Bitcoin), Proof of Stake (Ethereum, Solana), and BFT variants. Consensus ensures all honest nodes converge on the same transaction history despite potential network delays or malicious actors.
A consensus mechanism where validators are selected to produce blocks based on the amount of cryptocurrency they have staked (locked) as collateral. PoS is energy-efficient compared to Proof of Work. Misbehaving validators risk losing their stake (slashing). Solana, Ethereum (post-Merge), Cosmos, and Cardano use PoS variants.
A consensus mechanism where miners compete to solve computationally expensive puzzles to produce blocks and earn rewards. PoW provides strong security (51% attack resistance) but is energy-intensive. Bitcoin and pre-Merge Ethereum use PoW. The difficulty adjusts to maintain target block times regardless of total network hash power.