Gil Danziger

This issue is a bit old so we should get to a resolution here (implement soon / schedule to a future milestone / close). I like the general idea of...

@frolosofsky , to make it clear when looking at the history of #852 and this issue and make sure we converge to clear rules when to slash, we can't see...

Good catch! To be implemented/verified with the help of @amiller. Who disclosed disk attacks in some PoS currencies

Some fixes / responses to the vulnerabilities: - https://www.dropbox.com/s/nw6uipvjxo0ujrs/NLC2-PoS-Vulnerabilities-20190124.pdf?dl=0 - https://github.com/Galilel-Project/galilel/commit/1fe39e9ca036f915f27322dfb575da78c0163984

Ok thanks for looking further, can you also change the issue title to reflect the more precise problem?

Good catch, in general and by syncing few times, I'd strongly consider limiting the commits based sync to the fast sync use case only. There it's essential to iterate over...

In general fo security issues, I suggest to create a branch with a functional test in an active PoSv3 coin repository (Qtum is a good candidate, maybe Particl) as @amiller...

https://medium.com/@lukedashjr/cve-2018-20587-advisory-and-full-disclosure-a3105551e78b > 2018–12–30 A complex and experimental solution to fix both issues is released in Bitcoin Knots 0.17.1.knots20181229. We can simply track on how the issue is eventually handled in...

I do think it's a serious issue since it can affect votes being discarded for no reason, they are indeed unique transactions and should be treated this way. totally makes...

If that's the current behaviour and we just assumed it's different, is it really a bug?