Bitcoin Forum
January 18, 2026, 07:31:32 PM *
News: Latest Bitcoin Core release: 30.2 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: BSGS for over 80 bits  (Read 443 times)
pbies (OP)
Full Member
***
Offline Offline

Activity: 404
Merit: 230



View Profile
April 20, 2025, 10:39:24 AM
 #1

Guys, I am a madman and want to try BSGS for old 50 BTC addresses (pubkeys) in full 2^256 range. (There are over 34k of them)

Is there a software currently to do that? I mean software/program that accepts over 80 bits and up to 256?

BTC: bc1qmrexlspd24kevspp42uvjg7sjwm8xcf9w86h5k
Ivystar5
Full Member
***
Offline Offline

Activity: 518
Merit: 238


Stressed since 19's


View Profile
April 20, 2025, 12:15:10 PM
Merited by pbies (1)
 #2

Visit this thread BSGS solver for cuda by Etar (It has all you are looking for if you take your time to read through)

I think he also wrote the fraction on GitHub - https://github.com/Etayson/fraction-bsgs.git

pbies (OP)
Full Member
***
Offline Offline

Activity: 404
Merit: 230



View Profile
April 20, 2025, 01:20:27 PM
 #3

Visit this thread BSGS solver for cuda by Etar (It has all you are looking for if you take your time to read through)

I think he also wrote the fraction on GitHub - https://github.com/Etayson/fraction-bsgs.git

Great! Thanks!

However I have problems running these two programs. I've got PureBasic full-version but after fixing one code error the programs just start and immediately stop without any info. Strange.

BTC: bc1qmrexlspd24kevspp42uvjg7sjwm8xcf9w86h5k
BADERO
Member
**
Offline Offline

Activity: 112
Merit: 58


View Profile
April 21, 2025, 02:43:45 PM
 #4

Visit this thread BSGS solver for cuda by Etar (It has all you are looking for if you take your time to read through)

I think he also wrote the fraction on GitHub - https://github.com/Etayson/fraction-bsgs.git

Great! Thanks!

However I have problems running these two programs. I've got PureBasic full-version but after fixing one code error the programs just start and immediately stop without any info. Strange.

Try running the program in a terminal or command prompt so you can see any error messages before the window closes If programs you're trying to run in PureBasic start and then stop right away without any error or output, it's probably because essential input was missing, the configuration was incorrect, or an unhandled exception occurred make sure you're providing all necessary parameters (such as target pubkeys or key ranges) in the command line or input files examine the code's logic, paying particular attention to initialisation and file handling, and try adding debug prints or logging to see where it goes wrong

pbies (OP)
Full Member
***
Offline Offline

Activity: 404
Merit: 230



View Profile
April 21, 2025, 05:04:02 PM
 #5

Visit this thread BSGS solver for cuda by Etar (It has all you are looking for if you take your time to read through)

I think he also wrote the fraction on GitHub - https://github.com/Etayson/fraction-bsgs.git

Great! Thanks!

However I have problems running these two programs. I've got PureBasic full-version but after fixing one code error the programs just start and immediately stop without any info. Strange.

Try running the program in a terminal or command prompt so you can see any error messages before the window closes If programs you're trying to run in PureBasic start and then stop right away without any error or output, it's probably because essential input was missing, the configuration was incorrect, or an unhandled exception occurred make sure you're providing all necessary parameters (such as target pubkeys or key ranges) in the command line or input files examine the code's logic, paying particular attention to initialisation and file handling, and try adding debug prints or logging to see where it goes wrong

Yes, I've runned the compiled .exe with arguments and without. No error messages or anything in both cases. It just does nothing. Cannot do anything about it, tried many times.

BTC: bc1qmrexlspd24kevspp42uvjg7sjwm8xcf9w86h5k
BADERO
Member
**
Offline Offline

Activity: 112
Merit: 58


View Profile
April 21, 2025, 06:19:48 PM
 #6

Visit this thread BSGS solver for cuda by Etar (It has all you are looking for if you take your time to read through)

I think he also wrote the fraction on GitHub - https://github.com/Etayson/fraction-bsgs.git

Great! Thanks
However I have problems running these two programs. I've got PureBasic full-version but after fixing one code error the programs just start and immediately stop without any info. Strange.

Try running the program in a terminal or command prompt so you can see any error messages before the window closes If programs you're trying to run in PureBasic start and then stop right away without any error or output, it's probably because essential input was missing, the configuration was incorrect, or an unhandled exception occurred make sure you're providing all necessary parameters (such as target pubkeys or key ranges) in the command line or input files examine the code's logic, paying particular attention to initialisation and file handling, and try adding debug prints or logging to see where it goes wrong

Yes, I've runned the compiled .exe with arguments and without. No error messages or anything in both cases. It just does nothing. Cannot do anything about it, tried many times.
To track runtime events, use a debugger such as x64dbg. A silent crash or an inability to load a GPU kernel could be detected
  U can also Test with Minimal Command
Code:
 bitcrack.exe -c --keyspace 1:1000 -o results.txt 1BoatSLRHtKNngkdXEeobR76b53LETtpyT

 And if  this doesn’t even write the file or show progress, something is wrong at the binary level or with GPU compatibility
Code:
 bitcrack.exe -b 1 -t 1 -o results.txt 1BoatSLRHtKNngkdXEeobR76b53LETtpyT

pbies (OP)
Full Member
***
Offline Offline

Activity: 404
Merit: 230



View Profile
April 21, 2025, 10:38:43 PM
 #7

To track runtime events, use a debugger such as x64dbg. A silent crash or an inability to load a GPU kernel could be detected
  U can also Test with Minimal Command
Code:
 bitcrack.exe -c --keyspace 1:1000 -o results.txt 1BoatSLRHtKNngkdXEeobR76b53LETtpyT

 And if  this doesn’t even write the file or show progress, something is wrong at the binary level or with GPU compatibility
Code:
 bitcrack.exe -b 1 -t 1 -o results.txt 1BoatSLRHtKNngkdXEeobR76b53LETtpyT

It is not bitcrack. These are PureBasic programs compiled with original program for that, with GUI.

No errors at compile time and no messages when running these .exe files with or without params.

BTC: bc1qmrexlspd24kevspp42uvjg7sjwm8xcf9w86h5k
rose45scott
Newbie
*
Offline Offline

Activity: 1
Merit: 0


View Profile
May 01, 2025, 08:40:32 AM
Last edit: May 02, 2025, 04:19:41 AM by rose45scott
 #8

Guys, I am a madman and want to try BSGS for old 50 BTC addresses (pubkeys) in full 2^256 range. (There are over 34k of them)

Is there a software currently to do that? I mean software/program E-ZPassMD that accepts over 80 bits and up to 256?


Hello,
While attempting to crack 256-bit private keys for Bitcoin addresses using the Baby-step Giant-step (BSGS) algorithm might sound like an exciting endeavor, it's crucial to understand the practical limitations and the current state of technology.

Practicality of BSGS for 256-bit Keys
Computational Infeasibility: The keyspace for Bitcoin private keys is 2
256
 . The BSGS algorithm has a time and space complexity of approximately  
N


 , where N is the order of the group. In the case of ECDSA over the secp256k1 curve used by Bitcoin, N is roughly 2
256
 . Therefore, a full BSGS attack would require approximately 2
128
  operations and storage, which is computationally infeasible with current and foreseeable technology. To put this into perspective, 2
80
  operations are considered at the very edge of what might be achievable with immense resources and time. 2
128
  is astronomically larger.
Bitcoin Key Space: Bitcoin addresses are derived from public keys, which in turn are derived from private keys. The private keys are 256-bit numbers. Trying to find a private key corresponding to a given public key (or address) is an instance of the Elliptic Curve Discrete Logarithm Problem (ECDLP). BSGS is one algorithm for solving this, but its square root complexity makes it impractical for the scale of Bitcoin's key space.
Software for Large Keyspaces
Current Limitations: As of my last update in May 2025, there isn't any publicly known software capable of performing a full BSGS attack on key sizes anywhere close to 256 bits. The memory and computational resources required are simply too vast.
Research Focus: Research in cryptanalysis does explore algorithms for solving the ECDLP, and there are variations and optimizations of BSGS. However, these are generally theoretical or applicable to much smaller key sizes than 256 bits.
Specialized Hardware: While specialized hardware can accelerate cryptographic computations, even custom-designed ASICs would likely be unable to overcome the fundamental limitations posed by the  
2
256
 


 =2
128
  complexity of BSGS.
Alternative Attack Vectors
It's worth noting that instead of trying to brute-force the entire 256-bit keyspace, attackers often look for vulnerabilities in:

Random Number Generation: If the private key generation process was flawed and didn't produce truly random numbers, the effective keyspace might be much smaller and potentially exploitable. However, Bitcoin's secp256k1 curve and standard practices aim to avoid such weaknesses.
Wallet Software: Vulnerabilities in wallet software could expose private keys through exploits, malware, or phishing attacks. These are often more practical attack vectors than trying to break the underlying cryptography.
Side-Channel Attacks: These attacks exploit physical characteristics of the devices performing cryptographic operations (e.g., power consumption, electromagnetic emissions) to try and extract secret information.
pbies (OP)
Full Member
***
Offline Offline

Activity: 404
Merit: 230



View Profile
May 01, 2025, 08:56:58 AM
 #9

Guys, I am a madman and want to try BSGS for old 50 BTC addresses (pubkeys) in full 2^256 range. (There are over 34k of them)

Is there a software currently to do that? I mean software/program that accepts over 80 bits and up to 256?


Hello,
While attempting to crack 256-bit private keys for Bitcoin addresses using the Baby-step Giant-step (BSGS) algorithm might sound like an exciting endeavor, it's crucial to understand the practical limitations and the current state of technology.

Practicality of BSGS for 256-bit Keys
Computational Infeasibility: The keyspace for Bitcoin private keys is 2
256
 . The BSGS algorithm has a time and space complexity of approximately 
N


 , where N is the order of the group. In the case of ECDSA over the secp256k1 curve used by Bitcoin, N is roughly 2
256
 . Therefore, a full BSGS attack would require approximately 2
128
  operations and storage, which is computationally infeasible with current and foreseeable technology. To put this into perspective, 2
80
  operations are considered at the very edge of what might be achievable with immense resources and time. 2
128
  is astronomically larger.
Bitcoin Key Space: Bitcoin addresses are derived from public keys, which in turn are derived from private keys. The private keys are 256-bit numbers. Trying to find a private key corresponding to a given public key (or address) is an instance of the Elliptic Curve Discrete Logarithm Problem (ECDLP). BSGS is one algorithm for solving this, but its square root complexity makes it impractical for the scale of Bitcoin's key space.
Software for Large Keyspaces
Current Limitations: As of my last update in May 2025, there isn't any publicly known software capable of performing a full BSGS attack on key sizes anywhere close to 256 bits. The memory and computational resources required are simply too vast.
Research Focus: Research in cryptanalysis does explore algorithms for solving the ECDLP, and there are variations and optimizations of BSGS. However, these are generally theoretical or applicable to much smaller key sizes than 256 bits.
Specialized Hardware: While specialized hardware can accelerate cryptographic computations, even custom-designed ASICs would likely be unable to overcome the fundamental limitations posed by the 
2
256
 


 =2
128
  complexity of BSGS.
Alternative Attack Vectors
It's worth noting that instead of trying to brute-force the entire 256-bit keyspace, attackers often look for vulnerabilities in:

Random Number Generation: If the private key generation process was flawed and didn't produce truly random numbers, the effective keyspace might be much smaller and potentially exploitable. However, Bitcoin's secp256k1 curve and standard practices aim to avoid such weaknesses.
Wallet Software: Vulnerabilities in wallet software could expose private keys through exploits, malware, or phishing attacks. These are often more practical attack vectors than trying to break the underlying cryptography.
Side-Channel Attacks: These attacks exploit physical characteristics of the devices performing cryptographic operations (e.g., power consumption, electromagnetic emissions) to try and extract secret information.

You didn't understood the question and you are writing spam here.

BTC: bc1qmrexlspd24kevspp42uvjg7sjwm8xcf9w86h5k
MB2AA5RR
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
January 17, 2026, 07:45:12 PM
 #10

Hello
I run Collider BSGS. The program is super optimized, without errors. I managed to adapt the program for RX5090 cards and I obtained scanning speeds of 60-64 Exakey/sec (when scanning a single address). In tests, the program does not miss any address at this speed. I am interested in collaborating with people who achieve higher speeds. I bought the PureBasic program. I was unable to make this program functional in random mode, the program scans correctly, sees the addresses (Pub key...) but does not notify me of the results. The test is done on valid addresses.
JackMazzoni
Jr. Member
*
Offline Offline

Activity: 180
Merit: 6


View Profile
Today at 03:41:23 AM
 #11

Guys, I am a madman and want to try BSGS for old 50 BTC addresses (pubkeys) in full 2^256 range. (There are over 34k of them)

Is there a software currently to do that? I mean software/program that accepts over 80 bits and up to 256?


I like your experiment. But BSGS hardly works on 256 range. I'm currently working on a hybrid, I'm combining BSGS with pollard kangaroo. I'm hoping it could be a many times faster than kangaroo.

Need Wallet Recovery? PM ME. 100% SAFE
MB2AA5RR
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
Today at 06:46:43 PM
 #12

Hello
I don't understand you. Collider bsgs cuda adapted by me for RTX5090, scans in any space you give it and the speed is the same ~64 Exa key/ sec Here are examples below:

C:\Users\NN\Desktop\COLLIDER>bsgscudaHT_1_9_7file -t 256 -b 256 -p 914 -w 32 -htsz 31 -pk 6cf4feb12b75e8e00fffffffffffffffff -pke 6cf4feb12b75e8eFFFFFFFFFFFFFFFFFFF -infile Puzle135
Number of GPU threads set to #256
Number of GPU blocks set to #256
Number of pparam set to #914
Items number set to 2^32=4294967296
HT size set to 2^31
Range begin: 0x6cf4feb12b75e8e00fffffffffffffffff
Range end: 0x6cf4feb12b75e8efffffffffffffffffff
Will be used file: Puzle135
Found 1 Cuda device.
Cuda device:NVIDIA GeForce RTX 5090 (30840.000/32606MB)
Current config hash[]
GiantSUBvalue:0000000000000000000000000000000000000000000000000000000200000000
GiantSUBpubkey: 038c0989f2ceb5c771a8415dff2b4c4199d8d9c8f9237d08084b05284f1e4df706
*******************************
Total GPU Memory Need: 30060.000MB
*******************************
Both HT files exist
Load BIN file:256_256_914_4294967296_g2.BIN
  • chunk:1073741824b
  • [1] chunk:1073741824b
    [2] chunk:1073741824b
    Last chunk:612368384b
    [3] chunk:612368384b
    Done in 00:00:00s
    Gstep: e48000000000000
    GPU count #1
    GPU #0 launched
    GPU #0 Free/Total/Need memory: 30838/32606/30060.002MB
    _A size:120
    GPU #0 copied giant array
    Remove Giant array, freed memory: 3656.000 MB
    Load BIN file:79be667ef9dcbbac55a06295ce870b07029bfcdb2dce28d959f2815b16f81798_4294967296_214 7483648_htGPUv0.BIN
  • chunk:1073741824b
  • [1] chunk:1073741824b
    [2] chunk:1073741824b
    .......................................
    [23] chunk:1073741824b
    Last chunk:4b
    [24] chunk:4b
    Done in 00:00:03s
    GPU #0 copied hash table
    Remove HT for GPU, freed memory: 24576.000 MB
    Random verify packed HTCPU items in file...ok
    START RANGE= 0000000000000000000000000000006cf4feb12b75e8e00fffffffffffffffff
      END RANGE= 0000000000000000000000000000006cf4feb12b75e8efffffffffffffffffff
    WIDTH RANGE= 000000000000000000000000000000000000000000000ff00000000000000000 = 2^76
    SUBpoint= (afaacd852045a0e036d93ee350283936b312b379f0f1e04bf35565897ecaa282, 8a334cf89c64444f69049c40d563f435209697a9a7b92b38bd59a02b44db2556)
    Save work every 180 seconds
    Checker thread started

    Findpubkey  : 02145d2611c823a396ef6712ce0f712f09b9b4f3135e3e0aa3230fb9b6d08d1e16
    Searchpubkey: 03235dada82c3477f7b249b6c7660b84b664d490465f98afd5efcc2b8c5c074c97
    Cnt:fea5718000000000001 [1][ 7161 ] = 7161 MKeys/s x2^33.0=2^65.81 Jt:00:19:27
    Reached end of space
    GPU#0 job finished
    GPU#0 thread finished
    cuda finished ok
    Press Enter to exit

    Speed ​​calculation:
    Total RANGE =  ff00000000000000000 (hex) => 75262715820734970593280 (decimal)
    Working time = 00:19:27 = 1167 sec
    Average working speed = 75262715820734970593280 : 1167 = 64,492,472,854,100,231,870 => ~ 64.49 Exa key/sec

    ORI
    ...
    GPU #0 copied hash table
    Remove HT for GPU, freed memory: 24576.000 MB
    Random verify packed HTCPU items in file...ok
    START RANGE= 0000000000000000000000000000006cf4feb12b75e8e00fffffffffffffffff
      END RANGE= 8c37ab83ae6429b684e4fe6cf1d9dab9cf421366e80f7ba90000000000000000
    WIDTH RANGE= 8c37ab83ae6429b684e4fe6cf1d9da4cda43623b72269b990000000000000001 = 2^256
    SUBpoint= (afaacd852045a0e036d93ee350283936b312b379f0f1e04bf35565897ecaa282, 8a334cf89c64444f69049c40d563f435209697a9a7b92b38bd59a02b44db2556)
    Save work every 180 seconds
    Checker thread started

    Findpubkey  : 02145d2611c823a396ef6712ce0f712f09b9b4f3135e3e0aa3230fb9b6d08d1e16
    Searchpubkey: 03235dada82c3477f7b249b6c7660b84b664d490465f98afd5efcc2b8c5c074c97
    Cnt:ef0b28000000000001 [1][ 7147 ] = 7147 MKeys/s x2^33.0=2^65.80 Jt:00:01:09  STOP
Pages: [1]
  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!