diff --git a/content/10.zk-stack/20.running-a-hyperchain/10.locally.md b/content/10.zk-stack/20.running-a-hyperchain/10.locally.md
new file mode 100644
index 00000000..c8f9c1ae
--- /dev/null
+++ b/content/10.zk-stack/20.running-a-hyperchain/10.locally.md
@@ -0,0 +1,246 @@
+---
+title: Locally
+description:
+---
+
+## Getting Started with ZK Stack
+
+::callout{icon="i-heroicons-exclamation-triangle" color="amber"}
+ZK Stack is still under development. We advise you to only use for local and testnet deployments.
+::
+
+## Development dependencies
+
+Ensure you have followed [these instructions](https://github.com/matter-labs/zksync-era/blob/main/docs/guides/setup-dev.md)
+to set up dependencies on your machine (don't worry about the Environment section for now).
+
+## Deploying locally
+
+1. Clone the zksync-era repo (or pull the latest if you've already cloned it) and go to the root of it:
+
+    ```bash
+    git clone https://github.com/matter-labs/zksync-era
+    ```
+
+1. Add `ZKSYNC_HOME` to your path (e.g. `~/.bash_profile`, `~/.zshrc` ) - don't forget to source your profile file again (or restart your terminal):
+
+    ```bash
+    export ZKSYNC_HOME=/path/to/zksync/repo/you/cloned
+    export PATH=$ZKSYNC_HOME/bin:$PATH
+    ```
+
+1. Build latest version of zk tools by just running `zk` on the root of the project.
+
+    ```bash
+    zk
+    ```
+
+1. Last, start the wizard and follow instructions to set up and deploy your new hyperchain by running `zk stack init`
+
+    - Initially you want to `Configure new chain`
+
+    - Give it a name and chain id.
+
+    - Select localhost (default `matterlabs/geth`) and follow the wizard.
+
+        - If you are doing this for the first time, several components need to be compiled/built, so do not worry if it takes a few minutes.
+        The console will show what is going on anyways.
+
+    - If you don't want to configure any values for now and just want check the build process for a hyperchain, try out the `zk stack demo` command.
+
+::callout{icon="i-heroicons-exclamation-triangle" color="amber"}
+The commands above are not just running docker containers, but are actually building the code from the repo to spin up your hyperchain.
+For this reason the process might take some time.
+If you just want to run docker containers to play around with a zkSync chain, you can use `zksync-cli dev`.
+Learn more [here](/build/tooling/zksync-cli).
+::
+
+### Your hyperchain is now deployed
+
+Your hyperchain is now deployed to the base chain (most likely a local geth docker container) and configured.
+You can find all configuration in a new `.env` file created on `<project root>/etc/env/<your_chain_name_slug>.env`,
+and if you deployed test tokens, their addresses will be available at `<project root>/etc/tokens/<the_l1_identifier>.json`
+
+1. The wizard allows you to run the server in the end. If you chose not to, you’re still able to run it by executing
+
+    ```bash
+    zk server --components "http_api,eth,state_keeper,housekeeper"
+    ```
+
+1. You can now run transactions and start playing with your hyperchain by using the RPC available at <http://localhost:3050>.
+
+   - Don't forget to deposit some ETH and fund your accounts on your hyperchain. To do so follow the instructions for [Funding accounts](#funding-accounts).
+
+## Using your hyperchain
+
+### Funding accounts
+
+During the `zk stack init` configurator, you have a choice of what base layer to deploy the hyperchain onto:
+the local geth node, or an Ethereum network (e.g., Sepolia).
+The first step to start interacting with your hyperchain is to fund an account (or a few).
+This means you need some funds on the base layer.
+
+#### Base layer is the local geth node
+[@matterlabs/geth:latest](https://hub.docker.com/r/matterlabs/geth)
+
+- If you chose to deploy on local geth node, you will have a set of addresses that have 100 ETH each.
+  You can find the list [here](https://github.com/matter-labs/local-setup/blob/main/rich-wallets.json)
+  and use these addresses to deposit into your hyperchain via the bridge.
+
+#### Base layer is an Ethereum network (e.g., Sepolia)
+
+- If you chose to deploy on an Ethereum network (e.g., Sepolia), you need to have an account on the base layer with ETH.
+  You can use the deployer, governor, or operator wallets setup during the the deployment process,
+  or any other one you have funds, to deposit into your hyperchain via the bridge.
+
+Once you have the accounts with funds on the L1 base layer, you can do a deposit via the bridge to your hyperchain,
+and any further interactions with your hyperchain.
+
+### Using your hyperchain RPC
+
+Your server contains both HTTPS as well as WebSocket (WS) services that are fully web3 compatible (and contain some extra ZK Stack functionalities).
+Learn more about it [here](/build/api-reference).
+
+### Using zksync-cli
+
+zkSync CLI allows you to easily interact and develop applications on your hyperchain.
+When executing any command with zksync-cli, you can specify RPC urls for both L1 and L2.
+Your local server contains RPCs for both.
+An example deposit command via the bridge would look like:
+
+```bash
+npx zksync-cli bridge deposit --rpc=http://localhost:3050 --l1-rpc=http://localhost:8545
+```
+
+### Using Portal
+
+The dApp Portal module allows you to:
+
+- View balances, transfer and bridge tokens to your hyperchain.
+- Add contacts for quick and easy access.
+
+You can run the Portal module locally, and point it to your hyperchain configuration.
+It comes with scripts that help pulling the hyperchain configuration from your zksync-era repo and adapting to portal needs.
+Learn more [here](https://github.com/matter-labs/dapp-portal).
+An example command would look like:
+
+```bash
+npm run hyperchain:configure ../zksync-era
+npm run dev:node:hyperchain
+```
+
+You can now navigate to the displayed Portal URL (typically <http://localhost:3000>).
+
+### Using Block Explorer
+
+A free open source block explorer is available for your hyperchain.
+Block explorer contains three components [Worker](https://github.com/matter-labs/block-explorer/tree/main/packages/worker),
+[API](https://github.com/matter-labs/block-explorer/tree/main/packages/api),
+and [App](https://github.com/matter-labs/block-explorer/tree/main/packages/app),
+which you can run all together locally and connect to your hyperchain.
+
+Make sure you have your [zksync-era](https://github.com/matter-labs/zksync-era) repo set up locally and the `zk server` is running.
+The wizard in this guide allows you to run the server in the end.
+If you chose not to, you’re still able to run it by executing:
+
+```bash
+zk server --components "http_api,eth,state_keeper,housekeeper"
+```
+
+### Running block explorer locally
+
+#### Install block explorer
+
+Clone & install the block explorer repository:
+
+```bash
+cd /path/to/where/you/clone/repos
+git clone https://github.com/matter-labs/block-explorer.git
+cd block-explorer
+npm install
+```
+
+#### Setting up env variables
+
+Next you need to set up all the necessary environment and configuration files with your hyperchain settings. You can use a script to set them up:
+
+```bash
+npm run hyperchain:configure
+```
+
+#### Run block explorer
+
+Afterwards you can run the block explorer:
+
+```bash
+# if you are running block explorer for the first time
+npm run db:create
+```
+
+```bash
+npm run dev
+```
+
+#### Verify block explorer is up and running
+
+By default, you can access front-end `App` at <http://localhost:3010> in your browser.
+`API` should be available at <http://localhost:3020>, `Worker` at <http://localhost:3001> and `Data Fetcher` at <http://localhost:3040>.
+
+## Enabling Boojum prover
+
+With the default configuration, your hyperchain is not running a prover,
+and has a DummyExecutor contract, which mainly “accepts” that a batch is executed without proof.
+This enables you to test it with much lower hardware requirements.
+
+To enable the prover, run the `zk stack prover-setup` command. It will guide through the necessary configuration.
+
+There are two options for running the Boojum prover: in GPU, or in CPU.
+
+::callout{icon="i-heroicons-exclamation-triangle" color="amber"}
+**Running a prover is not required** for deploying a testnet. The requirements below are only necessary if you want to enable the prover.
+::
+
+### Requirements for GPU Prover
+
+The docker compose file assumes you will be running all components in the same machine. The current minimum requirements for a low TPS scenario are:
+
+- 6 GB VRAM NVIDIA GPU
+- 16 Core CPU
+- 64 GB of RAM
+- 300 GB of Disk Space (SSD preferred)
+
+### Requirements for CPU Prover
+
+The docker compose file assumes you will be running all components in the same machine.
+The current minimum requirements for a low TPS scenario are:
+
+- 32 Core CPU
+- 128 GB of RAM
+- 700 of Disk Space (SSD preferred)
+
+## Addendum
+
+- If you make changes to any contract, you can always deploy a new hyperchain to easily test those changes.
+- If you configure your hyperchain once, you don't need to do it again as the wizard allows you to use an existing config file.
+- For now, it is only possible to deploy a hyperchain as an L2, but soon it will also work as L3s.
+- When running the default matterlabs/geth, you have a set of rich wallets available to you.
+    ::drop-panel
+    ::panel{label="Rich Wallets"}
+      :display-partial{path="/_partials/_rich-wallets"}
+    ::
+    ::
+- If you face an issue compiling rust code (example `<jemalloc>: Error allocating TSD`) try removing the `rust-toolchain` file from the repo.
+- If you want to have a custom local base chain, you must ensure you have a database for your hyperchain, as well as the local RPC for your L1.
+  - To run a Postgres 14 database for your hyperchain, execute the following:
+
+    ```bash
+    docker-compose -f docker-compose-zkstack-common.yml up -d postgres
+    ```
+
+In case you don't want to use the docker Postgres database above but another one you already have locally,
+make sure its version is 14 and it is running and accepts connections at `postgres://postgres@localhost/zksync_local`.
+You can test with:
+
+```bash
+psql -h localhost -U postgres -d postgres -c 'SELECT 1;'
+```
diff --git a/content/10.zk-stack/20.running-a-hyperchain/20.production.md b/content/10.zk-stack/20.running-a-hyperchain/20.production.md
new file mode 100644
index 00000000..e120f12f
--- /dev/null
+++ b/content/10.zk-stack/20.running-a-hyperchain/20.production.md
@@ -0,0 +1,25 @@
+---
+title: In Production
+---
+
+::callout{icon="i-heroicons-exclamation-triangle" color="amber"}
+ZK Stack is still under development. We advise you to only use for local and testnet deployments.
+::
+
+## Deploying to a non-local environment
+
+The process to deploy to a non local environment is pretty similar to the local one.
+The wizard allows you to set up URLs to external services (database, RPCs, etc).
+
+## Database
+
+The wizard allows you to provide a custom database url connector.
+Make sure you provide it and that it accepts external connections if your server is not running in the same private network.
+
+## Server (Sequencer) & Prover
+
+After configuring your hyperchain, you can generate docker images for your server and prover.
+To do that run `zk stack docker-setup`.
+
+This command will guide you to properly name and tag your image.
+After building it, a docker compose file will be available so you can run the images on whichever cloud environment you desire.
diff --git a/content/10.zk-stack/20.running-a-hyperchain/30.raas.md b/content/10.zk-stack/20.running-a-hyperchain/30.raas.md
new file mode 100644
index 00000000..26b4a3c1
--- /dev/null
+++ b/content/10.zk-stack/20.running-a-hyperchain/30.raas.md
@@ -0,0 +1,30 @@
+---
+title: Rollup as a Service
+description:
+---
+
+::callout{icon="i-heroicons-exclamation-triangle" color="amber"}
+ZK Stack is still under development. We advise you to only use for local and testnet deployments.
+::
+
+## Deploying and running using a Rollup as a Service provider
+
+Looking to deploy a ZK Stack chain but worried about complexities?
+RaaS providers are here to simplify the process!
+Providers offer scalable and secure nodes, and may provide quick and user-friendly interfaces,
+allowing you to deploy your ZK Stack chain with ease and efficiency.
+Experience the seamless integration of advanced blockchain technology without the hassle.
+Get started today and revolutionize your product with the power of RaaS and ZK Stack!
+
+Use RaaS in to improve scalability, reduce costs, access specialized services, speed up development, enhance interoperability,
+and maintain flexibility in an ever-evolving technological landscape.
+
+The list of RaaS providers you can use to deploy and customise their your hyperchain:
+
+<!-- * [Caldera](https://www.caldera.xyz/) -->
+
+- [Zeeve](https://www.zeeve.io/appchains/zksync-hyperchains-zkrollups/)
+- [Ankr](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/ankrpbc1684783099666.ankr_appchains?tab=Overview/)
+- [AltLayer](https://altlayer.io/raas)
+- [Magic](https://magic.link/docs/blockchains/other-chains/evm/zksync)
+- [Luganodes](https://www.luganodes.com/product/zkraas/)
diff --git a/content/10.zk-stack/20.running-a-hyperchain/99.dependencies.md b/content/10.zk-stack/20.running-a-hyperchain/99.dependencies.md
new file mode 100644
index 00000000..7bdb5197
--- /dev/null
+++ b/content/10.zk-stack/20.running-a-hyperchain/99.dependencies.md
@@ -0,0 +1,289 @@
+---
+title: Dependencies
+---
+
+## TL;DR
+
+If you run on 'clean' Debian on GCP:
+
+```bash
+# Rust
+curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
+# NVM
+curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.5/install.sh | bash
+# All necessary stuff
+sudo apt-get install build-essential pkg-config cmake clang lldb lld libssl-dev postgresql docker-compose
+# Docker
+sudo usermod -aG docker YOUR_USER
+
+## You might need to re-connect (due to usermod change).
+
+# Node & yarn
+nvm install node
+npm install -g yarn
+yarn set version 1.22.19
+
+# SQL tools
+cargo install sqlx-cli --version 0.5.13
+# Stop default postgres (as we'll use the docker one)
+sudo systemctl stop postgresql
+# Start docker.
+sudo systemctl start docker
+```
+
+## Supported operating systems
+
+zkSync currently can be launched on any \*nix operating system (e.g. any linux distribution or MacOS).
+
+If you're using Windows, then make sure to use WSL 2, since WSL 1 is known to cause troubles.
+
+Additionally, if you are going to use WSL 2, make sure that your project is located in the _linux filesystem_, since
+accessing NTFS partitions from inside of WSL is very slow.
+
+If you're using MacOS with an ARM processor (e.g. M1/M2), make sure that you are working in the _native_ environment
+(e.g. your terminal and IDE don't run in Rosetta, and your toolchain is native). Trying to work with zkSync code via
+Rosetta may cause problems that are hard to spot and debug, so make sure to check everything before you start.
+
+If you are a NixOS user or would like to have a reproducible environment, skip to the section about `nix`.
+
+## `Docker`
+
+Install `docker`. It is recommended to follow the instructions from the
+[official site](https://docs.docker.com/install/).
+
+Note: currently official site proposes using Docker Desktop for Linux, which is a GUI tool with plenty of quirks. If you
+want to only have CLI tool, you need the `docker-ce` package and you can follow
+[this guide](https://www.digitalocean.com/community/tutorials/how-to-install-and-use-docker-on-ubuntu-20-04) for Ubuntu.
+
+Installing `docker` via `snap` or from the default repository can cause troubles.
+
+You need to install both `docker` and `docker-compose`.
+
+**Note:** `docker-compose` is installed automatically with `Docker Desktop`.
+
+**Note:** On linux you may encounter the following error when you’ll try to work with `zksync`:
+
+```sh
+ERROR: Couldn't connect to Docker daemon - you might need to run `docker-machine start default`.
+```
+
+If so, you **do not need** to install `docker-machine`. Most probably, it means that your user is not added to
+the`docker` group. You can check it as follows:
+
+```bash
+docker-compose up # Should raise the same error.
+sudo docker-compose up # Should start doing things.
+```
+
+If the first command fails, but the second succeeds, then you need to add your user to the `docker` group:
+
+```bash
+sudo usermod -a -G docker your_user_name
+```
+
+After that, you should logout and login again (user groups are refreshed after the login). The problem should be solved
+at this step.
+
+If logging out does not help, restarting the computer should.
+
+## `Node` & `Yarn`
+
+1. Install `Node` (requires version `v18.18.0`). Since our team attempts to always use the latest LTS version of
+   `Node.js`, we suggest you to install [nvm](https://github.com/nvm-sh/nvm). It will allow you to update `Node.js`
+   version easily in the future (by running `nvm use` in the root of the repository)
+2. Install `yarn` (make sure to get version 1.22.19 - you can change the version by running `yarn set version 1.22.19`).
+   Instructions can be found on the [official site](https://classic.yarnpkg.com/en/docs/install/).
+   Check if `yarn` is installed by running `yarn -v`. If you face any problems when installing `yarn`, it might be the
+   case that your package manager installed the wrong package.Make sure to thoroughly follow the instructions above on
+   the official website. It contains a lot of troubleshooting guides in it.
+
+## `Axel`
+
+Install `axel` for downloading keys:
+
+On mac:
+
+```bash
+brew install axel
+```
+
+On debian-based linux:
+
+```bash
+sudo apt-get install axel
+```
+
+Check the version of `axel` with the following command:
+
+```sh
+axel --version
+```
+
+Make sure the version is higher than `2.17.10`.
+
+## `clang`
+
+In order to compile RocksDB, you must have LLVM available. On debian-based linux it can be installed as follows:
+
+On linux:
+
+```bash
+sudo apt-get install build-essential pkg-config cmake clang lldb lld
+```
+
+On mac:
+
+You need to have an up-to-date `Xcode`. You can install it directly from `App Store`. With Xcode command line tools, you
+get the Clang compiler installed by default. Thus, having XCode you don't need to install `clang`.
+
+## `OpenSSL`
+
+Install OpenSSL:
+
+On mac:
+
+```bash
+brew install openssl
+```
+
+On linux:
+
+```bash
+sudo apt-get install libssl-dev
+```
+
+## `Rust`
+
+Install the latest `rust` version.
+
+Instructions can be found on the [official site](https://www.rust-lang.org/tools/install).
+
+Verify the `rust` installation:
+
+```bash
+rustc --version
+rustc 1.xx.y (xxxxxx 20xx-yy-zz) # Output may vary depending on actual version of rust
+```
+
+If you are using MacOS with ARM processor (e.g. M1/M2), make sure that you use an `aarch64` toolchain. For example, when
+you run `rustup show`, you should see a similar input:
+
+```bash
+rustup show
+Default host: aarch64-apple-darwin
+rustup home:  /Users/user/.rustup
+
+installed toolchains
+--------------------
+
+...
+
+active toolchain
+----------------
+
+1.67.1-aarch64-apple-darwin (overridden by '/Users/user/workspace/zksync-era/rust-toolchain')
+```
+
+If you see `x86_64` mentioned in the output, probably you're running (or used to run) your IDE/terminal in Rosetta. If
+that's the case, you should probably change the way you run terminal, and/or reinstall your IDE, and then reinstall the
+Rust toolchain as well.
+
+## Postgres
+
+Install the latest postgres:
+
+On mac:
+
+```bash
+brew install postgresql@14
+```
+
+On linux:
+
+```bash
+sudo apt-get install postgresql
+```
+
+### Cargo nextest
+
+[cargo-nextest](https://nexte.st/) is the next-generation test runner for Rust projects. `zk test rust` uses
+`cargo nextest` by default.
+
+```bash
+cargo install cargo-nextest
+```
+
+### SQLx CLI
+
+SQLx is a Rust library we use to interact with Postgres, and its CLI is used to manage DB migrations and support several
+features of the library.
+
+```bash
+cargo install sqlx-cli --version 0.5.13
+```
+
+## Solidity compiler `solc`
+
+Install the latest solidity compiler.
+
+```bash
+brew install solidity
+```
+
+Alternatively, download a [precompiled version](https://github.com/ethereum/solc-bin) and add it to your PATH.
+
+## Python
+
+Most environments will have this preinstalled but if not, install Python.
+
+## Easier method using `nix`
+
+Nix is a tool that can fetch _exactly_ the right dependencies specified via hashes. The current config is Linux-only but
+it is likely that it can be adapted to Mac.
+
+Install `nix`. Enable the nix command and flakes.
+
+Install docker, rustup and use rust to install SQLx CLI like described above. If you are on NixOS, you also need to
+enable nix-ld.
+
+Go to the zksync folder and run `nix develop --impure`. After it finishes, you are in a shell that has all the
+dependencies.
+
+## Environment
+
+Edit the lines below and add them to your shell profile file (e.g. `~/.bash_profile`, `~/.zshrc`):
+
+```bash
+# Add path here:
+export ZKSYNC_HOME=/path/to/zksync
+
+export PATH=$ZKSYNC_HOME/bin:$PATH
+
+# If you're like me, uncomment:
+# cd $ZKSYNC_HOME
+```
+
+### Tip: `mold`
+
+Optionally, you may want to optimize the build time with the modern linker, [`mold`](https://github.com/rui314/mold).
+
+This linker will speed up the build times, which can be pretty big for Rust binaries.
+
+Follow the instructions in the repo in order to install it and enable for Rust.
+
+## Tip: Speeding up building `RocksDB`
+
+By default, each time you compile `rocksdb` crate, it will compile required C++ sources from scratch. It can be avoided
+by using precompiled versions of library, and it will significantly improve your build times.
+
+In order to do so, you can put compiled libraries to some persistent location, and add the following to your shell
+configuration file (e.g. `.zshrc` or `.bashrc`):
+
+```sh
+export ROCKSDB_LIB_DIR=<library location>
+export SNAPPY_LIB_DIR=<library location>
+```
+
+Make sure that compiled libraries match the current version of RocksDB. One way to obtain them, is to compile the
+project in the usual way once, and then take built libraries from
+`target/{debug,release}/build/librocksdb-sys-{some random value}/out`.
diff --git a/content/10.zk-stack/20.running-a-hyperchain/99.enabling-prover.md b/content/10.zk-stack/20.running-a-hyperchain/99.enabling-prover.md
new file mode 100644
index 00000000..0b7a195f
--- /dev/null
+++ b/content/10.zk-stack/20.running-a-hyperchain/99.enabling-prover.md
@@ -0,0 +1,30 @@
+---
+title: Enabling Prover
+description:
+---
+
+With the default configuration, your hyperchain is not running a prover,
+and has a `DummyExecutor` contract, which mainly “accepts” that a batch is executed without proof.
+This enables you to test it with much lower hardware requirements.
+
+To enable the prover, run the `zk stack prover-setup` command.
+It will guide through the necessary configuration.
+
+> :warning: Running a prover is not required for deploying a testnet. The requirements below are only necessary if you want to enable the prover.
+
+## Requirements for CPU Prover
+
+The docker compose file assumes you will be running all components in the same machine. The current minimum requirements for a low TPS scenario are:
+
+- 32 Core CPU
+- 128 GB of RAM
+- 700 of Disk Space (SSD preferred)
+
+## Requirements for GPU Prover
+
+The docker compose file assumes you will be running all components in the same machine. The current minimum requirements for a low TPS scenario are:
+
+- 16 GB VRAM NVIDIA GPU
+- 16 Core CPU
+- 64 GB of RAM
+- 300 GB of Disk Space (SSD preferred)
diff --git a/content/10.zk-stack/20.running-a-hyperchain/99.using-hyperchain.md b/content/10.zk-stack/20.running-a-hyperchain/99.using-hyperchain.md
new file mode 100644
index 00000000..8a7e71eb
--- /dev/null
+++ b/content/10.zk-stack/20.running-a-hyperchain/99.using-hyperchain.md
@@ -0,0 +1,77 @@
+---
+title: Using Your Hyperchain RPC
+description:
+---
+
+Your server contains both HTTPS as well as WS services that are fully web3 compatible (and contain some extra ZK Stack functionalities).
+
+By default your server is available at <http://localhost:3050> - but if you deployed the server into some cloud provider,
+you will have a different URL to interact with.
+
+## Using zksync-cli
+
+When executing any command with zksync-cli,
+you can specify RPC urls for both L1 and L2 if you choose “localnet” as your network.
+An example deposit command would look like:
+
+```bash
+npx zksync-cli bridge deposit --rpc=http://localhost:3050 --l1-rpc=http://localhost:8545
+```
+
+## Using dApp Portal
+
+You can run the Portal module locally, and point it to your hyperchain configuration.
+It comes with scripts that help pulling the hyperchain configuration from your zksync-era repo and adapting to portal needs.
+Learn more here. An example command would look like:
+
+```bash
+npm run hyperchain:migrate ../zksync-era
+npm run dev:node:hyperchain
+```
+
+## Using Block Explorer
+
+Block explorer contains three components (Worker, API, and App), which you can run all together locally and connect to your hyperchain.
+For that, you need to set up all the necessary environment and configuration files with your hyperchain settings.
+You can use a script to build them. See setting up env variables.
+
+Once you have your zksync-era repo set up locally, you can run the following command to
+build environment and configuration files for block explorer based on your **[zksync-era](https://github.com/matter-labs/zksync-era)** repo configuration:
+
+```bash
+npm run hyperchain:configure
+```
+
+The script generates all the necessary configuration files for block-explorer, which you can edit if you need any changes.
+
+## Addendum
+
+- If you make changes to any contract, you can always deploy a new hyperchain to easily test those changes.
+
+- If you configure your hyperchain once, you don't need to do it again as the wizard allows you to use an existing config file.
+
+- For now, it is only possible to deploy a hyperchain as an L2, but soon it will also work as L3s.
+
+- When running the default matterlabs/geth, you have a set of rich wallets available to you.
+    ::drop-panel
+    ::panel{label="Rich Wallets"}
+      :display-partial{path="/_partials/_rich-wallets"}
+    ::
+    ::
+- If you want to have a custom local base chain, you must ensure you have a database for your hyperchain, as well as the local RPC for your L1.
+
+- To run a Postgres 14 database for your hyperchain, execute the following:
+
+```bash
+docker-compose -f docker-compose-zkstack-common.yml up -d postgres
+```
+
+In case you don't want to use the docker Postgres database above but another one you already have locally,
+make sure its version is 14 and it is running and accepts connections at postgres://postgres@localhost/zksync_local.
+You can test with:
+
+```bash
+psql -h localhost -U postgres -d postgres -c 'SELECT 1;'
+```
+
+If you face an issue compiling rust code (example `<jemalloc>: Error allocating TSD`) try removing the `rust-toolchain` file from the repo.
diff --git a/cspell-config/cspell-blockchain.txt b/cspell-config/cspell-blockchain.txt
index 5d567977..52d59646 100644
--- a/cspell-config/cspell-blockchain.txt
+++ b/cspell-config/cspell-blockchain.txt
@@ -5,7 +5,7 @@ Eigen
 ethereum
 EVM
 evmla
-Geth
+geth
 gwei
 IERC
 inversed
@@ -32,3 +32,4 @@ Vitalik
 vyper
 Weth
 Yul
+Zeeve
diff --git a/cspell-config/cspell-dev.txt b/cspell-config/cspell-dev.txt
index 72bae563..0dc84883 100644
--- a/cspell-config/cspell-dev.txt
+++ b/cspell-config/cspell-dev.txt
@@ -1,9 +1,11 @@
+Ankr
 binop
 blake2s
 blake2s256
 cccond
 ccret
 CHAINID
+debian
 decommit
 decommits
 decommitter
@@ -24,8 +26,10 @@ fontaine
 .interm
 inttoptr
 iszero
+jemalloc
 JUMPI
 legendre
+librocksdb
 mload
 MontInvbEEA
 montgomery
@@ -45,24 +49,29 @@ nuxtjs
 NVMe
 plux
 postgres
+postgresql
 preds
 prode
 prodeh
 prodh
 prodm
 prodl
+psql
 ptrtoint
 recid.
 REDC
+rocksdb
 rodata
+rustc
 rustup
-rocksdb
 secp
 signv
 sload
 smod
 sstore
+sqlx-cli
 syncvm
+tlsv1
 .uadd.
 .umin.
 Vue
diff --git a/cspell-config/cspell-zksync.txt b/cspell-config/cspell-zksync.txt
index 53fcf0c7..1cee5f54 100644
--- a/cspell-config/cspell-zksync.txt
+++ b/cspell-config/cspell-zksync.txt
@@ -8,6 +8,7 @@ zkevm
 zkforge
 zkout
 zksolc
+zkstack
 zkSync
 zksync
 zksync-cli
diff --git a/cspell.json b/cspell.json
index f68c98e7..0977f9c9 100644
--- a/cspell.json
+++ b/cspell.json
@@ -1,6 +1,9 @@
 {
   "language": "en",
   "ignorePaths": [
+    "bun.lockb",
+    "*.css",
+    "*.config.*",
     "node_modules/**",
     ".github/**",
     ".firebase/**",
@@ -18,14 +21,17 @@
     "cryptocurrencies",
     "docker",
     "css",
+    "csharp",
     "en_GB",
     "en_US",
     "filetypes",
     "fullstack",
     "git",
     "golang",
+    "go",
     "html",
     "java",
+    "latext",
     "misc",
     "node",
     "npm",