Quickstarts
Run the EEZ Devnet with Kurtosis
STEP 1 OF 3
NEXT WALKTHROUGH: How to deploy the protocol →
PREREQS + SUBMODULE
Linux host
Docker
Kurtosis CLI
Foundry v1.7.1
Bash
Git
GNU timeout
jq
curl
openssl
eez-rollup-ui checkout (or EEZ_UI_REPO)
$ 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 four images, network access to pull the client images, the contracts submodule checked out locally, and the standalone eez-rollup-ui repo cloned beside this one (or a prebuilt UI image).
PINNED
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 and the standalone UI repo beside it.
One script deploys the contracts, generates the L2 genesis, and boots the L1, MEV-builder, node, proof-signer and protocol playground together in a disposable network; ports.sh then prints every endpoint.
WHAT YOU'LL LEARN
- 01 · PREREQS + SUBMODULEA Linux host with Docker, all local tooling, plus the real contract source pulled in via submodule and the eez-rollup-ui repo.
- 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. ports.sh exports the RPC, front and playground URLs.
Verified against eez-rollupX Git commit 2c19e36; interfaces may move.