Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Merged
merged 1 commit into from
Apr 24, 2024

Conversation

montekki
Copy link
Contributor

@montekki montekki commented Apr 24, 2024

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

Why ❔

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

@montekki montekki merged commit 90655c1 into main Apr 24, 2024
9 checks passed
@montekki montekki deleted the fvs-start-from-l1-block branch April 24, 2024 09:48
montekki pushed a commit that referenced this pull request Apr 24, 2024
🤖 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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants