…bs#2901)

## What ❔

Remove use of ZK tool in docker-build process

## Why ❔

Improve readability of CI, speeds up building process

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zk fmt` and `zk lint`.

## What ❔

- Resolves "nonce too low" errors on L1 by retrying transaction
requests. This is a temporary measure until a new version of `reth` is
released.
- Reduces spammy logs for integration tests. Enables verbose output for
integration tests in CI.
- Fixes some other issues with tests (e.g., a data race in the snapshot
recovery test).

## Why ❔

Makes CI more stable.

## Checklist

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [x] Tests for the changes have been added / updated.
- [x] Code has been formatted via `zk fmt` and `zk lint`.

## What ❔

<!-- What are the changes this PR brings about? -->
<!-- Example: This PR adds a PR template to the repo. -->
<!-- (For bigger PRs adding more context is appreciated) -->

## Why ❔

<!-- Why are these changes done? What goal do they contribute to? What
are the principles behind them? -->
<!-- Example: PR templates ensure PR reviewers, observers, and future
iterators are in context about the evolution of repos. -->

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [ ] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zk fmt` and `zk lint`.

Signed-off-by: Danil <deniallugo@gmail.com>

## What ❔

Workflow to build base-image

## Why ❔

Added ability to push to ghcr.io

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zk fmt` and `zk lint`.

## What ❔

Fix multiarch command for build-base-image CI

## Why ❔


## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zk fmt` and `zk lint`.

## What ❔

Change build-base image location from dockerhub to ghcr.io

## Why ❔

Workaround for dockerhub rate-limiting 

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zk fmt` and `zk lint`.

## What ❔

This PR is the first part of [this
one](matter-labs#2631).

We decided to separate it into smaller PRs to make it easier to read and
review.

This PR contains only the changes to the `TransactionData` structs for
the different VM versions, modifying them for an optional field.

The other parts are currently available in our repo fork, as they are
based on this branch. The other PRs are:
- [feat: evm simulator as base system
contract](#256):
integrates the EVM interpreter contract as a base system contract and
includes all necessary updates for zksync-era to run with it.
- [feat: make evm simulator optional for the
server](#257): makes the
evm simulator optional to run using a config file.

## Why ❔

<!-- Why are these changes done? What goal do they contribute to? What
are the principles behind them? -->
<!-- Example: PR templates ensure PR reviewers, observers, and future
iterators are in context about the evolution of repos. -->

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [ ] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zk fmt` and `zk lint`.

## What ❔

Introduce WitnessGenerator trait
Rename some methods

## Why ❔

<!-- Why are these changes done? What goal do they contribute to? What
are the principles behind them? -->
<!-- Example: PR templates ensure PR reviewers, observers, and future
iterators are in context about the evolution of repos. -->

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [ ] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zk fmt` and `zk lint`.

## What ❔

Following Anton's suggestion, we have switched to hex serialization for
API/RPC requests and responses. Previously, we used default JSON
serialization for Vec<u8>, which resulted in a lengthy comma-separated
list of integers.

This change standardizes serialization, making it more efficient and
reducing the size of the responses. The previous format, with a series
of comma-separated integers for pubkey-like fields, looked odd.

Then:
```
curl -X POST\
     -H "Content-Type: application/json" \
     --data '{"jsonrpc": "2.0", "id": 1, "method": "unstable_getTeeProofs", "params": [491882, "sgx"] }' \
        https://mainnet.era.zksync.io
{"jsonrpc":"2.0","result":[{"attestation":[3,0,2,0,0,0,0,0,10,<dozens of comma-separated integers here>
```

Now:
```
$ curl -X POST \
       -H "Content-Type: application/json" \
       --data '{"jsonrpc": "2.0", "id": 1, "method": "unstable_getTeeProofs", "params": [1, "sgx"] }' \
          http://localhost:3050
{"jsonrpc":"2.0","result":[{"l1BatchNumber":1,"teeType":"sgx","pubkey":"0506070809","signature":"0001020304","proof":"0a0b0c0d0e","provedAt":"2024-09-16T11:53:38.253033Z","attestation":"0403020100"}],"id":1}
```

This change needs to be deployed in lockstep with:
matter-labs/teepot#209.

## Why ❔

To improve user experience (UX) and optimize the RPC response size.

## Checklist

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [x] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [x] Code has been formatted via `zk fmt` and `zk lint`.

Co-authored-by: Artem Makhortov <13339874+artmakh@users.noreply.github.com>

## What ❔

Adding image which will be used as runtime-base for services

## Why ❔

As a workaround for dockerhub ratelimits

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zk fmt` and `zk lint`.

## What ❔

Rename workflows for runner and builder base

## Why ❔

Easier to find =)

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zk fmt` and `zk lint`.

## What ❔

Proper platform names for docker build action

## Why ❔

Docker documentation (which is linked in docker-build-action docs)
[points to non-working
reference](https://docs.docker.com/reference/cli/docker/buildx/build/#platform)

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zk fmt` and `zk lint`.

…ter-labs#2924)

## What ❔

Proper type of var for platforms in docker build action

## Why ❔

<!-- Why are these changes done? What goal do they contribute to? What
are the principles behind them? -->
<!-- Example: PR templates ensure PR reviewers, observers, and future
iterators are in context about the evolution of repos. -->

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zk fmt` and `zk lint`.

## What ❔

<!-- What are the changes this PR brings about? -->
<!-- Example: This PR adds a PR template to the repo. -->
<!-- (For bigger PRs adding more context is appreciated) -->

## Why ❔

<!-- Why are these changes done? What goal do they contribute to? What
are the principles behind them? -->
<!-- Example: PR templates ensure PR reviewers, observers, and future
iterators are in context about the evolution of repos. -->

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [ ] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zk fmt` and `zk lint`.

---------

Signed-off-by: Danil <deniallugo@gmail.com>

…labs#2926)

## What ❔

Move building images to zksync-runtime-base

## Why ❔

Workaround for dockerhub rate limits

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zk fmt` and `zk lint`.

🤖 I have created a release *beep* *boop*
---


##
[24.25.0](matter-labs/zksync-era@core-v24.24.0...core-v24.25.0)
(2024-09-19)


### Features

* (DB migration) Rename recursion_scheduler_level_vk_hash to
snark_wrapper_vk_hash
([matter-labs#2809](matter-labs#2809))
([64f9551](matter-labs@64f9551))
* add da clients
([matter-labs#2743](matter-labs#2743))
([9218612](matter-labs@9218612))
* attester committees data extractor (BFT-434)
([matter-labs#2684](matter-labs#2684))
([92dde03](matter-labs@92dde03))
* emit errors in prover API metrics
([matter-labs#2890](matter-labs#2890))
([2ac7cc5](matter-labs@2ac7cc5))
* **en:** Resume incomplete snapshot in snapshot creator in more cases
([matter-labs#2886](matter-labs#2886))
([f095b4a](matter-labs@f095b4a))
* make `to` address optional for transaction data
([matter-labs#2852](matter-labs#2852))
([8363c1d](matter-labs@8363c1d))
* **prover:** Optimize setup keys loading
([matter-labs#2847](matter-labs#2847))
([19887ef](matter-labs@19887ef))
* Selector generator tool
([matter-labs#2844](matter-labs#2844))
([b359b08](matter-labs@b359b08))
* **tee:** use hex serialization for RPC responses
([matter-labs#2887](matter-labs#2887))
([abe0440](matter-labs@abe0440))
* **utils:** Rework locate_workspace, introduce Workspace type
([matter-labs#2830](matter-labs#2830))
([d256092](matter-labs@d256092))
* **zk_toolbox:** Add external_node consensus support
([matter-labs#2821](matter-labs#2821))
([4a10d7d](matter-labs@4a10d7d))


### Bug Fixes

* count SECP256 precompile to account validation gas limit as well
([matter-labs#2859](matter-labs#2859))
([fee0c2a](matter-labs@fee0c2a))
* **en:** Fix connection starvation during snapshot recovery
([matter-labs#2836](matter-labs#2836))
([52f4f76](matter-labs@52f4f76))
* **eth_watch:** fix `get_events_inner`
([matter-labs#2882](matter-labs#2882))
([c957dd8](matter-labs@c957dd8))
* handling of HTTP 403 thrown by proxyd
([matter-labs#2835](matter-labs#2835))
([2d71c74](matter-labs@2d71c74))
* **state-keeper:** Restore processed tx metrics in state keeper
([matter-labs#2815](matter-labs#2815))
([4d8862b](matter-labs@4d8862b))
* **tee-prover:** fix deserialization of `std::time::Duration` in `envy`
config ([matter-labs#2817](matter-labs#2817))
([df8641a](matter-labs@df8641a))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

---------

Co-authored-by: zksync-era-bot <zksync-era-bot@users.noreply.github.com>

## What ❔
- 30 GB of free disk space are no longer sufficient to run a testnet EN.
Upped the system requirements to 50 GB.
- State growth is normally used to refer to the growth of the state
tree, not of the historical state. What we have is historical state
pruning, not state pruning.

## What ❔

Bumps the `vm2` crate revision and updates new VM usage correspondingly.

## Why ❔

To keep the `vm2` dependency up to date and track possible regressions.

## Checklist


- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [x] Tests for the changes have been added / updated.
- [x] Code has been formatted via `zk fmt` and `zk lint`.

## What ❔

Use precompiled `rocksdb` and `snappy` in the nix build.

## Why ❔

Speeds up compilation and is usually better maintained.

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zk fmt` and `zk lint`.

Signed-off-by: Harald Hoyer <harald@matterlabs.dev>

)

## What ❔

Add `/queue_report` endpoint, which will get the data about queue and
send it.

## Why ❔

To work with new autoscaler

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [ ] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zk fmt` and `zk lint`.

---------

Co-authored-by: EmilLuta <EmilLuta@users.noreply.github.com>

…rices (matter-labs#2927)

Signed-off-by: tomg10 <lemures64@gmail.com>
Co-authored-by: perekopskiy <mikeson.dp@gmail.com>

It will allow us to announce the recommended default list of peers to
all ENs without manual intervention.
Fixes BFT-509.

---------

Co-authored-by: Bruno França <bruno@franca.xyz>

## What ❔

- Allows to continue batch execution on divergence via new
`ShadowLenient` VM mode.
- Dumps VM state to logs and optionally a file on divergence.

## Why ❔

Allows to detect divergencies in multiple batches w/o blockers. The
dumped VM state will hopefully allow investigating divergencies locally,
although this logic isn't implemented yet.

## Checklist

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [x] Tests for the changes have been added / updated.
- [x] Documentation comments have been added / updated.
- [x] Code has been formatted via `zk fmt` and `zk lint`.

…tter-labs#2930)

## What ❔

In some places our sqlx queries are using string literals instead of
query macros. This PR changes this behaviour in places it is possible.

## Why ❔

To prevent possible SQL injections.
It also will cache the queries, which should make them faster.

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [ ] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zk fmt` and `zk lint`.

### Summary

This PR introduces a new component `circuit_prover`, which is multiple
WVGs & GPU prover running together, groupless. The changes are
non-destructive, old setup and new setup must work together in-tandem.

### What?

Circuit prover is a component that runs X WVGs alongside a GPU prover.
Making full use of CPUs on the GPU machine, WVGs as a component can be
removed altogether. Prover groups are not needed anymore. Based on
empiric testing we can (almost -- there will be follow-up fixes to make
it efficient) fully run everything on a single machine.

The current implementation can sunset the old setup. Current metrics
show that circuit prover is > 60% efficient than old one (but quirks are
needed for node proofs to unlock it -- will be treated as a follow-up).

The purpose is to have the `circuit_prover` deprecate old `prover_fri` &
`witness_vector_generator`.

### Why?

The changes will allow us to reduce our infrastructure footprint by ~2x
and fix plenty of issues we had in the past. Namely:
- fully decoupled of GCP
- better resource utilization & reduce costs
- reduce overall infrastructure needs (which solves the GPU
unavailability we've been facing)
- reduce complexity & other inefficiencies (no more prover groups!)
- and more

### Ask

We want to unblock folks running on AWS. This PR is done as is to speed
up release process on DevOps side, as it's the longest pole.

NOTE: This is the first PR out of a longer set of PRs.

Comments are more than welcome, but the following concerns will be
addressed in follow-up PRs and are out of scope for this PR:
- tracing implementation is subpar; in fact, I'm confident that most
metrics could be done via traces
- there's a lot of code duplication (both old/new prover, but runner
interface between new WVG & CP)
- tests
- concern separation between job scheduling & job execution
- job priority based on resource consumption
- other nits (such as no README, constants being hard-coded instead of
configuration, etc.)

### Reviewer suggestion

This is basically a merge between `prover_fri`,
`witness_vector_generation` and `JobProcessor`. Checking code alongside
should give you a better view of what's going on. Sorry for making this
hard. :/

## What ❔

Refactors `L1BatchParamsProvider`, in particular its construction.

## Why ❔

To have more intuitive DevEx.

## Checklist

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [x] Tests for the changes have been added / updated.
- [x] Documentation comments have been added / updated.
- [x] Code has been formatted via `zk fmt` and `zk lint`.

…s#2885)

## What ❔

Continues oneshot VM executor extraction by moving generic environment
types to the `zksync_vm_executor` crate.

## Why ❔

Makes it possible to use the VM executor outside the API server. E.g.,
it's now used in `zksync_node_consensus`.

## Checklist

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [x] Tests for the changes have been added / updated.
- [x] Documentation comments have been added / updated.
- [x] Code has been formatted via `zk fmt` and `zk lint`.

Discovered during testing Gateway integration (our own asserts from
query.rs started being triggered by our eth api implementation :D )

---------

Co-authored-by: perekopskiy <mikeson.dp@gmail.com>

## What ❔
Adding more information to the EN Grafana dashboards, which barely had
any.

## Why ❔
Better observability.

Fixes BFT-507

🤖 I have created a release *beep* *boop*
---


##
[24.26.0](matter-labs/zksync-era@core-v24.25.0...core-v24.26.0)
(2024-09-23)


### Features

* added seed_peers to consensus global config
([matter-labs#2920](matter-labs#2920))
([e9d1d90](matter-labs@e9d1d90))
* **circuit_prover:** Add circuit prover
([matter-labs#2908](matter-labs#2908))
([48317e6](matter-labs@48317e6))
* **prover:** Add endpoint to PJM to get queue reports
([matter-labs#2918](matter-labs#2918))
([2cec83f](matter-labs@2cec83f))
* **vm:** Do not panic on VM divergence
([matter-labs#2705](matter-labs#2705))
([7aa5721](matter-labs@7aa5721))
* **vm:** Extract oneshot VM executor – environment types
([matter-labs#2885](matter-labs#2885))
([a2d4126](matter-labs@a2d4126))


### Bug Fixes

* **api_server:** fix blob_gas length
([matter-labs#2673](matter-labs#2673))
([44a8f79](matter-labs@44a8f79))
* **eth-sender:** print better error message in case of missing blob
prices ([matter-labs#2927](matter-labs#2927))
([38fc824](matter-labs@38fc824))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

---------

Co-authored-by: zksync-era-bot <zksync-era-bot@users.noreply.github.com>

After new prover was introduced, a new flag is needed for code that
touches GPU related code that has no CUDA available. This PR adds the
flag to CI pipelines that were missed.
[Sample](https://github.com/matter-labs/zksync-era/actions/runs/10958933706/job/30430256489)
broken CI.

## What ❔

Splits old and new VM implementations in the `multivm` crate:

- Old VMs are encapsulated in the `LegacyVmInstance` enum, while new
ones in the `FastVmInstance` enum (which includes plain and shadowed VM
variants).
- Fast VM and `FastVmInstance` now expose a tracer type.
- Usage of the Fast VM in the batch executor are updated
correspondingly.

## Why ❔

It seems infeasible to unify the tracer model for old and new VMs, so
keeping them all in a single enum makes little sense.

## Checklist

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [x] Tests for the changes have been added / updated.
- [x] Documentation comments have been added / updated.
- [x] Code has been formatted via `zk fmt` and `zk lint`.

…ion and zk_supervisor (matter-labs#2934)

## What ❔

- Introduced `--inception` and `--supervisor` options to allow users to
specify which binaries to install.
- Removed the `ZKUP_SKIP_ZK_SUPERVISOR` option.

## Why ❔

Make it clear what to install, focusing on what to include rather what
to exclude

…2935)

## What ❔

Add zk toolbox unit tests to zks test

…atter-labs#2939)

This will enable us to build images for circuit proving (new version).
Not tested.

---------

Co-authored-by: Yury Akudovich <ya@matterlabs.dev>

## What ❔

Copy setup keys to be available for docker/circuit-prover-gpu-gar.
<!-- What are the changes this PR brings about? -->
<!-- Example: This PR adds a PR template to the repo. -->
<!-- (For bigger PRs adding more context is appreciated) -->

## Why ❔

To build circuit-prover-gpu image with keys.
<!-- Why are these changes done? What goal do they contribute to? What
are the principles behind them? -->
<!-- Example: PR templates ensure PR reviewers, observers, and future
iterators are in context about the evolution of repos. -->

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [x] Code has been formatted via `zk fmt` and `zk lint`.

….rs" (matter-labs#2945)

## What ❔

This PR fixes 2 invalid links in the documents which was caused by
refactor (refactor: Split the rest of the zksync_core
(matter-labs#1940))

## Why ❔

Unclarity in documentation

## Checklist

- [ ] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [x] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zk fmt` and `zk lint`.

Previously, this was done via a compile flag. This was deemed poor taste
and we've moved a specific env-var - `ZKSYNC_USE_CUDA_STUBS`. This is
wired deep within crypto dependencies.

This PR updates the dependencies, adds documentation on how to work with
the flag and updates all workflows (fixing the broken ones from
RUSTFLAGS time).

---------

Co-authored-by: Igor Aleksanov <popzxc@yandex.ru>

16 minutes is just ridiculous. This should've been done a long time ago,
but has been avoided due to other priorities and always put on the
back-burner/forgotten. Today we change it.

## What ❔

It was an inconsistency between call tracer results

## Why ❔

<!-- Why are these changes done? What goal do they contribute to? What
are the principles behind them? -->
<!-- Example: PR templates ensure PR reviewers, observers, and future
iterators are in context about the evolution of repos. -->

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [x] Code has been formatted via `zk fmt` and `zk lint`.

---------

Signed-off-by: Danil <deniallugo@gmail.com>

🤖 I have created a release *beep* *boop*
---


##
[24.27.0](matter-labs/zksync-era@core-v24.26.0...core-v24.27.0)
(2024-09-25)


### Features

* **vm:** Split old and new VM implementations
([matter-labs#2915](matter-labs#2915))
([93bc66f](matter-labs@93bc66f))


### Bug Fixes

* **api:** Return correct flat call tracer
([matter-labs#2917](matter-labs#2917))
([218646a](matter-labs@218646a))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

---------

Co-authored-by: zksync-era-bot <zksync-era-bot@users.noreply.github.com>

This PR contains code from sync-layer-stable + I removed old upgrades
processor and updated unit-tests to use the new one

---------

Signed-off-by: tomg10 <lemures64@gmail.com>

## What ❔

Create WG struct with generic round param.
Implement generic JobProcessor for all types of WG.

## Why ❔

<!-- Why are these changes done? What goal do they contribute to? What
are the principles behind them? -->
<!-- Example: PR templates ensure PR reviewers, observers, and future
iterators are in context about the evolution of repos. -->

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [ ] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zk fmt` and `zk lint`.

## What ❔

Removes deprecated proof loading for eth-sender

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [ ] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zk fmt` and `zk lint`.

…finalized_block (matter-labs#2969)

Signed-off-by: tomg10 <lemures64@gmail.com>

## What ❔

- ~`.cargo/config.toml` is a remnant from when we used private repos. It
should no longer be necessary.~
- ~`configs/` doesn't seem to be used at all.~
- `building-from-scratch` just contains an old docker file that was used
for Coinbase. No longer used.

## What ❔
Adds https://rustsec.org/advisories/RUSTSEC-2024-0375 to `deny.toml`,
which is due to `StructOpt`.

<!-- What are the changes this PR brings about? -->
<!-- Example: This PR adds a PR template to the repo. -->
<!-- (For bigger PRs adding more context is appreciated) -->

## Why ❔
* Currently it's impossible to migrate to clap as
[zkevm_test_harness](https://github.com/matter-labs/era-zkevm_test_harness/blob/v1.5.0/Cargo.toml#L46)
still depends on structopt.

* This
[unblocks](https://github.com/matter-labs/zksync-era/actions/runs/11054218994/job/30710479095)
the CI

<!-- Why are these changes done? What goal do they contribute to? What
are the principles behind them? -->
<!-- Example: PR templates ensure PR reviewers, observers, and future
iterators are in context about the evolution of repos. -->

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [x] Tests for the changes have been added / updated.
- [x] Documentation comments have been added / updated.
- [x] Code has been formatted via `zk fmt` and `zk lint`.

In some previous pr, I've added a field to json RPC response
(consensusGlobalConfig) and it turned out to be incompatible due to the
default parsing behavior: an error was returned when unknown fields were
present. In general, for programmatic communications the recommended
behaviour is to silently ignore unknown fields, so that adding new
fields is compatible.

I've also weakened the restriction on accepting new consensus genesis by
external nodes - when the unknown fields are silently dropped, it is
possible that the node will perceive genesis with the same fork number
differently after a binary update (because it receives more fields).

…2973)

## What ❔

Use governor for minting process and do not panic if minting is not
successful

## Why ❔

<!-- Why are these changes done? What goal do they contribute to? What
are the principles behind them? -->
<!-- Example: PR templates ensure PR reviewers, observers, and future
iterators are in context about the evolution of repos. -->

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [ ] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zk fmt` and `zk lint`.

Signed-off-by: Danil <deniallugo@gmail.com>

…2900)

zk_toolbox command for setting attester committee in consensus registry
contract.

Fixes BFT-505

---------

Co-authored-by: Bruno França <bruno@franca.xyz>

## What ❔

Added support for chainstack developer and growth plan. 

## Why ❔

I was getting the below error with chainstack's growth plan when I tried
run self deployed zksync hyperchain. To fix this, I have added
appropriate changes to the code.

```
ERROR zksync_eth_watch: Failed to process new blocks: Eth client error: JSON-RPC request get_logs(filter=Filter { from_block: Some(Number(6732838)), to_block: Some(Number(6757429)), block_hash: None, address: Some(ValueOrArray([0xadd82b0c015be3fb7e8410061b4f15d577b4207f, 0xd6ee28b24f87c1d634540699b00e9c37fdc7b3bd, 0x41b75786db38a486c99972c8322fcb14c4f000a2, 0x5d300908338b85bee3f30f2e0ad196fc1587b70d])), topics: Some([Some(ValueOrArray([0x4531cd5795773d7101c17bdeb9f5ab7f47d7056017506f937083be5d6e77a382, 0x23bc9f5dc037eb49c162fd08c2a4d43dfe70063149e140d502273168da0a0625, 0xd50ef21701c8ef211433b140724b8d6de471e7d822c8a616c3d424fe2d0e98a9]))]), limit: None }) failed: ErrorObject { code: InvalidParams, message: "Block range limit exceeded. See more details at https://docs.chainstack.com/docs/limits#evm-range-limits", data: None }
```

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [x] Tests for the changes have been added / updated.
- [x] Documentation comments have been added / updated.
- [x] Code has been formatted via `zk fmt` and `zk lint`.

Signed-off-by: tomg10 <lemures64@gmail.com>

## What ❔

Updates `derive_more` to a stable version.

<!-- What are the changes this PR brings about? -->
<!-- Example: This PR adds a PR template to the repo. -->
<!-- (For bigger PRs adding more context is appreciated) -->

## Why ❔

We're currently on beta and this is a requisite for supporting
[foundry-zksync](https://github.com/matter-labs/foundry-zksync).

<!-- Why are these changes done? What goal do they contribute to? What
are the principles behind them? -->
<!-- Example: PR templates ensure PR reviewers, observers, and future
iterators are in context about the evolution of repos. -->

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [x] Tests for the changes have been added / updated.
- [x] Documentation comments have been added / updated.
- [x] Code has been formatted via `zk fmt` and `zk lint`.

## What ❔

Add an opportunity to store the sensitive information of DA clients in
the secrets.

## Why ❔

Some sensitive info is currently stored as plaintext, which is not
secure, we should use secrets for those values

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [ ] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zk fmt` and `zk lint`.

---------

Co-authored-by: Danil <deniallugo@gmail.com>

## What ❔

Changes the `debug_traceCall` handler to use the fee provider for recent
blocks (pending / latest / committed).

## Why ❔

Previously, the `debug` namespace used a static batch fee input
retrieved at the node initialization. This looks incorrect.

## Checklist

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [x] Tests for the changes have been added / updated.
- [x] Documentation comments have been added / updated.
- [x] Code has been formatted via `zk fmt` and `zk lint`.

)

## What ❔

<!-- What are the changes this PR brings about? -->
<!-- Example: This PR adds a PR template to the repo. -->
<!-- (For bigger PRs adding more context is appreciated) -->
Add fees integration test to toolbox and CI.

## Why ❔

<!-- Why are these changes done? What goal do they contribute to? What
are the principles behind them? -->
<!-- Example: PR templates ensure PR reviewers, observers, and future
iterators are in context about the evolution of repos. -->

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zk fmt` and `zk lint`.

---------

Signed-off-by: Danil <deniallugo@gmail.com>
Co-authored-by: Danil <deniallugo@gmail.com>

## What ❔
Exposes the consensus http debug on port 5000.
Fixes BFT-508

## What ❔
Added `EcosystemPortsScanner` tool to scan ecosystem directory config
and find all values for ports.
Returns `EcosystemPorts` object with ports found and custom description
of a service.
`EcosystemPorts` also contains methods to: check whether the port is
assigned, allocate a new port in range, etc.

## Why ❔
With multiple chains and number of services (like explorer, etc.)
growing - it is useful to have a tool (`EcosystemPorts`) that can be
used to allocate new ports, thus, lowering the chance of port conflicts
within created configuration.

## Checklist
- [ ] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zk fmt` and `zk lint`.

---------

Co-authored-by: Matías Ignacio González <maigonzalez@fi.uba.ar>

## What ❔
ENs, started from docker compose, now have consensus and pruning enabled
as default. Also, the EN docs were updated.

## What ❔

Removing deprecated `artifacts` dir from build process

## Why ❔

<!-- Why are these changes done? What goal do they contribute to? What
are the principles behind them? -->
<!-- Example: PR templates ensure PR reviewers, observers, and future
iterators are in context about the evolution of repos. -->

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zk fmt` and `zk lint`.

## What ❔

<!-- What are the changes this PR brings about? -->
<!-- Example: This PR adds a PR template to the repo. -->
<!-- (For bigger PRs adding more context is appreciated) -->

## Why ❔

<!-- Why are these changes done? What goal do they contribute to? What
are the principles behind them? -->
<!-- Example: PR templates ensure PR reviewers, observers, and future
iterators are in context about the evolution of repos. -->

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [ ] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zk fmt` and `zk lint`.

Signed-off-by: Danil <deniallugo@gmail.com>

## What ❔

Makes gas estimation more efficient by using heuristics similar to ones
used by Ethereum clients:

- Defines the lower gas limit bound as the gas consumed with an
effectively infinite gas limit.
- Defines an initial binary search pivot as a slightly larger value so
that in the best / average case, most of the search space is immediately
discarded.

## Why ❔

Improves gas estimation latency in the best and average case.

## Checklist

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [x] Tests for the changes have been added / updated.
- [x] Documentation comments have been added / updated.
- [x] Code has been formatted via `zk fmt` and `zk lint`.

…inverse error (matter-labs#2970)

## What ❔

- I introduce tests to external_price_api crate. Some work was taken
from matter-labs#2315
- fix multiplicative inverse ratio calculation bug
- fix missing checks in get_fraction

## Why ❔

- We want to make sure the flow of data from API response to token ratio
is correct

## Checklist

- [X] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [X] Tests for the changes have been added / updated.
- [X] Documentation comments have been added / updated.
- [X] Code has been formatted via `zk fmt` and `zk lint`.

## What ❔

Switch to zk_supervisor fmt in our githooks
## Why ❔

<!-- Why are these changes done? What goal do they contribute to? What
are the principles behind them? -->
<!-- Example: PR templates ensure PR reviewers, observers, and future
iterators are in context about the evolution of repos. -->

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [ ] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zk fmt` and `zk lint`.

---------

Signed-off-by: Danil <deniallugo@gmail.com>

## What ❔
Add SQL format for zk supervisor

## What ❔

Add Makefile for easier local build of all components

## Why ❔

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [x] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zk fmt` and `zk lint`.

…2922)

## What ❔

Right now, while running prover binaries inside of zksync-era, config
paths are specified as path to config from chain config(which is
`./chain/configs` - relative path, but not absolute). This breaks,
because to run prover binaries, shell enters prover directory of era.

## Why ❔

<!-- Why are these changes done? What goal do they contribute to? What
are the principles behind them? -->
<!-- Example: PR templates ensure PR reviewers, observers, and future
iterators are in context about the evolution of repos. -->

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [ ] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zk fmt` and `zk lint`.

## What ❔

Update databases during update process, now it's a universal receipt how
to pull changes
## Why ❔

<!-- Why are these changes done? What goal do they contribute to? What
are the principles behind them? -->
<!-- Example: PR templates ensure PR reviewers, observers, and future
iterators are in context about the evolution of repos. -->

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [ ] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zk_supervisor fmt` and `zk_supervisor
lint`.

Signed-off-by: Danil <deniallugo@gmail.com>

…oundry (matter-labs#3000)

## What ❔

Creation of empty dirs, to support building from both new
(foundry-built) and old contracts

## Why ❔

<!-- Why are these changes done? What goal do they contribute to? What
are the principles behind them? -->
<!-- Example: PR templates ensure PR reviewers, observers, and future
iterators are in context about the evolution of repos. -->

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zk_supervisor fmt` and `zk_supervisor
lint`.

🤖 I have created a release *beep* *boop*
---


##
[24.28.0](matter-labs/zksync-era@core-v24.27.0...core-v24.28.0)
(2024-10-02)


### Features

* **da-clients:** add secrets
([matter-labs#2954](matter-labs#2954))
([f4631e4](matter-labs@f4631e4))
* **eth-sender:** add a cap to time_in_mempool
([matter-labs#2978](matter-labs#2978))
([650d42f](matter-labs@650d42f))
* **eth-watch:** redesign to support multiple chains
([matter-labs#2867](matter-labs#2867))
([aa72d84](matter-labs@aa72d84))
* Expose http debug page
([matter-labs#2952](matter-labs#2952))
([e0b6488](matter-labs@e0b6488))
* **zk_toolbox:** add fees integration test to toolbox
([matter-labs#2898](matter-labs#2898))
([e7ead76](matter-labs@e7ead76))
* **zk_toolbox:** Add SQL format for zk supervisor
([matter-labs#2950](matter-labs#2950))
([540e5d7](matter-labs@540e5d7))


### Bug Fixes

* **api:** Fix batch fee input for `debug` namespace
([matter-labs#2948](matter-labs#2948))
([79b6fcf](matter-labs@79b6fcf))
* chainstack block limit exceeded
([matter-labs#2974](matter-labs#2974))
([4ffbf42](matter-labs@4ffbf42))
* **eth-watch:** add missing check that from_block is not larger than
finalized_block
([matter-labs#2969](matter-labs#2969))
([3f406c7](matter-labs@3f406c7))
* ignore unknown fields in rpc json response
([matter-labs#2962](matter-labs#2962))
([692ea73](matter-labs@692ea73))


### Performance Improvements

* **api:** More efficient gas estimation
([matter-labs#2937](matter-labs#2937))
([3b69e37](matter-labs@3b69e37))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

---------

Co-authored-by: zksync-era-bot <zksync-era-bot@users.noreply.github.com>

…atter-labs#2946)

## What ❔
Added subcommands:
`zki chain init configs` - just creates configs with an intention to run
chain initialization manually via subcommands
`zki chain register-chain` - runs steps from `RegisterHyperchain.s.sol`
`zki chain accept-chain-ownership` - accepts ownership for
`DiamondProxy`
`zki chain genesis database` - initializes database only, performs
migration (uses values from args or `secrets.yaml`)
`zki chain genesis server` - runs server --genesis

Added flags:
`zki ecosystem init --ecosystem-only` - runs `init` only for ecosystem
(skips `init` for chain)

Other changes:
* Fixed issue with `--wallet_path` value ignored
* Nullify database names if `zki ecosystem init` is used for multiple
chains
* Zeroify some addresses in `contracts.yaml` when copying from ecosystem
during init

## Why ❔
These changes allow us to run the chain registration process for
externally hosted chains.
Not ideal yet, but the process goes like this:
L1 side:
* Init ecosystem: `zki ecosystem create && zki ecosystem init
--ecosystem-only && zki chain init configs`
* Fill in wallets
* Register chain: `zki chain register-chain`
* Deploy L2 contracts: `zki chain deploy-l2-contracts`
* Share `contracts.yaml`

L2 side:
* Init ecosystem: `zki ecosystem create && zki ecosystem init
--ecosystem-only && zki chain init configs`
* Fill in wallets
* Copy `contracts.yaml`
* Accept ownership: `zki chain accept-chain-ownership`
* Initialize databases: `zki chain genesis database`
* Run server genesis: `zki chain genesis server`

## Checklist
- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [x] Documentation comments have been added / updated.
- [x] Code has been formatted via `zk fmt` and `zk lint`.

## What ❔

<!-- What are the changes this PR brings about? -->
<!-- Example: This PR adds a PR template to the repo. -->
<!-- (For bigger PRs adding more context is appreciated) -->

## Why ❔

<!-- Why are these changes done? What goal do they contribute to? What
are the principles behind them? -->
<!-- Example: PR templates ensure PR reviewers, observers, and future
iterators are in context about the evolution of repos. -->

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [ ] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zk_supervisor fmt` and `zk_supervisor
lint`.

Signed-off-by: Danil <deniallugo@gmail.com>

## What ❔

Add external-node build to Makefile

## Why ❔

<!-- Why are these changes done? What goal do they contribute to? What
are the principles behind them? -->
<!-- Example: PR templates ensure PR reviewers, observers, and future
iterators are in context about the evolution of repos. -->

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [x] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zk_supervisor fmt` and `zk_supervisor
lint`.

## What ❔
Remove prover db from server init

## Why ❔

prover db is not needed in server init since prover db is initialized
with prover init

## What ❔

Ability to build zk-env with cuda not only from push to main branch

## Why ❔

<!-- Why are these changes done? What goal do they contribute to? What
are the principles behind them? -->
<!-- Example: PR templates ensure PR reviewers, observers, and future
iterators are in context about the evolution of repos. -->

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zk_supervisor fmt` and `zk_supervisor
lint`.

## What ❔

Periodically fetch bridge addresses

## Why ❔

Addresses will be changed during gateway upgrade

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [ ] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zk fmt` and `zk lint`.

## What ❔

<!-- What are the changes this PR brings about? -->
<!-- Example: This PR adds a PR template to the repo. -->
<!-- (For bigger PRs adding more context is appreciated) -->

## Why ❔

<!-- Why are these changes done? What goal do they contribute to? What
are the principles behind them? -->
<!-- Example: PR templates ensure PR reviewers, observers, and future
iterators are in context about the evolution of repos. -->

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [ ] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zk_supervisor fmt` and `zk_supervisor
lint`.

## What ❔

Covers more `TxSender` functionality with unit tests.

## Why ❔

More test coverage is good. Also, it will help with new VM integration
(by running the added tests with a shadowed VM).

## Checklist

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [x] Tests for the changes have been added / updated.
- [x] Code has been formatted via `zk_supervisor fmt` and `zk_supervisor
lint`.

Configuration parameter for time_in_mempool_cap, cap for time_in_mempool
in eth-sender fee model + default values for parameter_a and parameter_b
for GasAdjuster

## What ❔

`fmt --check` wasn't returning an error code when failing

…bs#3016)

## What ❔

<!-- What are the changes this PR brings about? -->
<!-- Example: This PR adds a PR template to the repo. -->
<!-- (For bigger PRs adding more context is appreciated) -->
Remove `generate-sk` subcommand which doesn’t exist anymore.

## Why ❔

<!-- Why are these changes done? What goal do they contribute to? What
are the principles behind them? -->
<!-- Example: PR templates ensure PR reviewers, observers, and future
iterators are in context about the evolution of repos. -->

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [x] Tests for the changes have been added / updated.
- [x] Documentation comments have been added / updated.
- [x] Code has been formatted via `zk_supervisor fmt` and `zk_supervisor
lint`.

## What ❔

Removes unit test files for old VM versions in the `multivm` crate.

## Why ❔

These tests are not built (not included into the module tree of the
crate), so they are just deadweight.

## Checklist

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).

## What ❔

Brushes up the `eth_signer` crate so that its API is easier to use
(e.g., it doesn't require an async runtime).

## Why ❔

Improved DevEx.

## Checklist

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [x] Tests for the changes have been added / updated.
- [x] Documentation comments have been added / updated.
- [x] Code has been formatted via `zk_supervisor fmt` and `zk_supervisor
lint`.