fix: do not track l2_to_l1_logs block height on restart #445

montekki · 2024-04-24T09:40:09Z

What ❔

We are currently no longer track L2ToL1Logs from L1 (removed in #398 ), so no need to try to start from the last seen block for those events

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 cargo fmt.

🤖 I have created a release *beep* *boop* --- ## [0.9.0](v0.8.0...v0.9.0) (2024-04-24) ### Features * Adds filtering of erc20 tokens by their l2 address ([#447](#447)) ([09f8810](09f8810)) ### Bug Fixes * do not track l2_to_l1_logs block height on restart ([#445](#445)) ([90655c1](90655c1)) --- 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: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>

fix: do not track l2_to_l1_logs block height on restart

cd9776d

montekki requested review from AnastasiiaVashchuk, Deniallugo and haraldh as code owners April 24, 2024 09:40

AnastasiiaVashchuk approved these changes Apr 24, 2024

View reviewed changes

montekki merged commit 90655c1 into main Apr 24, 2024
9 checks passed

montekki deleted the fvs-start-from-l1-block branch April 24, 2024 09:48

release-please bot mentioned this pull request Apr 24, 2024

chore(main): release 0.9.0 #446

Merged