## What ❔

Updates the installing instructions for SQLx CLI

## Why ❔

Problems when compiling `clap_lex`:
`error[E0599]: no method named `as_encoded_bytes` found for reference
`&OsStr` in the current scope`
`error[E0599]: no function or associated item named
`from_encoded_bytes_unchecked` found for struct `OsStr` in the current
scope`

Note: healthchecks for `Main Node` and `Eth` client layers will be added
in the next PR(there is a general principle of change.)

## 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`.
- [ ] Spellcheck has been run via `zk spellcheck`.

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


##
[14.5.0](matter-labs/zksync-era@prover-v14.4.0...prover-v14.5.0)
(2024-06-04)


### Features

* update VKs and bump cargo.lock
([matter-labs#2112](matter-labs#2112))
([6510317](matter-labs@6510317))
* use semver for metrics, move constants to prover workspace
([matter-labs#2098](matter-labs#2098))
([7a50a9f](matter-labs@7a50a9f))


### Bug Fixes

* **block-reverter:** Fix reverting snapshot files
([matter-labs#2064](matter-labs#2064))
([17a7e78](matter-labs@17a7e78))
* **house-keeper:** Fix queue size queries
([matter-labs#2106](matter-labs#2106))
([183502a](matter-labs@183502a))

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

…s#2131)

## What ❔

Adds a couple of metrics / logs for tree data fetcher related to
fetching data from L1. Follow-up after matter-labs#2000.

## Why ❔

These metrics / logs would allow to track tree data fetcher health more
thoroughly.

## 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`.
- [x] Spellcheck has been run via `zk spellcheck`.

…#2017)

## What ❔

Adds a new component `vm_runner_protective_reads` that computes
protective reads independently and asynchronously from state keeper.

For now, the component does not actually save anything; instead, it
computes protective reads and compares them against what state keeper
has already written to the DB. So, in short, this is just the first
stepping stone aka a sanity check that the VM runner mechanism works as
intended.

## Why ❔

In the future, we want to be able to save protective reads
asynchronously thus saving time on L1 batch sealing.

## 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.
- [x] Code has been formatted via `zk fmt` and `zk lint`.
- [x] Spellcheck has been run via `zk spellcheck`.

## What ❔

Removes L1 client health check from EN.

## Why ❔

Doesn't bring that much value and leads to L1 client getting
rate-limited for our GCS ENs.

## Checklist

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [x] Code has been formatted via `zk fmt` and `zk lint`.
- [x] Spellcheck has been run via `zk spellcheck`.

## What ❔

Fixes changes from matter-labs/era-contracts#504

…ction (matter-labs#2091)

These fields are unused and don't affect the execution. eth_hash and
deadline_block are not even stored, so they have been removed
completely. eth_block is stored in db and is part of the block signed by
consensus, therefore removing it will require a protocol upgrade and a
hard fork.

## What ❔

Update the `pubdata.md` doc, and copy the 4844-related docs. 

## Why ❔

The docs in `pubdata.md` were outdated, and lacking the EIP-4844
details.

## 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`.
- [ ] Spellcheck has been run via `zk spellcheck`.

## What ❔

save l2 l1 logs for miniblock only if there are some

## Why ❔

We save l2 l1 logs using `COPY` and it appears it has some constant
overhead of ~40ms regardless whether there is some data to copy or not.
By checking if l2_l1_logs.is_empty we can save this 40ms.

## 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`.
- [ ] Spellcheck has been run via `zk spellcheck`.

## What ❔

Allows recovering a node from a specific snapshot specified at the start
of recovery.

## Why ❔

Useful at least for testing recovery and pruning end-to-end on the
testnet. There, L1 batches are produced very slowly, so it makes sense
to recover from an earlier snapshot in order to meaningfully test
pruning.

## 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`.
- [x] Spellcheck has been run via `zk spellcheck`.

## What ❔

* Updated boojum version, which allows us to update nightly rust
compiler.

## Why ❔

* Our rust nightly is quite old (around 1 year)

…-labs#2140)

## What ❔

Considers a subset of contract call errors as transient.

## Why ❔

Currently, consistency checker considers all contract call errors fatal,
which leads to EN terminating when it shouldn't.

## Checklist

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [x] Code has been formatted via `zk fmt` and `zk lint`.
- [x] Spellcheck has been run via `zk spellcheck`.

…tter-labs#2148)

## What ❔

- Tweaking postgres `healthcheck` command in EN Docker Compose example
to work from shells other than bash
- Minor formatting fixes to the aforementioned Docker Compose example
files
- EN bump to the latest stable in the aforementioned Docker Compose
example files

## Why ❔

Fixes:
**zkSync-Community-Hub/zksync-developers#526 (comment)

## 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`.
- [ ] Spellcheck has been run via `zk spellcheck`.

## What ❔

* Prover_cli has a new command - `debug-proof`, that prints a lot more
detailed information about any basic proof file.

## Why ❔

* This will speed up debugging  of the failed proofs.
* Small caveat - the cli has to be compiled with `verbose_circuits`
feature - which will include the whole zkevm_test_harness and all the
other crypto libraries.


How to use:
* Simply download the .bin file with the proof, and run `./prover_cli
debug-proof file.bin`

Part of EVM-639

matter-labs#2147)

…st images.

## What ❔

* Added workflow_dispatch to zk_enviroinment

## Why ❔

* This way, you can build the 'experimental' docker images to test
things before merging into 'main' branch.
* It will build only zk_environment basic (not GPU specific ones), and
it will NOT mark it as latest.

…ork (matter-labs#2138)

## What ❔

Refactors `ObjectStore` and `ObjectStoreFactory` to fit it into the node
framework:

- Consistently uses `Arc<dyn ObjectStore>` in DI
- Clearly documents `ObjectStoreFactory` as one possible `ObjectStore`
producer
- Expose GCS, file-based and mock object stores directly and remove
ability to create mock object stores from `ObjectStoreFactory`
- Refactors retries as `ObjectStore` "middleware"

## Why ❔

Currently, object store APIs don't fit into the node framework well,
leading to suboptimal 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`.
- [x] Spellcheck has been run via `zk spellcheck`.

## What ❔

- renames fields in method's response
- removes `verification_keys_hashes` completely

## Why ❔

- more meaningfully field names and camelCase for consistency
- `verification_keys_hashes` doesn't make sense in the context of minor
protocol version

## 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`.
- [x] Spellcheck has been run via `zk spellcheck`.

…atter-labs#2021)

## 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`.
- [ ] Spellcheck has been run via `zk spellcheck`.

…-labs#2144)

## What ❔

* Update historical_keys dir with the proper keys.

## Why ❔

* To maintain a clear history, and a small unittest to verify that they
are correct.

## What ❔

- Adds zk_toolbox CI with ecosystem initialization
- Add zk_supervisor integration-tests command
- Make paths in ecosystem config absolute

## Why ❔

- Improve CI flow

## 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`.
- [x] Spellcheck has been run via `zk spellcheck`.

…covery (matter-labs#2050)

## What ❔

Persists chunks during tree recovery in parallel to processing
subsequent chunks.

## Why ❔

- Could speed up tree recovery ~2x on the mainnet (both persistence and
processing of a single chunk of 200k entries take ~3s).
- Significantly easier to implement and reason about than alternatives.
- May be used together with alternatives.

## 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`.
- [x] Spellcheck has been run via `zk spellcheck`.

…r-labs#2158)

## What ❔

Adds a new config value that regulate which batch to consider as the
last processed on a fresh start.

Also renames config values to be more idiomatic due to several from
DevOps and other people :)

## Why ❔

We don't want to wait half a year for VM to process all testnet/mainnet
batches.

## 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.
- [x] Code has been formatted via `zk fmt` and `zk lint`.
- [x] Spellcheck has been run via `zk spellcheck`.

…labs#2143)

Added a bunch of intermediate representations for rlp structs. I need
these to be able to verify L1 batches for
https://linear.app/matterlabs/issue/BFT-471/implement-stateless-l1-batch-verification

Added .md to match other md names

## 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`.
- [ ] Spellcheck has been run via `zk spellcheck`.

## What ❔

* VK generation tool now allows specifying --jobs - to run multiple jobs
in parallel
* Added a progress bar

## Why ❔

* To make it easier (and faster) to generate new verification keys.

Fixes: EVM-642

## What ❔

Moves some easily movable stuff from `zksync_external_node` binary, e.g.

- rustc metrics
- main node healthcheck
- validate chain ids task

Note: this PR does not aim to be exhaustive. There will be more PRs like
this in the future.

## Why ❔

- Makes logic shareable (e.g. we can now use rustc metrics for main node
too)
- Less logic in binary makes it easier to switch to the framework.

## 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`.
- [ ] Spellcheck has been run via `zk spellcheck`.

…bs#2150)

## What ❔

Add file based config for fri prover gateway

## 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`.
- [x] Spellcheck has been run via `zk spellcheck`.

)

## What ❔

File based configs for witness generator

## 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`.
- [x] Spellcheck has been run via `zk spellcheck`.

## 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`.
- [ ] Spellcheck has been run via `zk spellcheck`.

Signed-off-by: Danil <[email protected]>

## 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`.
- [ ] Spellcheck has been run via `zk spellcheck`.

---------

Co-authored-by: Stanislav Bezkorovainyi <[email protected]>

Signed-off-by: tomg10 <[email protected]>

## 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`.
- [ ] Spellcheck has been run via `zk spellcheck`.

---------

Co-authored-by: Stanislav Bezkorovainyi <[email protected]>

…r-labs#2153)

## What ❔

Implements an optional caching layer for object store that persists
objects fetched from an external store (e.g., a GCS one) to a
configurable local directory.

## Why ❔

Allows to speed up repeated snapshot recovery w/o sacrificing generality
(i.e. switching to a file-backed store and downloading all snapshot data
manually).

## 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`.
- [x] Spellcheck has been run via `zk spellcheck`.

## What ❔

Add config package

## 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`.
- [x] Spellcheck has been run via `zk spellcheck`.

## What ❔

Add zkVM solc 1.0.1

## 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`.
- [ ] Spellcheck has been run via `zk spellcheck`.

## 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`.
- [ ] Spellcheck has been run via `zk spellcheck`.

---------

Signed-off-by: Danil <[email protected]>

…er-labs#2068)

## What ❔

Enables the MiniMerkleTree to be used for priority queue to efficiently
calculate merkle proofs for priority transactions.

## Why ❔

As part of the preparation for the priority queue migration to sync
layer.

## 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`.
- [ ] Spellcheck has been run via `zk spellcheck`.

Curl is unable to retry some transient errors, so it's more reliable to
use run_retried which retries any error

Signed-off-by: tomg10 <[email protected]>

In this PR: [Pull Request
matter-labs#2022](https://github.com/matter-labs/zksync-era/pull/2022/files), the
logic was changed to stop using the $ZKSYNC_HOME environment variable to
construct paths relative to the root of zksync-era.
But the prover is a separate workspace, so it fails to create the path
to the contract with the functions in the main workspace..

## Checklist

- [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`.
- [x] Spellcheck has been run via `zk spellcheck`.

Changes: 

- Get database url from the `prover_cli` config.
 - Remove the deletion of archived jobs.

---------

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

## 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`.
- [ ] Spellcheck has been run via `zk spellcheck`.

---------

Signed-off-by: Danil <[email protected]>

## What ❔

Fixes getting data for the pending block in `eth_getBlockByNumber` and a
couple of other methods.

## Why ❔

Getting a pending block should always return `null`, but right now it
actually doesn't. Caused by non-atomic reads from Postgres in the method
implementation: first, a pending block number is resolved, and then a
block with this number is fetched. Between these two reads, a block with
this number may be inserted to Postgres.

While it's somewhat unlikely that anyone will query a pending block,
it's still a correctness issue.

## Checklist

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

## 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`.
- [ ] Spellcheck has been run via `zk spellcheck`.

Signed-off-by: Danil <[email protected]>

…s#2020)

unused for ~4 months
removal requested by @RomanBrodetski

## What ❔

Fixes the latency of API server unit tests caused by the lack of
buffering when reading contracts.

## Why ❔

Lack of buffering is a logical error on its own. In this case, it leads
t slow test runs, i.e., degrades 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`.
- [x] Spellcheck has been run via `zk spellcheck`.

…atter-labs#2179)

## What ❔

Uses an SQL query for deleting past storage logs which promises to be
more efficient than the one currently used.

## Why ❔

The current DB query used for this purpose has fluctuating, but overall
slow, performance.

## 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`.
- [x] Spellcheck has been run via `zk spellcheck`.

…s#2199)

## What ❔

Optimize `get_l2_blocks_to_execute_for_l1_batch`

## Why ❔

`transactions.l1_batch_number` is not indexed

## 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`.
- [ ] Spellcheck has been run via `zk spellcheck`.

I've added more detailed logs.. I've also generally split the
calculations and metrics for fees for blob and non-blob transactions as
they are radically different.

---------

Signed-off-by: tomg10 <[email protected]>

## What ❔

Add zksolc v1.5.0

## 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`.
- [ ] Spellcheck has been run via `zk spellcheck`.

…lock (matter-labs#2208)

Signed-off-by: tomg10 <[email protected]>

…labs#2209)

## What ❔

Ditto

## Why ❔

Faster interruption

## 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`.
- [x] Spellcheck has been run via `zk spellcheck`.

A refactoring introduced lately caused multiple restarts in provers
(namely BWGs) when GCS was unavailable (502 or 503). This is a sporadic,
once in a while, but still invalides tens of minutes of work and makes
proving fickle and slow. This PR addresses the issue and restores old
behavior pre-refactoring, treating 502s and 503s as transient errors.

## What ❔

This PR just adds some basic VM runner-specific metrics. Note that VM
runner already inherits VM-related metrics from state keeper.

I decided to split `storage_load`/`vm_run`/`output_handle` into 3
different metrics as opposed to a single metric with 3 stages as the
stages happen asynchronously and don't represent a continuous execution.
Lmk if you disagree though.

## 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.
- [x] Code has been formatted via `zk fmt` and `zk lint`.
- [x] Spellcheck has been run via `zk spellcheck`.

…-labs#2197)

## What ❔

Fixes reorg detection logic so that it accounts for the tree data
fetcher:

- **In tree data fetcher:** Tries to detect reorgs, so that root hashes
are not written for diverging L1 batches.
- **In reorg detector:** Checks last L2 block correspondence during
binary searching a diverging L1 batch.

## Why ❔

Reorg detection may be broken if tree data fetcher is enabled:

- The tree data fetcher doesn't check that fetched L1 batch root hashes
correspond to local L1 batches, i.e. it can fetch a root hash after a
revert.
- Hence, the logic in reorg detector which binary-searches the diverged
L1 batch is broken because the latest L1 batch isn't guaranteed to
diverge if there's a divergence.

## 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`.
- [x] Spellcheck has been run via `zk spellcheck`.

## What ❔

Reworks tree rollback so that it's supported on the distributed external
node, including the case when a node runs multiple trees.

- Desync with Postgres is now detected on metadata calculator
initialization, and the tree is truncated correspondingly.
- The old approach is left intact as a safety guard.

## Why ❔

Right now, reorg logic on EN relies on a node running a single tree, and
block reverter being a singleton. Both these assumptions are bogus in
case of a distributed EN.

## 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`.
- [x] Spellcheck has been run via `zk spellcheck`.

…ce API (matter-labs#1993)

## What ❔

This PR introduces three new endpoints to the prover interface API:
1. `/tee/proof_inputs` - for fetching input data for the TEE verifier.
It is intended for TEE workers to obtain a batch to process.
2. `/tee/submit_proofs/<l1_batch_number>` - for submitting TEE proof.
3. `/tee/register_attestation` - for registering TEE attestation.

The first two introduced API endpoints correspond to the existing,
analogous `/proof_generation_data` and `/submit_proof/<l1_batch_number>`
endpoints used for the ZK proofs.

The state of batches (e.g., _proven_, _taken_, etc.) is tracked in the
database. The `TeeVerifierInputProducer` generates serialized TEE prover
inputs, which are then stored in the object store.

To run the unit tests, you need to use the following command: `zk test
rust --package zksync_proof_data_handler --lib tests`. Running `cargo
test` directly fails because the `zk` command sets up an additional
database for testing purposes.

To test it manually, run the ZK server with the command:
```
zk server --components proof_data_handler --use-node-framework
```
and then send an HTTP request:
- to get TEE verifier input data:
  ```
curl -X POST -H "Content-Type: application/json" --data-raw "{}" -vvv
http://127.0.0.1:3320/tee/proof_inputs
  ```
  To inspect the database for the TEE verifier input data jobs, run:
  ```
  $ PGPASSWORD='notsecurepassword' psql -h 127.0.0.1 -p 5432 -U postgres
  # \c zksync_local
  # SELECT * FROM tee_verifier_input_producer_jobs;
  ```
- register TEE attestation:
  ```
curl -X POST -H "Content-Type: application/json" --data-raw '{
"attestation": [ 4, 3, 2, 1, 0 ], "pubkey": [ 5, 6, 7, 8, 9 ] }' -vvv
http://127.0.0.1:3320/tee/register_attestation
  ```
  To inspect the database for the TEE attestations, run:
  ```
  $ PGPASSWORD='notsecurepassword' psql -h 127.0.0.1 -p 5432 -U postgres
  # \c zksync_local
  # SELECT * FROM tee_attestations;
  ```
- to submit TEE proof:
  ```
curl -X POST -H "Content-Type: application/json" --data-raw '{
"signature": [ 0, 1, 2, 3, 4 ], "pubkey": [ 5, 6, 7, 8, 9 ], "proof": [
10, 11, 12, 13, 14 ] }' -vvv http://127.0.0.1:3320/tee/submit_proofs/1
  ```
  To inspect the database for the TEE proofs, run:
  ```
  $ PGPASSWORD='notsecurepassword' psql -h 127.0.0.1 -p 5432 -U postgres
  # \c zksync_local
  # SELECT * FROM tee_proof_generation_details;
  ```

## Why ❔

This PR contributes to the effort outlined in the docs:
-
https://www.notion.so/matterlabs/2FA-for-zk-rollups-with-TEEs-a2266138bd554fda8846e898fef75131?pvs=4
-
https://www.notion.so/matterlabs/Proof-2F-verification-with-SGX-5fca2c619dd147938971cc00ae53e2b0?pvs=4

## 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`.
- [x] Spellcheck has been run via `zk spellcheck`.

)

## What ❔

update the nix flake

## Why ❔

to reproducibly build the zksync-era server and to develop easily with
the help of nix

## 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`.
- [x] Spellcheck has been run via `zk spellcheck`.

Signed-off-by: Harald Hoyer <[email protected]>

…s#2168)

## What ❔

Reworks `TxCache` for full nodes to look more like a mempool:

- Retains transactions from it when they are sent to the main node
- Gets rid of querying transactions from the main node in `TxProxy`.

## Why ❔

Right now, two transaction-related methods (`eth_getTransactionByHash`
and `zks_getTransactionDetails`) return data for pruned transactions.
Some other methods (e.g., `eth_getTransactionReceipt`) do not return
data for pruned transactions (i.e., return `null`). This looks
inconsistent; also may be wasteful w.r.t. calls to the main node.

## 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`.
- [x] Spellcheck has been run via `zk spellcheck`.

## What ❔

Reverts matter-labs#2179

## Why ❔

The new query turned out to be slower than the old one.

…ode (matter-labs#2213)

This PR deliberately only moves the code around without refactoring the
logic itself to decrease the risk of error. More PRs will most likely
follow

---------

Signed-off-by: tomg10 <[email protected]>

## What ❔

Adds metrics to state keeper for better observability

## 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`.
- [ ] Spellcheck has been run via `zk spellcheck`.

"%err" is just printing the leaf message which is not useful. "{err:#}"
prints the whole stack trace, as desired.

…abs#2217)

## What ❔

* Now prover_cli will also debug recursive circuits (for example
recursion tip)

## What ❔

Add metrics for better observability

## 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`.
- [ ] Spellcheck has been run via `zk spellcheck`.

…matter-labs#2218)

## What ❔

Update msg_address_doesnt_have_enough_money_prompt to:
`Address {address:?} doesn't have enough money to deploy contracts do
you want to try again?`

…r-labs#2212)

## What ❔

- When adding an ecosystem or new chain, localhost wallets should not be
allowed to be selected.

## Why ❔

- Localhost are intended for local development.
<!-- 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`.
- [x] Spellcheck has been run via `zk spellcheck`.

Co-authored-by: Matías Ignacio González <[email protected]>

…labs#2223)

## What ❔

+ Change `get_transaction_receipts` DAL method to fetch the contract
address from the `events` table.
+ Add integration test that checks we return the correct contract
address in the receipt of the transaction that deployed inner-outer
contract(e.g. contract that initializes another contract in its
constructor).

## Why ❔
The current approach(going to the `storage_logs` table to get the
contract address) is error-prone. The problem here is that we
deduplicate storage logs, which renders operation_number invalid. So,
the ordering is not correct, and we might return the incorrect deployed
address. This is important when one tx deploys a contract that
initializes another contract in the constructor(which means we deploy
several contracts here) - the user expects the "outer" contract address
but gets the inner.

## 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`.
- [ ] Spellcheck has been run via `zk spellcheck`.

Verification of an L1 batch, based on StoredBatchInfo. We extract the
hash of the last block of the transaction via merkle path from the
root_state (for batch n and n-1) and we recompute the rolling block hash
based on transactions in the payload. The verification is not perfect as
there are still some fields in payload for which we don't have a
commitment - we should address that later.

Verification will be used for syncing L1Batches over p2p network (not
implemented yet).

Also removed serde serialization from TransactionRequest which is unused
- we don't need to maintain encoding compatibility for it.

…2229)

## What ❔

Add metric for l2 block seal reason

## 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`.
- [ ] Spellcheck has been run via `zk spellcheck`.

Execute::factory_deps is set explicitly to null is storage, which breaks
parsing

This PR is done as a fix for boojnet outage.

TL;DR; of outage -- race condition caused by prover jobs moving from
'successful` state to `in_progress`/`in_gpu_proving`.

The PR addresses: 
- no job can move from successful state (considered final state)
- fix local development (contracts were pointing to 0.24.0 instead of
0.24.1) -- can be split to a different PR, if this is problematic.
- add table constraint -- again, can be split in different PR
- add checks for recursion_tip number of jobs (post outage check, should
not happen ever, but better to verify)

## What ❔

Update URLs pointing to our zksync Docs, most of them are outdated and
using an older URL for docs.zksync.io

## Why ❔

We've removed a lot of older redirects and URLs should reflect the up to
date URL for docs.

…abs#2232)

Rollforward matter-labs#2019 which was reverted by
matter-labs#2230

Made Execute json encoding super backward compatible.
The only change from the previous attempt is in
core/lib/types/src/execute.rs

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


##
[15.0.0](matter-labs/zksync-era@prover-v14.5.0...prover-v15.0.0)
(2024-06-14)


### ⚠ BREAKING CHANGES

* updated boojum and nightly rust compiler
([matter-labs#2126](matter-labs#2126))

### Features

* added debug_proof to prover_cli
([matter-labs#2052](matter-labs#2052))
([b1ad01b](matter-labs@b1ad01b))
* faster & cleaner VK generation
([matter-labs#2084](matter-labs#2084))
([89c8cac](matter-labs@89c8cac))
* **node:** Move some stuff around
([matter-labs#2151](matter-labs#2151))
([bad5a6c](matter-labs@bad5a6c))
* **object-store:** Allow caching object store objects locally
([matter-labs#2153](matter-labs#2153))
([6c6e65c](matter-labs@6c6e65c))
* **proof_data_handler:** add new endpoints to the TEE prover interface
API ([matter-labs#1993](matter-labs#1993))
([eca98cc](matter-labs@eca98cc))
* **prover:** Add file based config for fri prover gateway
([matter-labs#2150](matter-labs#2150))
([81ffc6a](matter-labs@81ffc6a))
* **prover:** file based configs for witness generator
([matter-labs#2161](matter-labs#2161))
([24b8f93](matter-labs@24b8f93))
* support debugging of recursive circuits in prover_cli
([matter-labs#2217](matter-labs#2217))
([7d2e12d](matter-labs@7d2e12d))
* updated boojum and nightly rust compiler
([matter-labs#2126](matter-labs#2126))
([9e39f13](matter-labs@9e39f13))
* verification of L1Batch witness (BFT-471) - attempt 2
([matter-labs#2232](matter-labs#2232))
([dbcf3c6](matter-labs@dbcf3c6))
* verification of L1Batch witness (BFT-471)
([matter-labs#2019](matter-labs#2019))
([6cc5455](matter-labs@6cc5455))


### Bug Fixes

* **config:** Split object stores
([matter-labs#2187](matter-labs#2187))
([9bcdabc](matter-labs@9bcdabc))
* **prover_cli:** Fix delete command
([matter-labs#2119](matter-labs#2119))
([214f981](matter-labs@214f981))
* **prover_cli:** Fix the issues with `home` path
([matter-labs#2104](matter-labs#2104))
([1e18af2](matter-labs@1e18af2))
* **prover:** config
([matter-labs#2165](matter-labs#2165))
([e5daf8e](matter-labs@e5daf8e))
* **prover:** Disallow state changes from successful
([matter-labs#2233](matter-labs#2233))
([2488a76](matter-labs@2488a76))
* Treat 502s and 503s as transient for GCS OS
([matter-labs#2202](matter-labs#2202))
([0a12c52](matter-labs@0a12c52))


### Reverts

* verification of L1Batch witness (BFT-471)
([matter-labs#2230](matter-labs#2230))
([227e101](matter-labs@227e101))

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

## What ❔

Removes some false positive clippy lints

## Why ❔

No longer false positive after the recent rustc 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`.
- [ ] Spellcheck has been run via `zk spellcheck`.

…batch` (matter-labs#2238)

## What ❔

Fixes a bug that is currently being observed on testnet

## Why ❔

Previously, on a fresh start, `last_ready_batch` could report incorrect
batch meaning no progress would be made as `last_ready_batch` would be
far less than `first_processed_batch`.

## 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`.
- [x] Spellcheck has been run via `zk spellcheck`.

…bs#2234)

## What ❔

Improves switching logic between Postgres and RocksDB for SK cache. With
these changes, RocksDB is guaranteed to be used if it's up to date when
it's opened.

## Why ❔

Previously, Postgres could be used after node start (primarily if
there's a pending L1 batch) even if RocksDB is up to date. This is
caused by potential delays when opening RocksDB. This behavior was
observed in the wild, e.g. for a mainnet full node with pruning enabled.

## 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`.
- [x] Spellcheck has been run via `zk spellcheck`.

## What ❔

Considers `reqwest::Error`s with "request" kind transient for the object
store logic.

## Why ❔

Similar to some other kinds of `reqwest::Error`s, not all "request"
errors are truly transient, but considering them as such is a safer
option.

## Checklist

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [x] Code has been formatted via `zk fmt` and `zk lint`.
- [x] Spellcheck has been run via `zk spellcheck`.

## What ❔

- Improves zk-toolbox integration tests CI adding missing arguments from
typescript core 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).
- [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`.
- [x] Spellcheck has been run via `zk spellcheck`.

## What ❔

Lowers function selector not found log level to debug

## Why ❔

It's non-actionable, harmless and spammy at the same time, for example:

![Screenshot 2024-06-17 at 5 10
15 PM](https://github.com/matter-labs/zksync-era/assets/7879134/90b831e1-6391-43da-94da-444a2b47030b)

## 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`.
- [ ] Spellcheck has been run via `zk spellcheck`.

Signed-off-by: tomg10 <[email protected]>

…atter-labs#2253)

## What ❔

Update `decommitted_code_hashes` in `prepare_to_decommit`

## Why ❔

Contract hashes that reached `prepare_to_decommit` should be returned by
`get_used_contracts`

## 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`.
- [ ] Spellcheck has been run via `zk spellcheck`.

## What ❔

Move the contract verifier struct to the separate lib crate.

## Why ❔

This logic can be used as a library. At lest, for example, now it's
needed for some compiler analysis tool.

## 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`.
- [ ] Spellcheck has been run via `zk spellcheck`.

## What ❔

Show balance of account if it's not enough for contract deployment

## 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`.
- [ ] Spellcheck has been run via `zk spellcheck`.

Signed-off-by: Danil <[email protected]>

…r-labs#2195)

## What ❔

Use `docker compose` instead of `docker-compose`

## Why ❔

The recommended command-line syntax is docker compose:

https://docs.docker.com/compose/migrate/#docker-compose-vs-docker-compose

…r-labs#2248)

This PR removes the fixes that were used to correct the circuit_id in
the node witness generator.

## 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`.
- [x] Spellcheck has been run via `zk spellcheck`.

…atter-labs#2255)

## What ❔

- `system-mode`, `force-evmla` flag are not provided for zksolc post
v1.5.0 compilations
- `solc-path` is not provided for system yul post v1.5.0 compilations 

## Why ❔

Changes in compiler interface

## 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`.
- [ ] Spellcheck has been run via `zk spellcheck`.

…atter-labs#2260)

## 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`.
- [ ] Spellcheck has been run via `zk spellcheck`.

Signed-off-by: Danil <[email protected]>

…s#2236)

This change introduces an invariant "If the transaction may have been
sent, then the sent_at_block is set". This way we never remove
eth_txs_history entries if the transaction may be included in block. The
downside is that we can't distinguish between not sent transaction and
one that has not been mined, but you can't have it both.
The next step is to remove "send_unsent_transactions" step, but it can't
be done in this PR as there might be transactions in db without
sent_at_block set

---------

Signed-off-by: tomg10 <[email protected]>

…labs#2266)

## What ❔

Adds a check that would prevent gas adjuster task from actually running
if there are no users of `GasAdjuster`.

## Why ❔

`GasAdjuster` is provided as a resource for anyone to use, but its
support task uses RPC (which has usage limits), so it doesn't make sense
to run it if nobody uses `GasAdjuster`.

## 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`.
- [ ] Spellcheck has been run via `zk spellcheck`.

## 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`.
- [ ] Spellcheck has been run via `zk spellcheck`.

## What ❔

this removes the need to call `nix develop` with the `--impure` flag

## Why ❔

This removes an inconvenience.

## 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.
- [x] Code has been formatted via `zk fmt` and `zk lint`.
- [ ] Spellcheck has been run via `zk spellcheck`.

Signed-off-by: Harald Hoyer <[email protected]>

)

## What ❔

* Exposing fair_pubdata_price in our block & batches API

## Why ❔

* This is crucial information for projects that need to replay our
transactions (for example era_test_node).
* Without this, they cannot compute the correct gas costs.