Secuenciador
Un sequencer es un nodo especializado responsable de ordenar y procesar transacciones en una blockchain, particularmente en soluciones de escalado de capa 2 como rollups, para mejorar la eficiencia y reducir los costos.
Un sequencer juega un papel fundamental en la tecnología blockchain, especialmente dentro de las soluciones de escalado de capa 2. Su función principal es recopilar transacciones de los usuarios, ordenarlas y luego enviarlas a la blockchain de capa 1 subyacente. Este proceso asegura que las transacciones se procesen en una secuencia específica, lo cual es crucial para el estado correcto de la blockchain.
El concepto de un sequencer ha ganado prominencia con el auge de los rollups, como los optimistic y ZK-rollups. Estas soluciones tienen como objetivo mejorar la escalabilidad de las blockchains ejecutando transacciones fuera de la cadena y luego enviando los datos de la transacción a la cadena principal. El sequencer es responsable de manejar estas transacciones fuera de la cadena, agruparlas y proponerlas a la capa 1.
La eficiencia de un sequencer impacta directamente en la experiencia del usuario. Al ordenar y procesar las transacciones rápidamente, un sequencer puede reducir la latencia de las transacciones y proporcionar tiempos de confirmación más rápidos. La descentralización de los sequencers es un área de desarrollo en curso, con esfuerzos para crear sistemas más robustos y seguros para prevenir puntos únicos de falla y censura.
graph LR
Center["Secuenciador"]:::main
Pre_layer_2["layer-2"]:::pre --> Center
click Pre_layer_2 "/terms/layer-2"
Pre_transaction["transaction"]:::pre --> Center
click Pre_transaction "/terms/transaction"
Rel_optimistic_rollup["optimistic-rollup"]:::related -.-> Center
click Rel_optimistic_rollup "/terms/optimistic-rollup"
Rel_zk_rollup["zk-rollup"]:::related -.-> Center
click Rel_zk_rollup "/terms/zk-rollup"
Rel_mev["mev"]:::related -.-> Center
click Rel_mev "/terms/mev"
classDef main fill:#7c3aed,stroke:#8b5cf6,stroke-width:2px,color:white,font-weight:bold,rx:5,ry:5;
classDef pre fill:#0f172a,stroke:#3b82f6,color:#94a3b8,rx:5,ry:5;
classDef child fill:#0f172a,stroke:#10b981,color:#94a3b8,rx:5,ry:5;
classDef related fill:#0f172a,stroke:#8b5cf6,stroke-dasharray: 5 5,color:#94a3b8,rx:5,ry:5;
linkStyle default stroke:#4b5563,stroke-width:2px;
🧠 Prueba de conocimiento
🧒 Explícalo como si tuviera 5 años
Think of a sequencer like a traffic controller for a busy highway exit ([Layer 2](/es/terms/layer-2)). It gathers all the cars (transactions) trying to get on the highway, lines them up neatly, and sends them onto the main road ([Layer 1](/es/terms/layer-1)) all at once, making things faster and cheaper.
🤓 Expert Deep Dive
In the context of optimistic and zero-knowledge rollups, the sequencer acts as the central orchestrator responsible for [transaction ordering](/es/terms/transaction-ordering) and state transitions off-chain. It receives a stream of user-submitted transactions (often via an RPC endpoint), validates their basic format and signature, and enqueues them into a mempool. The sequencer then deterministically orders these transactions, typically based on arrival time or a fee-market mechanism (e.g., EIP-1559-like structures if applicable), and executes them against the current rollup state. The result of this execution is a new state root, which is then committed to the layer-1 blockchain. Crucially, the sequencer batches multiple transactions into a single state transition. This batching is what enables the significant gas cost savings and throughput increases characteristic of rollups. For optimistic rollups, the sequencer constructs a proposed state transition and submits a transaction to the L1 containing the compressed transaction data and the resulting state root. A challenge period follows, during which anyone can submit a fraud proof if they detect an invalid state transition. For ZK-rollups, the sequencer not only orders and executes transactions but also generates a validity proof (e.g., a ZK-SNARK or ZK-STARK) that mathematically guarantees the correctness of the state transition. This proof, along with the transaction data and the new state root, is submitted to the L1 verifier contract. Decentralization of the sequencer is a key research area, with proposed solutions including shared sequencers, sequencer pools, and randomized leader election to mitigate censorship and single points of failure. The sequencer's internal logic often involves managing state forks, handling reorgs, and ensuring atomicity of batches.