fix(db): use ru height for history indices & events instead of using the host block number #11
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…mber This will cause issues since we're not providing the correct number for changeset updates on the L2.
…st, where appropriate
This stack of pull requests is managed by Graphite. Learn more about stacking. |
prestwich
approved these changes
Aug 13, 2025
Evalir
changed the title
Evalir
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fix(db): update ru history indices instead of using the host block number
This will cause issues since we're not providing the correct number for changeset updates on the L2.
fix(db): Insert enters to
SignetEventstable with their RU heightchore(db): rename every ambiguous height parameter to ru height or host, where appropriate