-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
[BCI-3573] - Remove dependence on FinalityDepth in EVM TXM code #13794
Conversation
return fmt.Errorf("latest finalized head is not valid") | ||
} | ||
|
||
if latestFinalizedHead.BlockNumber() > head.BlockNumber() { |
There was a problem hiding this comment.
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.
Quality Gate passedIssues Measures |
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 ofFinalityDepth
.Acceptance Criteria
FinalityDepth
should be removed to enable the use of finality tags.FinalityDepth
from the EVM TXM codeNotes
Ticket:
Unblocks: