Can you explain shares in metric terms
http://lmgtfy.com/?q=what+is+a+share+in+crypto+mining
Topic: Faking Hash Rates.. (Read 212 times)
In the following code segment from blake2s.cu (ccminer source code - cuda C)
uint32_t vhashcpu[8];
uint32_t nonce = sph_bswap32(resNonces[1]);
be32enc(&endiandata[19], nonce);
blake2s_hash(vhashcpu, endiandata);
*hashes_done = pdata[19] - first_nonce + throughput;
How do pool miners prevent coders from modifying the source code and recompiling ccminer so they fake the hash count and get an unequal share of the winning pools?? This would apply in pretty much all the algos...?
uint32_t vhashcpu[8];
uint32_t nonce = sph_bswap32(resNonces[1]);
be32enc(&endiandata[19], nonce);
blake2s_hash(vhashcpu, endiandata);
*hashes_done = pdata[19] - first_nonce + throughput;
How do pool miners prevent coders from modifying the source code and recompiling ccminer so they fake the hash count and get an unequal share of the winning pools?? This would apply in pretty much all the algos...?
Because miners don't get paid for their hash rate, they get paid for submitting valid shares.
However, unscrupulous miner authors could tweak that value and voila! my miner is 30% better than stock, send me phat ETHs!!!
If you tell someone you are giving them a $10 bill, then hand them a $5 they will do their own verification by looking at the bill and realizing something isnt right. The pool isnt just going to accept whatever razndom share number people want to throw at it.
Can you explain shares in metric terms
How do pool miners prevent coders from modifying the source code and recompiling ccminer so they fake the hash count and get an unequal share of the winning pools?? This would apply in pretty much all the algos...?
Pools pay per the amount of shares you submit. They have no idea what the hash rate of your device nor what your software is reporting to you, nor do they care.
This does not pertain to all algorithms. Nobody mines Bitcoin with GPU's anymore and when we did we would never use an nVidia GPU as it would have been a waste of electricity.
You do know that pools verify the share sent in, right? And subsequently calculate the share rate to the pool... 
In the following code segment from blake2s.cu (ccminer source code - cuda C)
uint32_t vhashcpu[8];
uint32_t nonce = sph_bswap32(resNonces[1]);
be32enc(&endiandata[19], nonce);
blake2s_hash(vhashcpu, endiandata);
*hashes_done = pdata[19] - first_nonce + throughput;
How do pool miners prevent coders from modifying the source code and recompiling ccminer so they fake the hash count and get an unequal share of the winning pools?? This would apply in pretty much all the algos...?
uint32_t vhashcpu[8];
uint32_t nonce = sph_bswap32(resNonces[1]);
be32enc(&endiandata[19], nonce);
blake2s_hash(vhashcpu, endiandata);
*hashes_done = pdata[19] - first_nonce + throughput;
How do pool miners prevent coders from modifying the source code and recompiling ccminer so they fake the hash count and get an unequal share of the winning pools?? This would apply in pretty much all the algos...?
Jump to: