@NotATether
Noted, I still remember these cons as something I was debugging dead on. I’m really a data-driven debugger, without memory access and lack of in-depth knowledge of CUDA, data is the only way I would be able to track logic.
3:30 here, so I’ll take a look tomorrow maybe something I’ll hit that helps anyone along too.
I decided after my contracted Kangaroo work is done (it's almost complete) I'm going to make a better Bitcrack. No point in me holding the source also or instead of trying to solve puzzles we spend ~3 pages of threads arguing about source code distribution.
Just curious, why bitcrack? If you want to improve upon anything, I would suggest to look at VanitySearch. It already handles multi GPU and is faster. The issue is reading full address, but works with partial/strings. It already does what bitcrack does, and faster, just full address issue.
Just a question.
Personally tried, but same problem with bitcrack, debugging without memory access makes this a really difficult one. I personally found the bitcrack code easier to understand & follow, the vanity one makes me feel like I’m trying to debug professor code. But that’s just personal taste. Besides bitcrack has already built in keyspacing, but vanity can be modified to do so if needed.
I’m kinda convinced if we would be able to *understand* what makes ampere cards crash on bitcrack, you could prob. fix vanity too.