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

[BCI-3573] - Remove dependence on FinalityDepth in EVM TXM code #13794

Merged
merged 55 commits into from
Aug 9, 2024

Conversation

Farber98
Copy link
Contributor

@Farber98 Farber98 commented Jul 9, 2024

Description

Parts of the EVM TXM code still relies on FinalityDepth regardless if the chain is enabled to use finality tags. Through this PR we are updating the code to utilize the head tracker’s latest finalized block instead of FinalityDepth.

Acceptance Criteria

  • All direct references to FinalityDepth should be removed to enable the use of finality tags.
  • Remove all instances of FinalityDepth from the EVM TXM code

Notes

  • Please see comments

Ticket:

Unblocks:

common/txmgr/confirmer.go Outdated Show resolved Hide resolved
common/txmgr/confirmer.go Outdated Show resolved Hide resolved
silaslenihan
silaslenihan previously approved these changes Aug 6, 2024
return fmt.Errorf("latest finalized head is not valid")
}

if latestFinalizedHead.BlockNumber() > head.BlockNumber() {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: Don't think this log is needed.
The HeadTracker should never send finalzied blocks that are newer than current blocks.
This is likely a clear case of TXM panicking or throwing critical errors. But this should already been handled at HT layer.

@prashantkumar1982 prashantkumar1982 added this pull request to the merge queue Aug 8, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Aug 8, 2024
@prashantkumar1982 prashantkumar1982 added this pull request to the merge queue Aug 8, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Aug 8, 2024
@prashantkumar1982 prashantkumar1982 added this pull request to the merge queue Aug 9, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Aug 9, 2024
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.

7 participants