Closed dapi closed 5 years ago
@dapi/z this project will fix the problem faster if you donate a few dollars to it; just click here and pay via Stripe, it's very fast, convenient and appreciated; thanks a lot!
@dapi can you please explain what exactly will be done by the fraudulent node in order to compromise our protocol?
Change node’s local time into the future and spend whole time of shifted period to calculate score’s value instead of expected 24 hours.
@dapi I quote the White Paper: "The score is only valid when the starting time is earlier than the current time, but not earlier than 24 hours ago." Thus, every client, which will see your score, will just ignore it as "invalid" if your time is ahead in the future, comparing to the local time of the client.
@dapi This problem is already fixed, I believe. However, if you see it again, please don't hesitate to create a new issue. Thanks for your contribution!
Job gh:zold-io/papers#68
is not assigned, can't get performer
This job is not in scope
This problem is already fixed, I believe. However, if you see it again, please don't hesitate to create a new issue. Thanks for your contribution!
I'm not sure. I believe you must not use remote timestamp to check or trust given score in any cases.
That is why we can’t decide is score still alive or not and can’t really know how long has it been calculating.
Possible solution is to have something
trusted network time
, to compare received score time with it.