Native rollups must at some point consume data from L1. The most straightforward example is deposits, but there might be many other use cases. Then, the question is: How can the native rollup access L1 data in a verifiable way? Implementing Deposits by Passing Arbitrary L1 Context tl;dr: The L1 rollup contract constructs l1Context (a subset of L1 state) in memory and passes it to EXECUTE. L2 contracts can read this data and process it in any way. We add a new argument l1Context to EXECUTE: // on L1

The sequencer is one of the core components in the Scroll protocol: it is responsible for maintaining the L2 blockchain. The sequencer also ensures that the user and developer experience on Scroll closely resemble those on Ethereum. It achieves this by maintaining EVM and RPC behaviour that is directly inherited from Ethereum, with very few modifications. The primary functions of Scroll's sequencer are: Collect transactions from L2 and L1. Validate transactions and pack them into L2 blocks. Execute blocks and maintain the L2 blockchain state. Pack blocks into chunks for zkEVM proving. Pack chunks into batches for aggregate proving. Submit batches onto L1 (Ethereum), providing Data Availability.

At Scroll, we are building a fully EVM-compatible zkRollup based on a zkEVM. This is a complex system with multiple components including a sequencer node (go-ethereum fork), prover nodes (aka rollers), a roller manager, a bridge, etc. We are looking for a Site Reliability Engineer to help Scroll provide awesome user and developer experience. Your responsibilities will involve deploying and maintaining a complex set of services, solving and preventing issues, as well as developing and automating processes. This is a remote position. However, we are mainly looking for applicants based in Europe. Job Duties Deploy updates and fixes to the Scroll infrastructure. Investigate and resolve technical issues.