Properly handle blocked/unblocked committee members in Neo cache #1300

Open
opened 2025-12-28 17:15:57 +00:00 by sami · 1 comment
Owner

Originally created by @AnnaShaleva on GitHub (May 20, 2024).

Current Behavior

Neo committee and validators cache is being updated only if vote-related or transfer-related transactions were included into block. We don't recalculate cache if Policy blocked/unblocked some accounts.

Expected Behavior

We should recalculate Neo cache wrt Policy changes. Cache won't be as optimized as it is now, but it will work properly with this change.

This bug is not critical since committee members blocking/unblocking is not a hot path on public networks.

Originally created by @AnnaShaleva on GitHub (May 20, 2024). ## Current Behavior Neo committee and validators cache is being updated only if vote-related or transfer-related transactions were included into block. We don't recalculate cache if Policy blocked/unblocked some accounts. ## Expected Behavior We should recalculate Neo cache wrt Policy changes. Cache won't be as optimized as it is now, but it will work properly with this change. This bug is not critical since committee members blocking/unblocking is not a hot path on public networks.
Author
Owner

@roman-khimov commented on GitHub (Jul 16, 2024):

Cache won't be as optimized as it is now

I doubt it'll be noticeable in practice.

@roman-khimov commented on GitHub (Jul 16, 2024): > Cache won't be as optimized as it is now I doubt it'll be noticeable in practice.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nspcc-dev/neo-go#1300
No description provided.