You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found the same issue was raised earlier also but I fail to see a fix to it:
"
Hopefully on here we can figure this out.
We need to make it so that block is just a hash and does not relate to a mining address at all.
Then once a miner finds a valid block, we get masternodes to confirm that a specific address mined it. (the miner submits his address to the masternodes with the block data and the masternodes signs a message, and as a reward it gets 30% of the blockreward)
This means that when a pool's miners finds a block, the block finder can swap out the pool's address with his address when he submits it to the masternodes.
This means that no one will know if he was mining as part of the pool or not because the submitted block has no information that relates it to the pool.
Can it work or not? Don't give up, I'm convinced we can fix this.
guys ... whats stopping me from changing the code and submitting a different miner hash every time?
The text was updated successfully, but these errors were encountered: