Quote from: Lichtsucher on March 18, 2019, 12:38:39 PM

Quote from: bible_pay on March 18, 2019, 11:52:49 AM

Quote from: capulo on March 18, 2019, 06:59:52 AM

Quote from: bible_pay on March 17, 2019, 02:45:29 PM

Quote from: capulo on March 17, 2019, 02:26:57 PM

hash1 is not affected in solo or pool mining, sum of wallets hash power is +- still same

Please explain in more detail; I thought you told Dave there was a 500% edge?

Edit: I only know of one thing, HPS (not hash1 or hash2 anymore, I think we got rid of that a year ago).

i mean hash1 in pool or hps in solo (i think it is same number) is not affected by multiwallets
if you run 2 wallets, it just split to ~half and so

only hash2 in pool is affected by multiwallets

Thanks, I havent looked at it yet but will be looking at this stuff today and PMs etc.

In this case Purepool should not be affected, as it only counts the valid shares of the users. No HPS2 tricks or anythink like that

Just to clarify your post to everyone else: HPS2 was not a TRICK. HPS2 was just a reading that we passed on to the user of their total clients HPS gathered from the sum of their wallets transmissions to Us. We always paid off of HPS in the pool.

So to re-state what Ive said all along:

Pool.biblepay used to have two columns: Your HPS (for share assessment) and your HPS2 (that matched the clients total HPS). It was useful to see if your miners matched the pool thats all it was. No tricks, nor has there ever been tricks!

I challenge any Theymos's, any naysayers, anyone who ever points the finger of .01 BBP of corruption on BiblePay or ME, that you will be rebuked and proven wrong in Jesus Name!

Long live Biblepay, and its integrity!