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 #13755

Conversation

Farber98
Copy link
Contributor

@Farber98 Farber98 commented Jul 3, 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

Tickets:

Requires:

Unblocks:

amit-momin and others added 23 commits June 20, 2024 12:36
@Farber98 Farber98 changed the base branch from develop to BCI-3486-implement-finality-check-for-the-get-transaction-status-method July 4, 2024 15:06
@@ -1474,7 +1469,7 @@ FROM (
FOR UPDATE OF e1
) e0
WHERE e0.id = evm.txes.id
RETURNING e0.id, e0.nonce`, ErrCouldNotGetReceipt, cutoff, chainID.String())
RETURNING e0.id, e0.nonce`, ErrCouldNotGetReceipt, latestFinalizedBlockNum, chainID.String())
Copy link
Contributor Author

@Farber98 Farber98 Jul 4, 2024

Choose a reason for hiding this comment

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

Do we want HAVING max(evm.tx_attempts.broadcast_before_block_num) < $2 (latestFinalizedBlockNum) to be inclusive now?

@amit-momin amit-momin force-pushed the BCI-3486-implement-finality-check-for-the-get-transaction-status-method branch from 5b18016 to 911d342 Compare July 9, 2024 02:09
@Farber98 Farber98 closed this Jul 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.

2 participants