All work will be performed on a fork of the official zksync-era repository, which can be found here.

• Relevant docs for prototyping with a ZK Stack-based chain: https://docs.zksync.io/zk-stack
• Installation instructions: https://docs.zksync.io/zk-stack/running/quickstart
• Relevant bit about validiums and custom DA integrations: https://docs.zksync.io/zk-stack/running/validium
  • For the offsite, we will focus on a two-step challenge:
    • Step 1: sending data to DA and verify it on L1
      • This is the easiest to reach since it requires the least amount of changes on the existing codebase
      • The outcome of this is already an important result since we could propose the changeset upstream and let projects building on ZK Sync use Nomos as one DA option
    • Step 2: sending data to DA without interacting with the L1 at all
      • This requires more changes in the binary and further deviating from the “canonical” way of doing things, and will require a bit more work and hacks
• Prover installation instructions: https://matter-labs.github.io/zksync-era/prover/latest/02_setup.html

As for the codebase, the most interesting points are:

• https://github.com/logos-co/zksync-era/tree/main/core/node/da_clients
  • Interface and implementations of the different supported DA clients
• Server structure docs: https://docs.zksync.io/zk-stack/components/server
  • These are some of the bits we will have to modify/remove in order to morph the L2 into a sovereign rollup 🧙🧙‍♀️🧙‍♂️
• https://github.com/matter-labs/zksync-era/tree/main/core/node/proof_data_handler
  • Prover code

Set up the prover

1. Add a new chain that uses GPU proofs
2. Remove the default era chain from the chains folder
3. Run zkstack containers to spin up DB and L1
4. Run zkstack ecosystem init to deploy L2
5. Run zkstack prover init to initialize the prover DB
6. Follow the guide in https://matter-labs.github.io/zksync-era/prover/latest/03_launch.html, except for the first step where the new chain is created, since we already have that

How the plan could look like

1. Explain the technology, and the architecture
2. List the intended goals: deploy Uniswap on the L2, while posting L2 data to Nomos DA
3. Explain the two-step outcome:
   1. Develop and use Nomos DA adapter while keeping L1 finalization
      1. When this is achieved, someone can start looking into deploying Uniswap on this already
   2. Remove all mentions of L1 finalization, while retaining posting of batches onto Nomos DA
      1. Deploy Uniswap on this new architecture