Cedric
Cedric
Thank you for your response! I didn't notice that, feel free to close it! > This is a valid but known issue that we already have a pending fix for...
Hi @raychu86 , I've reviewed this pr, and I believe it can prevent this attack.
Hi @raychu86 , The attack doesn't work only for validators which is syncing. In fact, it works for **ALL SYNCED** validators. The attacker will always generate block which height is...
Validator will always get block locators when perform_handshake, however, there's no need to do it when peer is a Prover or a Client，right？ https://github.com/AleoHQ/snarkOS/pull/2147
> > Validator will always get block locators when perform_handshake, however, there's no need to do it when peer is a Prover or a Client，right？ #2147 > > I've answered...
> `Sync` already ensures that the client/prover will only request a `PuzzleRequest` with a specific set of peers if it deems them to be further on the canonical chain. Additionally,...
Prover/Client will not process BlockRequest and BlockResponse now, and never update itself's canon chain, If I'm not mistaken, It only update_peer_locators in processing Ping. Please check this logic, thanks.
@howardwu
> All right. Not as you say "drop in height isn't great", it's even worse now, more frequent, greater height. Scoring mechanism is needed. There's no reward for Provers to...