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
We are not supposed to report equivocation if they happen during initial sync, because they could be stale.
To check if we are in initial sync, we need something like block origin. Block origin tells about where did we import this block. It could be things like we got it in the initial sync, was broadcasted in the network, genesis block, got it from a file, etc.
The best place to add that would be in BlockData (
P1sar
added
C-complex
Complex changes across multiple modules. Possibly will require additional research.
P-low
this is mostly nice to have.
and removed
BABE
labels
Jan 15, 2024
Issue summary
We are not supposed to report equivocation if they happen during initial sync, because they could be stale.
To check if we are in initial sync, we need something like block origin. Block origin tells about where did we import this block. It could be things like we got it in the initial sync, was broadcasted in the network, genesis block, got it from a file, etc.
The best place to add that would be in BlockData (
gossamer/dot/types/block_data.go
Line 15 in 8320a2d
Once we have support for block origins, we can just add a condition such that if block origin is initial sync don't report equivocation.
Other information and links
Block Origin in substrate
The text was updated successfully, but these errors were encountered: