## What ❔

GH resolver wasn't adding `v` for zksolc/zkvyper, while our API expects
it.

## What ❔

Hi @Deniallugo @popzxc 👋

Was playing with zkstack cli today. 

This PR is just fixing a couple of broken links and updating a bit of
wording in `zkstack_cli/README.md`.

PS: sidenote, "EVM emulator" is not explained in this readme, and
"Enable EVM emulator?" in interactive mode will be confusing to people
(they likely wont realize that it is emulating EVM equivalence but not
required for most chains + will be more expensive)

## Why ❔

Possibly a bit OCD, ie "Zk" being wrongly cased in one instance stayed
in my mind and bothered me hahahah 😉
<!-- 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 `zkstack dev fmt` and `zkstack dev
lint`.

This PR introduces the `custom_genesis_export` tool, designed to export
zkSync PostgreSQL database state in a format suitable for initializing a
custom genesis state for a new chain.

- Exports `initial_writes`, `storage_logs`, and `factory_deps`
(excluding system context entries) into a binary file.
- Updates the `genesis.yaml` file with:
- `genesis_root_hash`, `rollup_last_leaf_index`, and
`genesis_commitment` matching the exported data.
- Adds `custom_genesis_state_path` pointing to the export file, which is
recognised by the server during genesis.
- Adds support for initialising from a custom genesis state to the
server.

---------

Co-authored-by: Ivan Schasny <[email protected]>
Co-authored-by: Ivan Schasny <[email protected]>

## What ❔

The duration of a view timeout was previously hard-coded in
era-consensus (at 2 seconds). This caused excessive view changes in
networks with low traffic. era-consensus v0.7 now has view timeout
duration as a config parameter and downgraded view change logging from
`error` to `warn`. This PR includes those changes in zksync-era.

## What ❔
* erc configuration was overwriting the initial configuration (it was
using wrong file constant)

Implements an account validation gas limit and the validation tracer for
vm2, along with better tests for validation.

Instead of a second gas limit like in vm_latest, the normal gas limit is
used. Unfortunately this means that the VM is not safe to use in the
sequencer until we forbid the use of gasleft. I didn't do it here
because it requires something like taint analysis and could break
existing contracts that didn't know that gasleft is forbidden.

---------

Co-authored-by: Alex Ostrovski <[email protected]>
Co-authored-by: Alex Ostrovski <[email protected]>

tbd

---------

Co-authored-by: zksync-admin-bot2 <[email protected]>
Co-authored-by: Lech <[email protected]>

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


##
[25.4.0](core-v25.3.0...core-v25.4.0)
(2024-12-19)


### Features

* add support for custom genesis state
([#3259](#3259))
([3cffdb2](3cffdb2))
* **consensus:** Added view_timeout to consensus config
([#3383](#3383))
([fc02a8f](fc02a8f))
* Support stable compiler for VM (and some other crates)
([#3248](#3248))
([cbee99d](cbee99d))
* vm2 account validation
([#2863](#2863))
([af149a0](af149a0))


### Bug Fixes

* **contract-verifier:** Fix version extraction in gh resolver
([#3378](#3378))
([9a10dcf](9a10dcf))

---
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 <[email protected]>