mirror of
https://github.com/nspcc-dev/neo-go.git
synced 2026-03-01 04:28:51 +00:00
Properly handle blocked/unblocked committee members in Neo cache #1300
Labels
No labels
I1
I2
I3
I4
S1
S2
S3
S4
U0
U1
U2
U3
U3
U4
blocked
bug
bug
cli
compiler
config
config
consensus
dependencies
discussion
documentation
enhancement
epic
feature
go
good first issue
help wanted
neotest
network
oracle
performance
question
rpc
security
smartcontract
task
task
task
test
vm
wallet
windows
windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nspcc-dev/neo-go#1300
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
@roman-khimov commented on GitHub (Jul 16, 2024):
I doubt it'll be noticeable in practice.