From 339e45035e85eba7d60b533221be92ce78643705 Mon Sep 17 00:00:00 2001
From: EmilLuta <EmilLuta@users.noreply.github.com>
Date: Tue, 28 Nov 2023 19:53:30 +0100
Subject: [PATCH] fix: Update comments post-hotfix (#556)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

## 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>
Co-authored-by: Danil <deniallugo@gmail.com>
---
 core/lib/zksync_core/src/sync_layer/batch_status_updater.rs | 3 ---
 deny.toml                                                   | 1 +
 2 files changed, 1 insertion(+), 3 deletions(-)

diff --git a/core/lib/zksync_core/src/sync_layer/batch_status_updater.rs b/core/lib/zksync_core/src/sync_layer/batch_status_updater.rs
index bbf1e45c310..8e7ebe7a985 100644
--- a/core/lib/zksync_core/src/sync_layer/batch_status_updater.rs
+++ b/core/lib/zksync_core/src/sync_layer/batch_status_updater.rs
@@ -267,9 +267,6 @@ impl BatchStatusUpdater {
     }
 
     /// Inserts the provided status changes into the database.
-    /// This method is not transactional, so it can save only a part of the changes, which is fine:
-    /// after the restart the updater will continue from the last saved state.
-    ///
     /// The status changes are applied to the database by inserting bogus confirmed transactions (with
     /// some fields missing/substituted) only to satisfy API needs; this component doesn't expect the updated
     /// tables to be ever accessed by the `eth_sender` module.
diff --git a/deny.toml b/deny.toml
index b50b165b72f..7fa3c835088 100644
--- a/deny.toml
+++ b/deny.toml
@@ -8,6 +8,7 @@ yanked = "warn"
 notice = "warn"
 ignore = [
     "RUSTSEC-2023-0018",
+    "RUSTSEC-2023-0071"
 ]
 
 [licenses]