← Quickstarts
Run the EEZ Devnet with Kurtosis
PRE-MAINNET
STEP 1 OF 3
NEXT: How to deploy the protocol →
PREREQS + SUBMODULE
Linux host
Docker
Kurtosis CLI
Foundry v1.7.1
Bash
Git
GNU timeout
jq
curl
openssl
$ git submodule update --init --recursive \
eez-core-protocol
→
eez-core-protocol/ — contract source pulled in
A Linux host running Docker, plus Kurtosis, Foundry v1.7.1 and a handful of common CLI tools — with free space to build three images, network access to pull the client images, and the contracts submodule checked out locally.
ROLLUP OPERATORS

How to run the whole stack locally

The whole stack runs on a Linux host with Docker and the Kurtosis engine running — all local tooling, plus the real contract source pulled in via submodule.

One script deploys the contracts, generates the L2 genesis, and boots the L1, MEV-builder, node and proof-signer together in a disposable network.

WHAT YOU'LL LEARN
  • 01 · PREREQS + SUBMODULEA Linux host with Docker, all local tooling, plus the real contract source pulled in via submodule.
  • 02 · START THE ENGINEKURTOSIS_ENCLAVE names the disposable network; KURTOSIS_ARGS_FILE points at the real ci-args.yaml, which carries deterministic private-network keys.
  • 03 · ONE SCRIPT → FULL STACKOne script deploys contracts, generates the L2 genesis, and boots every service together — several minutes on the first run.

Verified against eez-rollup0 @ a4b9b2f — pre-mainnet; interfaces may move.