how to proove wheter a worker has actually finished a job?
JanCantCode opened this issue · 5 comments
as this question probaply already tells, i dont have a good idea of mining pools and stuff.
so from my understanding, a job is essentially a task for a miner in the pool to hash a transaction in combination with all nonces from value x to value y, and returns only correct hashs. is this understanding even right in the first place? but my main question is, how does the proxy know, that the miner has actually finished the job work, and doesnt just pretend that he did.
if i am having any wrong expectations in the first place, please go ahead and correct me, i am fairly new to crypto
Proxy doesn't know and doesn't check it. The pool you connect to checks all your shares.
Proxy doesn't know and doesn't check it. The pool you connect to checks all your shares.
and what concept is used by the pool to make that sure?
Pool calculates proof of work (RandomX hash) of the submitted job and checks that it meets required difficulty.
Pool calculates proof of work (RandomX hash) of the submitted job and checks that it meets required difficulty.
and what exactly is submitted?
and checks that it meets required difficulty.
I am interested in that as well. I have an issue where I suspect hashrates calculated to be far too high. However shares with the maximum possibility the pool offers (4.000.000) are still accepted, only occasionally being rejected. This leads to a calculation of hashrate which is impossible. I am using P2Pool and there should be shares submitted basically every 2 to 3 minutes which just is not the case, therefore the hashrate has to be fake.