Topic: BitCrack - A tool for brute-forcing private keys - page 15. (Read 77647 times)

Sounds exciting. Keep us up-to-date, please. And if NotATether is leading the whole thing or is on board, then it can only be good   wish you good luck with your plans and the project.

I myself have not really intensively played with BitCrack except trying it on-the-fly. I would like to know if you experienced puzzle hunters mostly work with Bitcrack, or with BitCrack2, or VanBitCracken etc.. ? What is best suite for puzzle hunting and for what reason? As far as I have understood correctly and have also found out myself through trial and error, BitCrack cannot get by with multiple GPUs. You have to manually put the workload on the respective GPU ids, but automatically this does not work (e.g. VanitySearch can). Would VanBitcracken or VanBitCrakcenS help here (what exactly is the difference between these two?).

Much appreciated ...

When the Project is to take shape in Early to Mid 2023, the Person in charge of it is @NotATether. More than a Collaboration, it is the basis of developing different ways and means for distribution of workload via theFARM such that the work is 'forked' across theFARM and processed in smaller data 'chunks' than it is today.

Again though, this is a long term Project and will come into it's own when Time allows.

#crysx #cwi

very wisely said. Best of luck and success

Not Yet ...

I never release (or more - never have released) product details until they are nearing completion, or complete.

I will say this though, the 'cracking' should never be taken for the 'Money' as the Goal - EVER. The building of such thing are for Proof of Concept and Development. Mostly though, they for the 'Fun' of doing.

Money is NEVER the Goal - it is only ever the Consequence!

#crysx #cwi

Please tell us more.

Already Planned and Instituted ...

That is the answer for both questions

#crysx #cwi

Thanks, but i use AND graphic card


Is there a software to bruteforce Ethereum private keys for AMD graphic cards?
If there is, please let me know.

How do you force BitCrack to use several available graphic cards?


The option --list-devices lists correctly the installed and available GPUs. But when running BitCrack only uses a single one. With the option -d we can specify which GPU to use, but again it only uses that particular selected GPU. I tried to use those arguments, but it didn't change anything

-d 0,1
-d 0 1
-d 0 -d 1

BitCrack only uses one of graphic cards installed. Can anyone tell me how to make BitCrack capable of using several GPUs ? I also tried this version, but same effects, nothing helped.

For me the prize is the main, considering that i am investing money (actually around 400$ for hardware) and electricity costs (in Italy 0,55$ kilowatt/hour) in the challenge so a pool is not a good investment, the prize is too small.
Of course the glory of finding the key is nice and funny too but secondary.
I like to pick up randomly everyday the keyspaces to analyze, it's a way to see how the random choice progressively covers the entire puzzle 66 keyspace. For me it's very interesting.
Dividing the keyspace in 74 million parts it's like meeting a person in a country with 74 millions people.
With 7,4 million parts "only" it will be like meeting the same person in a big city (i will need a 2080ti to try it, actually price is around 400$).

Keyhunt-cuda brute forces ethereum too. I never tried it.

Tell please analog soft from Ethereum

Does anyone have a working copy of BitCrack2 from secp8x32 ? Please upload it somewhere so I could download a copy of the latest git tree. Thank you in advance

So if you had a supercomputer you would basically create a pool of your own resources, but no-one has that much hash - So why not join a pool and build a supercomputer together?

To me, cracking the puzzle is not really about the prize but I find it exciting to see how long it takes and what methods people use to crack it. like picking a lock. Plenty of people pick locks as a hobby

Just now i'm running a new keyspace check!  
And i keep notice of the checked keyspace.
I do it 5-6 times daily. It takes an hour each.

D:\BitCrack>cubitcrack -o out.txt --keyspace 20000000000000000:3ffffffffffffffff 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so -b 32 -t 128 -p 5344 --share 36110528/74000000
[2022-11-04.07:14:56] [Info] Share 36110528 of 74000000
[2022-11-04.07:14:56] [Info] Compression: compressed
[2022-11-04.07:14:56] [Info] Starting at: 000000000000000000000000000000000000000000000002F9D886E6C2425E70
[2022-11-04.07:14:56] [Info] Ending at:   000000000000000000000000000000000000000000000002F9D8875AD6CA2BFF
[2022-11-04.07:14:56] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2022-11-04.07:14:56] [Info] Initializing NVIDIA GeForce GTX 1060 3GB
[2022-11-04.07:14:56] [Info] Generating 21,889,024 starting points (835.0MB)
[2022-11-04.07:15:04] [Info] 10.0%
[2022-11-04.07:15:06] [Info] 20.0%
[2022-11-04.07:15:08] [Info] 30.0%
[2022-11-04.07:15:08] [Info] 40.0%
[2022-11-04.07:15:08] [Info] 50.0%
[2022-11-04.07:15:08] [Info] 60.0%
[2022-11-04.07:15:09] [Info] 70.0%
[2022-11-04.07:15:09] [Info] 80.0%
[2022-11-04.07:15:09] [Info] 90.0%
[2022-11-04.07:15:10] [Info] 100.0%
[2022-11-04.07:15:10] [Info] Done
NVIDIA GeForce G 2633 / 3071MB | 1 target 130.57 MKey/s (1,926,234,112 total) [00:00:13]

Before the year's end i'm planning to buy a 2080ti to brute force the keyranges like now (i should reduce the keyspace in 7,4 millions parts, now is 74 millions parts) and use the actual 1060 for the keyhunt-cuda random check, only for the unchecked keyspaces between the already checked keyspaces.

Cubitcrack uses brute force to analyze key by key the entire keyspace that is submitted to it.
Keyhunt-cuda allows you to search for the key within a predetermined keyspace in random mode.

what is the main difference between cubitcrack and keyhunt-cuda ?

I think the best strategy is to use 2 computers (or splitting the power of the supercomputer).
The first one uses cubitcrack and you select randomly the keyspaces to check daily. Small keyspace portions to cover progressively the entire puzzle 66 range and without concentrating on few big portions.
The second one uses keyhunt-cuda in random mode to check for a fixed period of time (e.g. 12 hours) the unchecked keyspaces between the already checked keyspaces.

About commands you can see them in my previous posts.

Let's say you would have something like a 'supercomputer' with enormous power, what bitcrack command would you use to run for trying to crack the puzzle(s) ? Would you use cubitcrack or even bitcrack2 ?

My second question is: Are there any available tools like BitCrack that will make use of Tensor for much higher calculation rates than CUDA, does it make sense at all for Tensor use in our applications? As far as I know, Tensor cores can compute a lot faster than the CUDA cores. CUDA cores perform one operation per clock cycle, whereas tensor cores can perform multiple operations per clock cycle. On the other hand, CUDA cores produce very accurate results. So it Tensor only good for AI learning and NN but not for brute-force cracking for our application?

Better to try luck alone, perhaps sharing the ranges already tested. The prize is too small to split into a group. I believe that a random approach in choosing only the intervals is the best solution because it allows you to test small portions of the entire range and make a good competition to groups organized in a pool and which are usually concentrated on large and not very distributed portions..
Let's see who will find the key first!

There are just so many ranges on Puzzle #66 that its near impossible to solo.

Stats from ttdsales pool below in my sig.

Total Ranges Checked: 92,272 of 33,554,432
Total Private Keys Checked: 101.45414 Quadrillion
Percentage completed: 0.274992%

the ttd pool is using a customised vanitygen for cracking, source is available in the files on the site. seems to work quicker than Bitcrack. Worth trying out even if not with the pool, I found big improvements on the 2080 Ti's and 3070's not as much on the 3090's but still faster.

http://www.ttdsales.com/66bit/index.php