Author

Topic: Bitcoin puzzle transaction ~32 BTC prize to who solves it - page 242. (Read 229433 times)

jr. member
Activity: 49
Merit: 1

Speed test with 4 cores:   [ Speed : 301444.62 Keys/s ]
the calculation takes place one after the other, not at the same time, which would take time...

I can get the same speed with only one core using my code

..it depends on the CPU used... I have 3GHz/core... be happy, the faster the better!
but the forum is not for saying "who can run faster"

it's about innovation, ideas to shorten the search... new ways in the programming..
jr. member
Activity: 49
Merit: 1
I have 16 available cores each capable of 4.5 GHz but I get only 1,186,383.53 Keys/s when running your code. When I check utilization in top or htop I see there are only about 4 cores utilized at 100% but even then I would have expected higher rate. Anything I'm missing ?

I'm using secp256k1 from iceland2k14. When I manually set core for instance to "15" it utilizes 15 cores, but I would have expected that the cpu_count enumeration had worked. Seems it didn't, despite that ... With 15 cores I can achieve 2003121.42 Keys/s that is 2 MKey/s. You said you're achieving 600 MKey/s, how do you do that with CPU only? Wouldn't it be better to utilize GPU for such things?

You are confusing something, I achieve the 600 MKeys/s with the GPU and not with this code...
for this code a CPU is working with 3 GHz/core..
hero member
Activity: 862
Merit: 662

Speed test with 4 cores:   [ Speed : 301444.62 Keys/s ]
the calculation takes place one after the other, not at the same time, which would take time...

I can get the same speed with only one core using my code
hero member
Activity: 630
Merit: 731
Bitcoin g33k
I have 16 available cores each capable of 4.5 GHz but I get only 1,186,383.53 Keys/s when running your code. When I check utilization in top or htop I see there are only about 4 cores utilized at 100% but even then I would have expected higher rate. Anything I'm missing ?

I'm using secp256k1 from iceland2k14. When I manually set core for instance to "15" it utilizes 15 cores, but I would have expected that the cpu_count enumeration had worked. Seems it didn't, despite that ... With 15 cores I can achieve 2003121.42 Keys/s that is 2 MKey/s. You said you're achieving 600 MKey/s, how do you do that with CPU only? Wouldn't it be better to utilize GPU for such things?
member
Activity: 185
Merit: 15
Two things you should never abandon: Family & BTC
WIF-Key based scanner for the 66 bit range..
 ...happy Hunting!! Wink

your code is the most inefficient way to search the puzzle.

Your way:
WIF->Private Key->Publickey->Sha256->rmd160->Address.


Why not only?

Publickey->Sha256->rmd160

In this way you avoid some steps that need a lot of calculation.

Regards!



simple answer...
the area that is random consists of only 6 letters from the Wif-key...
and the secp256k1 from (ice) is super fast...

Speed test with 4 cores:   [ Speed : 301444.62 Keys/s ]
the calculation takes place one after the other, not at the same time, which would take time...
Using python or any high level language to do heavy computations is trouble .. cracking is better coded with c/cpp/golang/java .. but thank you a lot for sharing your code
hero member
Activity: 862
Merit: 662
WIF-Key based scanner for the 66 bit range..
 ...happy Hunting!! Wink

your code is the most inefficient way to search the puzzle.

Your way:
WIF->Private Key->Publickey->Sha256->rmd160->Address.


Why not only?

Publickey->Sha256->rmd160

In this way you avoid some steps that need a lot of calculation.

Regards!

newbie
Activity: 25
Merit: 0
http://www.ttdsales.com/66bit/index.php  doesn't even register my RTX3060ti hash running for over an hour so yeah not a great option!
member
Activity: 185
Merit: 15
Two things you should never abandon: Family & BTC
I wonder if anyone here has ever found any public key with pubhunt???

I think you are right someone lucky will eventually find #66 cause the way I see it is the last 12 characters can easily be brute forced, less than a day with 3 RTX GPUs for entire range

the very first character is a 2 or 3 take your pick, then its really the next 4 characters after that needs to be guessed. The probability of someone being lucky is high but most people give up after a few weeks I reckon.

I have searched a number of ranges I know the key is not in, If there was a place people were willing to collab I think it would be found quicker but I guess everyone just solo

If 3 RTX 3090 can finish 12 digits in an hour, such range and power against it would narrow down the entire range search time to 15 years:

16^4 = 65536 ranges to search
This is if you only pick 2 or 3 (the first significant bit)
Then if you choose to search both:
65536 x 2 = 131072 ranges to search
As each range would take one hour to finish .. we now need 131072 hours to search the entire range
131072 ÷ 24 hours = 5461 days
5461 ÷ 365 days = 14.9 years
hero member
Activity: 630
Merit: 731
Bitcoin g33k
member
Activity: 185
Merit: 15
Two things you should never abandon: Family & BTC
I have searched a number of ranges I know the key is not in, If there was a place people were willing to collab I think it would be found quicker but I guess everyone just solo

http://www.ttdsales.com/66bit/login.php
This site was created to collectively solve bit 66 of the Bitcoin puzzle challenge.

Like the Large Bitcoin Collider .. still 16 billion keys/s seem too small for a collab work .. need many more people to join .. problem with such method is it has diminishing return:

- Too few ppl in the collab would mean collab is not worth it compared to solo.
- Many ppl in the collab would mean your cut of the prize is very minimal compared to the resources/power you've contributed to that collab search .. the more ppl joining, the more the chance of solving the key but at the same time the less each one receives as a reward.

 i think I'm gonna stick to Solo searching .. who knows
newbie
Activity: 25
Merit: 0
Ok wow I've never heard of this http://www.ttdsales.com/66bit/login.php

I have signed up and will add some hash to it, hopefully they will honestly distribute the btc if found though!
member
Activity: 196
Merit: 67
I have searched a number of ranges I know the key is not in, If there was a place people were willing to collab I think it would be found quicker but I guess everyone just solo

http://www.ttdsales.com/66bit/login.php
This site was created to collectively solve bit 66 of the Bitcoin puzzle challenge.
newbie
Activity: 25
Merit: 0
I wonder if anyone here has ever found any public key with pubhunt???

I think you are right someone lucky will eventually find #66 cause the way I see it is the last 12 characters can easily be brute forced, less than a day with 3 RTX GPUs for entire range

the very first character is a 2 or 3 take your pick, then its really the next 4 characters after that needs to be guessed. The probability of someone being lucky is high but most people give up after a few weeks I reckon.

I have searched a number of ranges I know the key is not in, If there was a place people were willing to collab I think it would be found quicker but I guess everyone just solo
member
Activity: 185
Merit: 15
Two things you should never abandon: Family & BTC
pubhunt seems very limited, would it be easier to search for the public key using the hash160 first for puzz#66 then use kangaroo. Or is the difficulty to find the public key even harder then finding the actual private key. I've been searching for a Month for #66 using various methods but are we certain the range is 20000000000000000  -  3ffffffffffffffff  , I don't think its on the 319 range, who has better guess to the range?

The difficulty for finding a public key that opens puzzle #66 is as difficult as trying to find the public key of a bitcoin's dead address .. or any other ordinary address  .. i e: 256 bits difficulty .. so in this case brute forcing the entire 66 bit range is more likely achievable than trying to search for an unknown public key

Your second question reminds me of the doubt we heard earlier about puzzle #64, where it took too long for ppl to find the key that some even started to doubt the range entirely is wrong or intentionally misleading by the puzzle creator. Ppl tend to forget the fact that 64 bits, and even worse, puzzle #66 are too huge that it could normally take decades to find the keys within their ranges ..To give you a feel of how big the range is, a gpu with a power of 500 million keys/seconds will finish the entire 66 bits range in 2339 Years   Shocked

 if you ask me where the key might be located, my one and only answer is: it can be anywhere within 20000000000000000  -  3ffffffffffffffff

Meaning there is no clues here .. no narrowing down options .. no predictions .. no pattern .. we have to randomly search our way into this range until one lucky bastard among us eventually finds it.



Hope that answers your questions
newbie
Activity: 25
Merit: 0
pubhunt seems very limited, would it be easier to search for the public key using the hash160 first for puzz#66 then use kangaroo. Or is the difficulty to find the public key even harder then finding the actual private key. I've been searching for a Month for #66 using various methods but are we certain the range is 20000000000000000  -  3ffffffffffffffff  , I don't think its on the 319 range, who has better guess to the range?
jr. member
Activity: 49
Merit: 1
Quote

They're relentless already. Check out NVIDIA's "Hybrid Quantum-Classical Computing Platform" .. and "cuQuantum SDK"

WOW! Thanks a lot for this information... THUMBS UP!
member
Activity: 185
Merit: 15
Two things you should never abandon: Family & BTC
I wish we would have any quantum computing students or gurus here to discuss how many Qubits we need to break as much as 66 bits .. I'm guessing around 1000-3000 at most .. Quantum computing is amazingly useful when it comes to cryptography.

The "quantum leap" will come one day for us too, i'm confident at Nvidia, they are constantly working on the further development of their processors.. let's take a look at the developer cards... the computing power is overwhelming and will certainly continue to increase. Sure, it's not a comparison to the quantum computer... but but...

They're relentless already. Check out NVIDIA's "Hybrid Quantum-Classical Computing Platform" .. and "cuQuantum SDK"
jr. member
Activity: 49
Merit: 1
I wish we would have any quantum computing students or gurus here to discuss how many Qubits we need to break as much as 66 bits .. I'm guessing around 1000-3000 at most .. Quantum computing is amazingly useful when it comes to cryptography.

The "quantum leap" will come one day for us too, i'm confident at Nvidia, they are constantly working on the further development of their processors.. let's take a look at the developer cards... the computing power is overwhelming and will certainly continue to increase. Sure, it's not a comparison to the quantum computer... but but...
member
Activity: 185
Merit: 15
Two things you should never abandon: Family & BTC
I wish we would have any quantum computing students or gurus here to discuss how many Qubits we need to break as much as 66 bits .. I'm guessing around 1000-3000 at most .. Quantum computing is amazingly useful when it comes to cryptography.
member
Activity: 185
Merit: 15
Two things you should never abandon: Family & BTC
Quote
'....it's better after dividing the big range into smaller ones, to search within those subranges "randomly"'.

That's what I do.... that's exactly how I work.. Smiley I'm not a newbie in this matter.... But better with 600 MKeys/s than not looking for it at all... ^^

Yep, and it's not so far fetched either when searching with less power .. i remember someone solving an ethereum block with a very tiny mining rig .. solo
Jump to: