Bitcoin Forum
November 12, 2024, 01:49:30 PM *
News: Check out the artwork 1Dq created to commemorate this forum's 15th anniversary
 
   Home   Help Search Login Register More  
Pages: « 1 ... 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 [97]
  Print  
Author Topic: BitCrack - A tool for brute-forcing private keys  (Read 76644 times)
GikNikko
Newbie
*
Offline Offline

Activity: 1
Merit: 0


View Profile
October 09, 2024, 08:48:28 AM
 #1921

Hi guys,
I've been trying to compile BitCrack for my GPU (RTX 3080ti) for over 2 months now but I can't compile it. Can anyone please give me some directions or send me the downloaded program?
WanderingPhilospher
Full Member
***
Offline Offline

Activity: 1204
Merit: 237

Shooters Shoot...


View Profile
October 11, 2024, 05:28:10 AM
 #1922

Hi guys,
I've been trying to compile BitCrack for my GPU (RTX 3080ti) for over 2 months now but I can't compile it. Can anyone please give me some directions or send me the downloaded program?
Why waste your time? Use a VS with Bitcrack option or Keyhunt-Cuda / Rotor-Cuda. Search on github. They are faster than bitcrack.

Quote
Indeed speed is way faster but the problem i've encountered with KeyHuntCuda is that the if the address is in the last key of the range won't find it..(1st key no problem) tried adding +1 and sometimes is found some times not.. tested 10x
I've compiled it with multiple versions of cuda and g++ and still have the same issue.. i wonder if it's used with multiple gpu's and the space is split between the gpu's what if the searched address is in the last key from share 2/8 gpu's will it be found ?.. haven't tested as the split ranges are not shown.. (might test bit later to split range and get last key2address from share2/8)
With BitCrack had no issues.. it is  slower but always spot on.
ubuntu22.04 and 4090

How many GPUs were you using when it skipped the last key? Running just 1 per instance, that should not happen. I have tested this many times while setting up pools.
Nournst57
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
October 11, 2024, 08:11:29 AM
 #1923

Hey everyone, this got me thinking about something I recently read called the Dual Vanity Address Attack (DVAA). It’s where attackers can generate Bitcoin addresses that match patterns at both the start and end of an address. By doing this, they reduce the randomness we usually rely on for security, making it easier to pull off phishing or impersonation scams. It’s not quite brute-forcing keys, but it's another angle that shows how address generation can be vulnerable.
3dmlib
Jr. Member
*
Offline Offline

Activity: 44
Merit: 2


View Profile
October 11, 2024, 01:14:08 PM
 #1924

ttdclient on ttdpool is fastest brute tool now.
WanderingPhilospher
Full Member
***
Offline Offline

Activity: 1204
Merit: 237

Shooters Shoot...


View Profile
October 11, 2024, 02:36:09 PM
 #1925

ttdclient on ttdpool is fastest brute tool now.
(I will post here as well to stop the spreading of misinformation.)

You have lost your mind coming on this forum and spreading lies lol. Just stop.

Yeah, TTD is the fastest in skipping keys, generating wrong private keys, and losing your money. Yes, I agree, it is the fastest in those things. So please don't come on here trying to advertise for them and spread half truths.

I know, the owner does not take testing seriously at all, I've got receipts, so don't come at me with some BS.
xupaxiwy
Newbie
*
Offline Offline

Activity: 1
Merit: 0


View Profile
October 11, 2024, 10:25:56 PM
 #1926

Hey everyone, this got me thinking about something I recently read called the Dual Vanity Address Attack (DVAA).

Dual Vanity Address Attack (DVAA) is not about brute-forcing private keys but rather reducing the address space that attackers need to search by matching both the prefix and suffix of Bitcoin addresses.

This drastically lowers the randomness, shrinking the area we rely on. As a result, it makes impersonation or phishing much easier. This method doesn’t replace brute-forcing I guess but complements it, further it shows one more weaknesses in address generation.
citb0in
Hero Member
*****
Offline Offline

Activity: 840
Merit: 730


Bitcoin g33k


View Profile
October 12, 2024, 07:31:57 AM
Last edit: October 12, 2024, 08:18:19 AM by citb0in
Merited by ABCbits (2)
 #1927

Hey everyone, this got me thinking about something I recently read called the Dual Vanity Address Attack (DVAA). It’s where attackers can generate Bitcoin addresses that match patterns at both the start and end of an address. By doing this, they reduce the randomness we usually rely on for security, making it easier to pull off phishing or impersonation scams. It’s not quite brute-forcing keys, but it's another angle that shows how address generation can be vulnerable.

Hey everyone, this got me thinking about something I recently read called the Dual Vanity Address Attack (DVAA).

Dual Vanity Address Attack (DVAA) is not about brute-forcing private keys but rather reducing the address space that attackers need to search by matching both the prefix and suffix of Bitcoin addresses.

This drastically lowers the randomness, shrinking the area we rely on. As a result, it makes impersonation or phishing much easier. This method doesn’t replace brute-forcing I guess but complements it, further it shows one more weaknesses in address generation.

Please explain:

1) why you create a fresh new account to anonymously spread such crap and try to back it up without any technical explanation while maintaining to disguise your real and regularly username used on this forum
2) what exactly you have not understood about the avalanche effect and the result is that you assume you can use it to reduce the address range (which is not true)
3) why you bring randomness into play, that doesn't fit in with what you said, technically speaking in that context

Let's take your last username used "xupaxiwy" and for the sake of example the first and last two characters to look for...

Format
Bitcoin Address | Private Key
***********************************


1xuoyW6VS9JcEbwXmeKwZCPxJVmLyqFwy | B916A3BCF9DE0D3D97547A4E5CE541D7DEC5291DD86BA8975006F6FBA9F8FDA4
1xuxaNFBvMXwB6P5H9qc5TaKmh91DwFwy | D51E7843F7B980E257F27DA7A943C60F4549D0B627185556A289CBD3E48CD8CE
1xujEHjYxnPv9iiirpjZmG8ZYdC1asSwy | 6539D4FA10903B1E1230B484F96889CEA8112D31495EF0DF77E6F3CA1DBE9319



4) please explain the reduction of keyspace on the shown example


  _      _   _       __  _          _  _   __
 |_) |  / \|/   (_  / \ | \  / |_ |_) (_ 
 |_) |_ \_/ \_ |\   __) \_/ |_ \/  |_ | \ __)
--> citb0in Solo-Mining Group <--- low stake of only 0.001 BTC. We regularly rent about 5 PH/s hash power and direct it to SoloCK pool. Wanna know more? Read through the link and JOIN NOW
Nournst57
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
October 16, 2024, 07:04:13 PM
 #1928

Quote
Please explain:

1) why you create a fresh new account to anonymously spread such crap and try to back it up without any technical explanation while maintaining to disguise your real and regularly username used on this forum
2) what exactly you have not understood about the avalanche effect and the result is that you assume you can use it to reduce the address range (which is not true)
3) why you bring randomness into play, that doesn't fit in with what you said, technically speaking in that context

Thanks for the response! Let me clarify a few things:

1) Since the topic here is brute force, DVAA is simply a new brute force method targeting specific areas of addresses (prefix and suffix). It doesn’t brute-force the entire address space but narrows the search, making phishing or impersonation easier.

2) No brute force method is 100% successful, and DVAA is no different. It reduces randomness at the boundaries, not the entire space. It’s not about breaking Bitcoin’s security entirely but exploring an attack vector where randomness is reduced. Especially quantum computing will make a difference in brute forcing.

3)The avalanche effect and full randomness still hold, but in DVAA, the focus is on manipulating smaller sections. For example, in your case with prefixes and suffixes, the complexity is significantly reduced for those target areas, even if the overall security remains intact.

4) I’m new to the forum and everyone has a starting point, right? This was a good point to start. Is it the idea or the number of entries that matters more here? Just because I don’t have many posts doesn’t mean the idea isn’t worth discussing. Let’s focus on the concept please!
citb0in
Hero Member
*****
Offline Offline

Activity: 840
Merit: 730


Bitcoin g33k


View Profile
October 17, 2024, 06:28:04 AM
Merited by ABCbits (2)
 #1929

Quote
Please explain:

1) why you create a fresh new account to anonymously spread such crap and try to back it up without any technical explanation while maintaining to disguise your real and regularly username used on this forum
2) what exactly you have not understood about the avalanche effect and the result is that you assume you can use it to reduce the address range (which is not true)
3) why you bring randomness into play, that doesn't fit in with what you said, technically speaking in that context

Thanks for the response! Let me clarify a few things:

1) Since the topic here is brute force, DVAA is simply a new brute force method targeting specific areas of addresses (prefix and suffix). It doesn’t brute-force the entire address space but narrows the search, making phishing or impersonation easier.

2) No brute force method is 100% successful, and DVAA is no different. It reduces randomness at the boundaries, not the entire space. It’s not about breaking Bitcoin’s security entirely but exploring an attack vector where randomness is reduced. Especially quantum computing will make a difference in brute forcing.

3)The avalanche effect and full randomness still hold, but in DVAA, the focus is on manipulating smaller sections. For example, in your case with prefixes and suffixes, the complexity is significantly reduced for those target areas, even if the overall security remains intact.

4) I’m new to the forum and everyone has a starting point, right? This was a good point to start. Is it the idea or the number of entries that matters more here? Just because I don’t have many posts doesn’t mean the idea isn’t worth discussing. Let’s focus on the concept please!


what a load of rubbish. On top of that, you haven't even answered a single one of the questions asked, instead you blather on about pointless, theoretical, superficial stuff. Nobody can be that stupid, I'm now wondering if there are only some wannabe intelligent AI generated forum bots around, everything else makes no sense.

As long as you cannot technically substantiate your self-created hippie jewelry name DVAA and explain it using the example provided, there is nothing more to discuss, period.

  _      _   _       __  _          _  _   __
 |_) |  / \|/   (_  / \ | \  / |_ |_) (_ 
 |_) |_ \_/ \_ |\   __) \_/ |_ \/  |_ | \ __)
--> citb0in Solo-Mining Group <--- low stake of only 0.001 BTC. We regularly rent about 5 PH/s hash power and direct it to SoloCK pool. Wanna know more? Read through the link and JOIN NOW
ABCbits
Legendary
*
Offline Offline

Activity: 3052
Merit: 8079


Crypto Swap Exchange


View Profile
October 17, 2024, 09:24:42 AM
 #1930

--snip--
what a load of rubbish. On top of that, you haven't even answered a single one of the questions asked, instead you blather on about pointless, theoretical, superficial stuff. Nobody can be that stupid, I'm now wondering if there are only some wannabe intelligent AI generated forum bots around, everything else makes no sense.

As long as you cannot technically substantiate your self-created hippie jewelry name DVAA and explain it using the example provided, there is nothing more to discuss, period.

FYI chatbot or AI usage has been around for at least a year, see these threads.
AI Spam Report Reference Thread
Users who spread false/fake/unhelpful information on technical board, where many of those reported users seems to use chatbot.

█▀▀▀











█▄▄▄
▀▀▀▀▀▀▀▀▀▀▀
e
▄▄▄▄▄▄▄▄▄▄▄
█████████████
████████████▄███
██▐███████▄█████▀
█████████▄████▀
███▐████▄███▀
████▐██████▀
█████▀█████
███████████▄
████████████▄
██▄█████▀█████▄
▄█████████▀█████▀
███████████▀██▀
████▀█████████
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
c.h.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀█











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
bulleteyedk
Jr. Member
*
Offline Offline

Activity: 94
Merit: 3


View Profile
October 18, 2024, 12:08:15 PM
 #1931

Hi guys,
I've been trying to compile BitCrack for my GPU (RTX 3080ti) for over 2 months now but I can't compile it. Can anyone please give me some directions or send me the downloaded program?

Just go to the github linked in the first post, instead of downloading the sourcecode, just download the exe file.

If you really want to compile it your self, i can't help
Heinri
Newbie
*
Online Online

Activity: 3
Merit: 0


View Profile
November 01, 2024, 12:21:06 PM
 #1932

It seems like a lot of users are encountering challenges with BitCrack. Have you found any specific guides or resources that helped you in your compilation attempts?
Pages: « 1 ... 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 [97]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!