Quote from: iDisturbia on May 20, 2020, 08:50:15 PM

Quote from: kerney666 on May 20, 2020, 01:56:02 PM

Quote from: iDisturbia on May 20, 2020, 12:53:54 PM

Quote from: kerney666 on May 20, 2020, 11:19:12 AM

For miners that don't fully trust the displayed hashrate or that the communicated dev fee is correct, I would argue that the best way to verify poolside/dev fee hashrate is with fake pool hacks, much like the one we built ourselves for ethash, available on my github. It sets a low diff, the miner you want to test submits many many more shares compared to a normal pool, and after maybe 12h you have a very accurate picture of the "poolside" hashrate of the miner you're testing because you'll have submitted 500,000 shares by then and get a much much more accurate data point than looking at a 6h or 24h average on some pool for 1000 submitted shares (which really means nothing tbh).

I had better idea to prove my findings .... tested the hacked releases of 2 VERY popular ETH mining softwares and noticed my hash rates went up almost double compare with using the original ones!

Shocking, eh!!

Yeah, sounds a little weird tbh. Therefore, I'm happy to make you a public bet for 1 BTC with a known escrow that you're full of shit, care to take me up on it? You provide your magic hacked software that produces 58-62 MH/s on a Polaris card or 95-100 MH/s on a Vega 56/64, hashrate is then verified statistically by a 3rd party for a test with approx 1 million submitted shares to get the bounds on the Poisson distribution within reasonable bounds, then the escrow pays out? Would love to make an easy 1 BTC.

Save your 1 BTC ... just share the code in that source folder you created in github!
[/quote]

Nobody owes you anything.