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

Zetaclient should be able to remove the timeout logic when iterating thru EVM chain outtx trackers #1970

Closed
ws4charlie opened this issue Apr 1, 2024 · 0 comments · Fixed by #1984
Assignees
Labels
zetaclient Issues related to ZetaClient

Comments

@ws4charlie
Copy link
Contributor

Describe the Issue
Zetaclient still has the legacy timeout logic in function ObserveOutTx when it iterates thru the outtx tracker list. We should be able to get rid of this legacy logic which was introduced in hotfix patch to deal with overwhelming number of trackers.

The reason is that the EVM chain won't face overwhelming number of trackers in the latest implementation for that

  1. Zetaclient looks ahead120 cctx at most, meaning the number of pending trackers will always be <= 120, which is computationally a small list to iterate thru.
  2. The latest zetacore, after mainnet, is able to effectively block submission of garbage trackers (for instance, the reported tracker already has a finalized cctx; only <= 2 hashes can be submitted for a same pending cctx).

Expected Outcome
Zetaclient should iterate thru all trackers regardless of timeout.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment