02-20-2017, 09:46 PM
(This post was last modified: 02-20-2017, 09:59 PM by tom.schneider.)
Thanks for your response, of course this makes sense for a single hash but in this case i generated multiple hashes
with unique cipher and plain evenly distributed over the keyspace, and the speed was the same, i can see that the progress max is going up. i guess the time estimate is just on its upper end. or is it a estimation when the next hash will be complete?
What i don't get is:
Hashes 3: Progress.........: 759169024/216172782113783808 (0.00%)
Hashes 100: Progress.........: 654311424/7205759403792793600 (0.00%)
Hashes 50000: Progress.........: 654311424/5764607523034234880 (0.00%)
Hashes 1000000: Progress.........: 645922816/4611686018427387904 (0.00%) <- Overflow ???
So is this mean that blocks with differentsh. It does not matter if you are willing to pay. plain text will be checked consecutive adding up to the overall work.
So basically like generate keys, encrypt unique plain text, check against bloom filter or else.
for all hashes before going to the next?
with unique cipher and plain evenly distributed over the keyspace, and the speed was the same, i can see that the progress max is going up. i guess the time estimate is just on its upper end. or is it a estimation when the next hash will be complete?
What i don't get is:
Hashes 3: Progress.........: 759169024/216172782113783808 (0.00%)
Hashes 100: Progress.........: 654311424/7205759403792793600 (0.00%)
Hashes 50000: Progress.........: 654311424/5764607523034234880 (0.00%)
Hashes 1000000: Progress.........: 645922816/4611686018427387904 (0.00%) <- Overflow ???
So is this mean that blocks with differentsh. It does not matter if you are willing to pay. plain text will be checked consecutive adding up to the overall work.
So basically like generate keys, encrypt unique plain text, check against bloom filter or else.
for all hashes before going to the next?