Look before you start reading, i'm sorry. its gonna get heated, im gonna get mad, please be an adult and dont take it personally. I hate bad math, its my problem, its one of those pet peeves that just, ooooooh....right up the freaking wall! You're not an idiot, mistakes happen, blah blah blah.
that being said, jesus freaking christ CMON!
Jamstruth said:
If its a 24 digit code the possibles are 10 to the 24th
thats only true for number-only codes, and only in base ten.
ugh, my brain.
if it's a 24
DIGIT code, each digit takes up two
BYTES, or 16
BITS, which would result in a 384 bit code. i just dont think this is right.
asiekierka said:
Yes, we don't know WHERE is the code.
There are 2^127 combinations TBH.
We know the first bit though (loopy!) so that makes it 50% smaller
yeah im pretty sure this information is right. it should be a 256 bit public key, and assuming loopy isnt screwing with everyone trying to keep people from getting the key at all. did he EVER tell anyone why he never released?
QUOTE(CrimsoniteX @ Feb 4 2010, 02:37 PM)
I I did my math correctly...
If we get 1000 people to run this program at an average of 30,000 keys per second, that comes to 1,800,000,000 keys per second or 108,000,000,000 per hour. There are (10 to the 24th) possible keys, which is 1,000,000,000,000,000,000,000,000. That means it will still take about 9.25925926 × (10 to the 12th) hours, or
1,056,993,070 years to check every combination.
I hope it's running random keys, and not sequential xD
oh GOD your math! first off,
30,000 times
1,000 equals
30,000,000, not
1,800,000,000, what the hell is the matter with you?!?!
1,800,000,000 keys per minute, YES, but not per second. ok, lets pretend its
1,800,000,000 keys per second, that times
60 seconds per minute, times
60 minutes per hour, (just just times
3600) is
6,480,000,000,000, NOT
108,000,000,000 per hour, which you did actually get
RIGHT (good job)! lets continue pointing out your flaws...
there are not 10^24th possible keys, this is wrong, see above. the rest of your calculations are done with the number of keys wrong so no matter what calculation you actually did, even if by some miracle it was the right one, would still be wrong. heres how it should look. im gonna use acronyms KPS, KPH, KPY, etc, its keys per, im sure you can keep up.
1,000 people @
30,000 KPS =
30,000,000 KPS =
1,800,000,000 KPM =
108,000,000,000 KPH =
2,592,000,000,000 KPD =
946,080,000,000,000 KPY
2^127 = 1.7014118346046923173168730371588 x 10^38, which divided by 946,080,000,000,000 KPY, equals a MAXIMUM of
179,838,051,180,100,236,482,842.15258317 years at that rate.
doubling the KPS obviously cuts this time in half, so i say we shoot instead for 1,000,000 people running at 30,000 KPS, then it will only take 179,838,051,180,100,236,482.84215258317 years instead
thank you for your patience, now you know math.