You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
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.
The text was updated successfully, but these errors were encountered:
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
120
cctx at most, meaning the number of pending trackers will always be<= 120
, which is computationally a small list to iterate thru.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.
The text was updated successfully, but these errors were encountered: