Skip to content

Withdrawal queue checkpoint hint zero#1655

Open
Dev-In-Crypt wants to merge 3 commits intolidofinance:masterfrom
Dev-In-Crypt:bugfix/withdrawalqueue-checkpointhint-zero
Open

Withdrawal queue checkpoint hint zero#1655
Dev-In-Crypt wants to merge 3 commits intolidofinance:masterfrom
Dev-In-Crypt:bugfix/withdrawalqueue-checkpointhint-zero

Conversation

@Dev-In-Crypt
Copy link

Context

This affects findCheckpointHints, which is used to build hint indices for batches of withdrawal request IDs. The function is expected to work with lists that can contain a mix of finalized and unfinalized requests.

Problem

When _findCheckpointHint returns 0 for an ID (common for unfinalized requests), the previous logic still assigned _firstIndex = 0. On the next iterations this can lead to a revert inside _findCheckpointHint because it receives _start == 0. This breaks processing for mixed finalized/unfinalized lists even when the request IDs are properly sorted.

Solution

Update findCheckpointHints to only advance _firstIndex when a non zero hint is returned. This preserves a valid search start index across the loop and prevents _start == 0 reverts while keeping the existing sorted ID validation intact.

@Dev-In-Crypt Dev-In-Crypt requested a review from a team as a code owner February 5, 2026 19:55
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.

1 participant