Skip to content

Conversation

@sidhujag
Copy link

@sidhujag sidhujag commented May 7, 2018

if masternode payent votes are not checked for signature validity before changing state of objects you can run into cases where for example an attacker can impersonate to block good votes for that block occur at little to no costs.

sidhujag added 2 commits May 6, 2018 23:13
if masternode payent votes are not checked for signature validity before changing state of objects you can run into cases where for example an attacker can impersonate to block good votes for that block occur at little to no costs.
fix synced check. Sorry was typing this up on my phone!
@UdjinM6
Copy link

UdjinM6 commented May 7, 2018

Makes sense, thanks!

However, swapping logic this way is probably a bit too much, I have an alternative solution which I believe should do the work but still mostly preserves the current flow. Pls see #2071.

@UdjinM6 UdjinM6 added this to the 12.3 milestone May 7, 2018
@UdjinM6 UdjinM6 added the bug label May 10, 2018
@UdjinM6
Copy link

UdjinM6 commented May 24, 2018

closing in fav of #2071

@UdjinM6 UdjinM6 closed this May 24, 2018
@UdjinM6 UdjinM6 removed this from the 12.3 milestone Mar 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants