diff options
author | Mission Liao <mission.liao@dexon.org> | 2019-03-08 15:54:15 +0800 |
---|---|---|
committer | GitHub <noreply@github.com> | 2019-03-08 15:54:15 +0800 |
commit | c4e3025d230dbbab64a2f286835a65d797260ec9 (patch) | |
tree | 99f4c0c207f95c9decf7b6626d9e41743719c5d7 /core/test/marshaller.go | |
parent | cb2dc00068227b9544031c085b8f17124773256c (diff) | |
download | tangerine-consensus-c4e3025d230dbbab64a2f286835a65d797260ec9.tar tangerine-consensus-c4e3025d230dbbab64a2f286835a65d797260ec9.tar.gz tangerine-consensus-c4e3025d230dbbab64a2f286835a65d797260ec9.tar.bz2 tangerine-consensus-c4e3025d230dbbab64a2f286835a65d797260ec9.tar.lz tangerine-consensus-c4e3025d230dbbab64a2f286835a65d797260ec9.tar.xz tangerine-consensus-c4e3025d230dbbab64a2f286835a65d797260ec9.tar.zst tangerine-consensus-c4e3025d230dbbab64a2f286835a65d797260ec9.zip |
syncer: avoid attacked by older AgreementResult when syncing (#471)
One possible attack for syncer is:
- byzantine nodes periodically broadcast some very
old types.AgreementResults.
- If some syncer receive those
types.AgreementResult, they might synced
directly while still fall behind other nodes.
A quick workaround is ignore
types.AgreementResults older than the chain tip
when creating the syncer.Consensus instance.
Diffstat (limited to 'core/test/marshaller.go')
0 files changed, 0 insertions, 0 deletions