Our new testnet upgrade enables smart contract deployment on Scroll. This allows developers to write and deploy their own contracts on Scroll using the same Ethereum developer tools we all know and love!

What's new in the upgrade?

The new version supports the following features:

• Developers will be able to deploy smart contract applications using tooling like Hardhat and Foundry. Because our zkEVM is bytecode compatible with base layer Ethereum, Ethereum smart contracts will work natively on Scroll. We look forward to seeing what applications you are able to build and try out!

• Users can bridge NFTs and user-defined ERC-20s between our Layer 1 and Layer 2 testnets on our upgraded bridge contract. We now support the ERC-20, ERC-721, and ERC-1155 standards.

The upgraded Pre-Alpha Testnet will be the first chance for early developers to experience contract deployment on Scroll and to interact with our infrastructure. As we scale our proving nodes, we will relax the performance-motivated restrictions currently in place and onboard more testers.

How can I sign up and learn more?

While testnet registration is open to anyone, we are permissioning access at this stage as we improve our proving algorithm and scale our proving cluster. Sign up at signup.scroll.io for testnet access as we actively work to scale this up and support more users. Meanwhile, we are excited to open the sign up for developers to get early support at scroll.io/early-dev! Tell us a bit more about yourself and your projects to get prioritized.

• If you already have access, check out our new contract deployment doc and sample deploy repo. We have one line deploy scripts using Hardhat and Foundry ready for you to try!

• For those at DevCon Bogota, we are running a workshop at the ZK Community Hub from 1:30p to 3:00p on Oct 12. Come by in-person to deploy a contract on Scroll with us! We will present more details about the upgrade and performance at 11:00a Oct 13, see event link for more details.

• To learn more about Scroll, check out our website, Twitter, or Discord.

What's next for Scroll?

Soon after this upgrade, we will release our Alpha Testnet. Our community can expect the following features:

• A fully permissionless testnet open to all users without whitelisting.

• Proving throughput improvement with increased compute and batch block verification.

• Generating and aggregating more pieces of the zkEVM proof to be verified on-chain.

As we move step by step towards an eventual mainnet release, we will enable successively more pieces of our final architecture, including a decentralized Roller network and integrations with EVM-native developer tools. Stay tuned to learn more about our progress!

Join us

To become an early tester or contributor, sign up to try out our Pre-Alpha Testnet at signup.scroll.io. In the meantime, if our vision of scaling Ethereum in an open and community-driven way resonates with you, we are looking for values-aligned individuals to help Scroll become the most developer- and user-friendly scaling solution for Ethereum.

• If you are a ZK researcher, ZKP, Go or Solidity developer, or GPU engineer, we are working on many interesting technical challenges at the edge of what’s possible. Come build cutting-edge solutions to these problems with us in the open!

• If you love nurturing and growing ecosystems or communities, we are looking for developer advocates and community organizers to build with us in a community-aligned and user-friendly way.

To learn more about these roles, check out our jobs page. If you want to get straight to the code and build with us, you can find our repos at github.com/scroll-tech and github.com/privacy-scaling-explorations/zkevm-circuits.

In this post, we give an overview of Scroll’s overall architecture. More specifically, we will cover the initial version of Scroll which is composed of a centralized sequencing node and decentralized proving network. We are committed to decentralizing the set of sequencing nodes in the future and will share our design for this in future articles.

Scroll's architecture

The current architecture consists of three infrastructure components (see Figure 1):

• Scroll Node: Constructs L2 blocks from user transactions, commits them to the Ethereum base layer, and passes messages between L1 and L2.

• Roller Network: Generates the zkEVM validity proofs to prove that transactions are executed correctly.

• Rollup and Bridge Contracts: Provides data availability for Scroll transactions, verifies zkEVM validity proofs, and allows users to move assets between Ethereum and Scroll.

In what follows, we detail the role of each of these components.

Scroll Node

The Scroll node is the main way for applications and users to interact with Scroll. It consists of three modules, the Sequencer, Coordinator, and Relayer.

The Sequencer provides a JSON-RPC interface and accepts L2 transactions. Every few seconds, it retrieves a batch of transactions from the L2 mempool and executes them to generate a new L2 block and a new state root. Our sequencer implementation is based on the Go-Ethereum (Geth), one of the most popular Ethereum node implementation. By forking Geth, we can achieve the best compatibility and inherit security that has stood the test of time.

Once a new block is generated, the Coordinator is notified and receives the execution trace of this block from the Sequencer. It then dispatches the execution trace to a randomly-selected Roller from the roller pool for proof generation.

The Relayer watches the bridge and rollup contracts deployed on both Ethereum and Scroll. It has two main responsibilities. First, it monitors the rollup contract to keep track of the status of L2 blocks including their data availability and validity proof. Second, it watches the deposit and withdraw events from the bridge contracts deployed on both Ethereum and Scroll and relays the messages from one side to the other.

Roller Network

The Rollers serve as provers in the network that are responsible for generating validity proofs for the zkRollup. Rollers are expected to utilize accelerators such as GPUs, FPGAs, and ASICs to reduce the proving time and proving cost. Figure 2 shows how a Roller generates the validity proof for each block. The process consists of the following steps:

• A Roller first converts the execution trace received from the Coordinator to circuit witnesses.

• It generates proofs for each of the zkEVM circuits.

• Finally, it uses proof aggregation to combine proofs from multiple zkEVM circuits into a single block proof.

Rollup and Bridge Contracts

Scroll connects to the base layer of Ethereum through the Rollup and Bridge smart contracts. Together, these ensure data availability for L2 transactions and allow users to pass assets and messages between L1 and L2.

The Rollup contract receives L2 state roots and blocks from the Sequencer. It stores state roots in the Ethereum state and L2 block data as Ethereum calldata. This provides data availability for Scroll blocks and leverages the security of Ethereum to ensure that indexers including the Scroll Relayer can reconstruct L2 blocks. Once a block proof establishing the validity of an L2 block has been verified by the Rollup contract, the corresponding block is considered finalized on Scroll.

The Bridge contracts deployed on the Ethereum and Scroll allow users to pass arbitrary messages between L1 and L2. On top of this message passing protocol, we have also built a trustless bridging protocol to allow users to bridge ERC-20 assets in both directions. To send a message or funds from Ethereum to Scroll, users call a sendMessage transaction on the Bridge contract. The Relayer will index this transaction on L1 and send it to the Sequencer for inclusion in an L2 block. Sending messages from Scroll back to Ethereum uses a similar process on the L2 Bridge contract.

How does Scroll's zkRollup work?

Putting these three architectural pieces together, we can now explain the workflow of Scroll's zkRollup, summarized in Figure 3 below.

L2 blocks in Scroll are generated, committed to base layer Ethereum, and finalized in the following sequence of steps:

1. The Sequencer generates a sequence of blocks. For the i-th block, the Sequencer generates an execution trace T and sends it to the Coordinator. Meanwhile, it also submits the transaction data D as calldata to the Rollup contract on Ethereum for data availability and the resulting state roots and commitments to the transaction data to the Rollup contract as state.

2. The Coordinator randomly selects a Roller to generate a validity proof for each block trace. To speed up the proof generation process, proofs for different blocks can be generated in parallel on different Rollers.

3. After generating the block proof P for the i-th block, the Roller sends it back to the Coordinator. Every k blocks, the Coordinator dispatches an aggregation task to another Roller to aggregate k block proofs into a single aggregate proof A.

4. Finally, the Coordinator submits the aggregate proof A to the Rollup contract to finalize L2 blocks i+1 to i+k by verifying the aggregate proof against the state roots and transaction data commitments previously submitted to the rollup contract.

Figure 3 illustrates that Scroll blocks will be finalized on L1 in a multi-step process. Each L2 block will progress through the following three stages until it is finalized.

• Precommitted indicates a block has been proposed by a Sequencer and sent to Rollers. Although Precommitted blocks are not yet a canonical part of the Scroll L2 chain because they have not been posted on the Ethereum base layer, users who trust the Sequencer can choose to take action on them in anticipation.

• Committed indicates the transaction data of this block has been posted on the rollup contract on Ethereum. This ensures that the block data is available, but does not prove that it has been executed in a valid way.

• Finalized indicates the correct execution of transactoins in this block has been proven by verifying a validity proof on-chain on Ethereum. Finalized blocks are considered canonical parts of the Scroll L2 chain.

Putting all of these together, Scroll is able to execute native EVM bytecode on L2 while inheriting strong security guarantees from base layer Ethereum. In the next post in this series, we will explain the workflow for developers to deploy dapps on Scroll and how users can interact with them.

Learn more

We have designed Scroll's architecture to align with our vision and values and our technical principles. In upcoming articles, we explain how Scroll will use this architecture to provide a more scalable user and developer experience on Ethereum. Stay tuned to learn more, and sign up to try out our pre-alpha testnet at signup.scroll.io!

If our vision of scaling Ethereum in an open and community-driven way resonates with you, we are looking for values-aligned individuals to help Scroll become the most developer- and user-friendly scaling solution for Ethereum.

• If you are a ZK researcher, ZKP, Go or Solidity developer, or a GPU engineer, we are working on many interesting technical challenges at the edge of what’s possible. Come build cutting-edge solutions to these problems with us in the open!

• If you love nurturing and growing ecosystems or communities, we are looking for developer advocates and community organizers to make sure we are building in a community-aligned and user-friendly way.

To learn more about these roles and about Scroll, check out our website, Twitter, Discord, or jobs page. If you want to get straight to the code and build with us, you can find our repos at github.com/scroll-tech and github.com/privacy-scaling-explorations/zkevm-circuits.

Our technical principles

1. Ensuring user security

In the context of blockchain scaling solutions, the most important form of security concerns the integrity of user funds and data. Although a scaling solution may offer users additional capabilities, we believe ensuring users maintain access to their funds comes first. For Scroll, this means users should not need to rely on the honesty of Layer 2 nodes for security and can instead take advantage of full Layer 1 security even when transacting on Layer 2. By building on Ethereum according to this principle, we are rooting the security of Scroll in the most secure and decentralized consensus of the Ethereum base layer.

2. Maintaining EVM-equivalence

In addition to giving users additional capabilities, an effective Ethereum scaling solution should give users and developers a seamless migration path from existing dapps and developer tooling. We believe maintaining EVM-equivalence is the best way to achieve this. An EVM-equivalent environment behaves exactly the same as the Ethereum Virtual Machine specification in the Ethereum yellow paper. This means that users and developers can migrate without additional code changes, expensive audits, or disruptive changes to their development workflow.

EVM-equivalence provides substantially stronger guarantees than simple compatibility with the EVM through solutions such as transpilation. Settling for mere compatibility can force users and developers to modify or even completely reimplement large portions of Ethereum’s supporting infrastructure. In addition, maintaining security becomes much more difficult without EVM-equivalence. As a result, to be maximally developer and user friendly, Scroll is EVM-equivalent, not simply EVM-compatible.

3. Efficiency

In order for users to enjoy a great experience on a Layer 2, we believe that:

• Transaction fees should be low, orders of magnitude cheaper than on the base layer.

• Users should experience instant pre-confirmation on the Layer 2 and reasonably fast finality on the base layer (Ethereum in our case).

Though these conditions are easy to satisfy with a centralized operator, in order to preserve security they must continue to hold in a decentralized environment. In the Layer 2 context, we believe Scroll should be as efficient as possible while maintaining user security and decentralization in both Layer 2 and the base layer.

4. Decentralization across all layers of the community

Decentralization is a core property of blockchains that is often overlooked or improperly traded for efficiency. We believe it is one of the most valuable aspects of blockchains and ensures that protocols and communities are vibrant and resilient against censorship or coordinated attacks. We consider decentralization across many aspects of Scroll, including node operators, provers, and the community of developers and users. By building in the open with the community and charting a credible path to decentralizing both proving and sequencing, Scroll is committed to ensuring decentralization across all dimensions.

How our principles lead to Scroll's design

The major design choices for Scroll are naturally motivated by these technical principles.

1. Security and EVM-equivalence lead us to a zkEVM-based zkRollup solution

In building Scroll, security is our first priority. In our zkRollup-based design, the integrity of Layer 2 transactions executed on Scroll is guaranteed by succinct zero-knowledge proofs verified in a smart contract on the Ethereum base layer. This makes Scroll transactions as secure as transactions on the Ethereum base layer itself. As a result, users do not have to place trust in any third party to keep their funds safe -- security comes from the security of the Ethereum base layer and the mathematical guarantees of zero-knowledge cryptography. We believe this is the minimal possible set of trust assumptions, which provides the best security for our users.

After deciding on a zkRollup approach, we had to grapple with making it accessible to users and developers. We quickly realized that achieving EVM-equivalence through a zkEVM was the holy grail. Although breaking equivalence would substantially simplify this task, once we realized building a zkEVM was possible using recent breakthroughs in zero-knowledge cryptography, we decided it was the best choice. By taking on this technically involved and difficult task, Scroll aims to offer the best user and developer experience. Our zkEVM proves the correct execution of native EVM bytecode using succinct ZK proofs, providing guarantees on the state transition function of the EVM itself and allowing Scroll to support Ethereum native developer tooling such as the JSON-RPC interface and transaction format.

2. Decentralization leads us to a decentralized prover network

In designing our zkEVM, we quickly realized putting the EVM into a ZK proof would result in a large proving overhead due to incompatibility between native fields. To reduce time to finality on Layer 1 resulting from this proving time, we decided to build our Roller network, a permissionless and decentralized network of provers who generate proofs for Scroll Layer 2 blocks.

There are two major technical benefits of our decentralized prover network:

• We have designed our proving infrastructure to be highly parallelizable. This means that Scroll is able to massively scale proving compute simply by adding more proving nodes.

• The community will be incentivized to build substantially better hardware solutions and run provers themselves instead of relying only on the Scroll team in a centralized way. To bootstrap in the initial phase of the network, we are building GPU prover solutions internally which we will open-source for public usage. As this matures, we are exploring ASIC and FPGA solutions with several hardware companies. In the long run, we look forward to vibrant competition in this domain and firmly believe that latency and cost for proof generation will decrease exponentially.

Finally and most importantly, beginning with this first step of decentralizing the prover is a credible commitment to our principles of community engagement and decentralization. As Scroll approaches mainnet, we plan to also decentralize the sequencer alongside our prover network, providing greater censorship resistance and robustness for the protocol.

3. Efficiency leads us to focus on open research-driven innovation

To make Scroll's zkEVM practical under the strong constraints imposed by security and decentralization, we leveraged innovative research-driven solutions from the entire community. Our zkEVM design integrates recent breakthroughs in proof systems, proof aggregation, and ZK hardware acceleration, just to name a few. Our open development approach has allowed us to work with the PSE (Privacy and Scaling Explorations) group at the Ethereum Foundation and other collaborators to find the best ideas, and we believe this open-source research approach will produce the best and most efficient solution.

As we approach the first production version of our zkEVM, we continue to focus on optimization and integrating the newest and best techniques. In this vein, we are currently exploring:

• How data blobs post-danksharding can improve Scroll efficiency.

• How to co-optimize Scroll's zkEVM with new hardware-friendly ZK algorithms

• How to expose new ZK primitives to Layer 2 application developers

📜Tying it all together

The technical principles outlined in this article have led Scroll to a protocol design which aligns with the existing Ethereum community and provides a scaling path for the future billions of users who are not yet on-chain. In the next few weeks, we will release more posts with concrete details about Scroll's architecture and the corresponding user and developer experience. Stay tuned to learn more about those and sign up to try out our pre-alpha testnet at signup.scroll.io!

If our vision of scaling Ethereum in an open and community-driven way resonates with you, we are looking for values-aligned individuals to help Scroll become the most developer- and user-friendly scaling solution for Ethereum.

• If you are a ZK researcher, ZKP, Go or Solidity developer, or a GPU engineer, we are working on many interesting technical challenges at the edge of what’s possible. Come build cutting-edge solutions to these problems with us in the open!

• If you love nurturing and growing ecosystems or communities, we are looking for developer advocates and community organizers to make sure we are building in a community-aligned and user-friendly way.

To learn more about these roles and about Scroll, check out our website, Twitter, Discord, or jobs page. If you want to get straight to the code and build with us, you can find our repos at github.com/scroll-tech and github.com/privacy-scaling-explorations/zkevm-circuits.

If you’d like to be an early tester, sign up at signup.scroll.io for access. We will invite as many testers as possible while we drive towards a permissionless, public release.

What’s in the pre-alpha testnet?

This initial release will be run on a private PoA fork of Ethereum (the testnet L1) operated by Scroll. On top of this private chain, we will run a testnet Scroll L2 supporting the following features:

• Users will be able to play with a few key demo applications such as a Uniswap fork with familiar web interfaces such as Metamask.

• Users will be able to view the state of the Scroll testnet via block explorers.

• Scroll will run a node that supports unlimited read operations (e.g. getting the state of accounts) and user-initiated transactions involving interactions with the pre-deployed demo applications (e.g. transfers of ERC-20 tokens or swaps of tokens).

• Rollers will generate and aggregate validity proofs for part of the zkEVM circuits to ensure a stable release. In the next testnet phase, we will ramp up this set of zkEVM circuits.

• Bridging assets between these testnet L1 and L2s will be enabled through a smart contract bridge, though arbitrary message passing will not be supported in this release.

Scroll’s pre-alpha testnet will be the first chance for early users and developers to interact with our infrastructure and experience dapp workflows on Scroll. As we scale our node infrastructure, we will relax some of the performance-motivated restrictions and onboard more testers.

What’s next for Scroll?

Soon after our pre-alpha testnet, we will be deploying a more open and permissionless alpha testnet. This will be deployed on a public Ethereum testnet and will be open to the public. In particular, our community can expect the following features:

• Allowing developers to deploy smart contracts

• Allowing anyone to run an archival Scroll node

• Generating and aggregating more pieces of the zkEVM proof to be verified on-chain

As we move step by step towards an eventual mainnet release, we will enable successively more pieces of our final architecture, including a decentralized Roller network and integrations with EVM-native developer tools. In the next few weeks, we will release a series of expository articles and posts explaining Scroll’s architecture and the technical vision that has informed Scroll’s development decisions. Stay tuned to learn more about these!

Scroll’s Release Philosophy

Scroll’s plan for scaling Ethereum and serving billions of users and developers is a long-term roadmap that requires careful consideration and execution. We firmly believe in the future of the zkEVM as a key to scaling Ethereum, and as such, are committed to releasing it in a way that allows us to work through any challenges in a focused manner and incorporate feedback alongside our roadmap.

By giving users, developers and the broader community progressively more functionality to test instead of releasing all features at once, we aim to isolate any bugs and UX difficulties early and often, allowing us to build towards the most robust, scalable solution that will stand the test of time.

📜Join us and learn more

To become an early tester or contributor, sign up to try out our pre-alpha testnet at signup.scroll.io. In the meantime, if our vision of scaling Ethereum in an open and community-driven way resonates with you, we are looking for values-aligned individuals to help Scroll become the most developer- and user-friendly scaling solution for Ethereum.

• If you are a ZK researcher, ZKP, Go or Solidity developer, or a GPU engineer, we are working on many interesting technical challenges at the edge of what’s possible. Come build cutting-edge solutions to these problems with us in the open!

• If you love nurturing and growing ecosystems or communities, we are looking for developer advocates and community organizers to make sure we are building in a community-aligned and user-friendly way.

To learn more about these roles and about Scroll, check out our website, Twitter, Discord, or jobs page. If you want to get straight to the code and build with us, you can find our repos at github.com/scroll-tech and github.com/privacy-scaling-explorations/zkevm-circuits.

We have long believed that rollups are the only viable way today to scale blockchains without sacrificing decentralization and security. However, until recently, technical obstacles meant that they were impractical to scale, driving users to alternative Layer 1s and sidechains, where scalability comes at a cost. Early last year, as researchers working in this field, we realized recent breakthroughs in ZK proof systems and hardware acceleration meant it was finally practical to build a general purpose EVM-equivalent ZK-rollup. Using the magic of ZKPs, this removes the tradeoff between security and scalability, offering the best solution for blockchain users and developers -- minimal trust assumptions, fast finality, and seamless migration from the base layer.

While coming to these ideas, we were inspired by the community-centric, open and collaborative values of the Ethereum community. In addition to technical considerations, we believe this cultural and social bonding creates a robust foundation for a global settlement layer and is hardly matched by any other crypto community.

With this in mind, we set out to build Scroll -- an EVM-equivalent ZK-rollup in early 2021 as part of the vibrant Ethereum ecosystem. Scroll uses zkEVM as its core component to prove the native EVM execution trace and leverages a decentralized proving network to solve the efficiency problem on the prover side. As we move closer to a public release one year in, this post lays out our vision and the values that inspired this effort.

Our vision and values

We believe that decentralized computing platforms will play such a crucial role that they should not belong to any one team or company but instead uphold and promote principles representing the broader community. Like Ethereum, we expect Scroll to be shaped by the community over time, but we begin with the following core values:

1. Empowering humanity - starting with blockchain developers and users

Scroll aims to scale blockchains so that it can be assessible for billions of users. This requires making them both scalable and cheap enough to be accessible for all as well as being secure and easy-to-use for the ordinary user.

The current state of the Ethereum fee market means that high-stake applications such as DeFi and NFT trading are crowding out non-financial use cases as well as making Ethereum inaccessible to ordinary users with smaller amounts of capital. By using ZK-powered magic, Scroll will increase transaction throughput and reduce fees dramatically. It will unlock the potential for these new applications and users. We are excited to see new application layer innovations which will result in due course.

While achieving this, we believe Ethereum scaling solutions must meet developers and users where they are. That means giving them the benefits of scaling while minimizing any obstructions to their current workflows and interfaces. By starting with an EVM-equivalent solution, we allow existing applications and developer tooling to migrate from Ethereum to Scroll without deep modifications or rewrites.

Of course, we won't stop there; after this first step, we plan to add experimental new features extending EVM's capabilities to allow developers to create richer user experiences on Scroll. By acting as a live proving ground for these VM-level changes, Scroll will provide users access to bleeding-edge applications and at the same time assessing demand for experimental features to later be upstreamed to the base layer EVM itself.

2. Build in the open with the community

Scroll is built to be community-centric and fully open-source from day one. We believe such important technology should be open to everyone to understand and audit. We use public specs and repos, and we are collaborating with community members from the Ethereum Foundation Privacy and Scaling Explorations team to build the zkEVM in the open.

When building a platform which can define ownership of financial assets, the ability to openly audit and verify the code is essential. Otherwise, what if the platform is faking proofs or not actually following the protocol? By being open-source, we enable a fundamental level of community trust in Scroll. Even in the development phase, anyone can check on our progress simply by viewing our Github repos. This forces us to be transparent and responsible to our community.

From a developer's perspective, building in the open leads to more secure and better designed systems. By virtue of being accessible, Scroll's code constantly receives both internal and external peer review. Moreover, by implementing designs and improvements from community contributors, such open systems are able to aggregate the best ideas from a growing community of values-aligned developers.

We believe the open-source DNA at the very heart of Scroll will make it the most secure and robust ZK-rollup, and we will continue collaborating with the community and contributing our solutions back to Ethereum. Our ultimate goal is to advance the end goal of Ethereum scaling -- "zk-SNARK everything".

3. Fight for decentralization and censorship resistance

While building towards greater blockchain scalability, we believe it is essential to preserve the core properties of decentralization and censorship resistance that makes Ethereum so powerful. As an end goal, Scroll aims to achieve the same levels of decentralization and censorship resistance as base layer Ethereum itself, although we will approach these step by step.

From the beginning, we view the safety of user assets as paramount and will preserve the same security guarantees as Layer 1. By using Ethereum for both consensus and data availability, we inherit the same level of decentralization. Even in the case of a catastrophic failure, we are building forced exit into the protocol so that users are able to withdraw their funds.

Censorship resistance is more challenging to achieve for rollups, and we are approaching it step by step. First, we have designed a decentralized proving protocol which allows rollup proofs to be outsourced to a community of Rollers. We hope to foster a robust Roller ecosystem competing to improve prover performance with hardware acceleration, and more importantly, enable users to run prover themselves and force their transactions to a rollup batch in case of the censorship. As a second step, we aim to achieve full decentralization by decentralizing the sequencer. By then, anyone will be able to run a sequencer so that transactions cannot be censored. This final step is an area of active research, and we hope to build it in conjunction with the community.

📜Join us and learn more

If our vision of scaling Ethereum in an open and community-driven way resonates with you, we are looking for values-aligned individuals to help Scroll become the most developer- and user-friendly scaling solution for Ethereum.

• If you are a ZK researcher, ZKP, Go or Solidity developer, or a GPU engineer, we are working on many interesting technical challenges at the edge of what’s possible. Come build cutting-edge solutions to these problems with us in the open!

• If you love nurturing and growing ecosystems or communities, we are looking for developer advocates and community organizers to make sure we are building in a community-aligned and user-friendly way.

To learn more about these roles and about Scroll, check out our website, Twitter, Discord, or jobs page. If you want to get straight to the code and build with us, you can find our repos at github.com/scroll-tech and github.com/privacy-scaling-explorations/zkevm-circuits.