Some users are attempting to modify the following code to maximize their gains, and these users can see the corresponding rewards. For the fairness of everyone, please cancel these users’ gains.
Such proofs will be rejected by the network even if it shows up locally.
2 Likes
Like @abc said, if they try to redeem rewards they will find that they have wasted time and money getting proofs that are invalid
3 Likes
Genius hack. Very l33t. 
1 Like
yeah, that won’t work at all 
1 Like
This behavior should be considered cheating or sybil, and the corresponding rewards should be revoked.
1 Like
I agree with your viewpoint
1 Like
Why is my node’s seniority score 0? this node has been runing for at least a month
Signature check passed
Stasis lock not yet released.
.config is not an absolute path
Effective seniority score: 0
Why?
What if they modified the code just to make it more efficient?
Ideally, they would share that code with the open source community to make the network more efficient for everyone, but it wouldn’t directly hurt anyone to profit from an optimization.
In this case, they’re clearly trying to “game the system”, but other cases may not be so cut and dry.
This piece of code modifies the initial value of increment to increase rewards, which is considered a form of cheating. In my opinion, such shortcuts are all cheating.
Anyone can change the code. Nature of being open source. However, just because you can make changes doesn’t mean those changes will have an affect! In this case the network will reject the proofs that are generated by the modified node binary because there are network-level (server-side) protections in place to prevent this and other attempts at cheating.
Note My client-side and server-side analogy may not be entirely correct for web3, but it’s how it works in the web2 world and should get the point across 
1 Like