Bitcoin Forum
August 31, 2024, 11:11:00 PM *
News: Latest Bitcoin Core release: 27.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: 1 bit LSB  (Read 83 times)
cassondracoffee (OP)
Newbie
*
Offline Offline

Activity: 14
Merit: 0


View Profile
July 14, 2024, 09:41:55 AM
Last edit: July 14, 2024, 10:14:03 AM by cassondracoffee
 #1

python3 gen_data.py -f data.json  -c SECP256K1 -b 1 -t LSB -n 360

Private Key: 0xa0a9e351153934a4d5e86c4c53f21bef542e676e2639235596c5d3b81f57
Preparing Data
Generating 360 signatures with curve SECP256K1
 leaking 1 bits for k (LSB)  ...
File data.json written with all data.

python3 lattice_attack.py -f data.json  
(time python3 lattice_attack.py -f data.json) > time.txt 2>&1

----- Lattice ECDSA Attack -----
Loading data from file data.json
Running with 1 bits of k (LSB)
Starting recovery attack (curve SECP256K1)
Constructing matrix
Solving matrix ...
LLL reduction
.....
....
still running.....


How long does time solve guys Huh I run more than 6hr and not solving key, still running.....

If anyone tries to solve 1 bit of their own key



Please guide me on how quickly to solve 1 bit know

What method do you recommend me gus??



MINIMUM_BITS = 1
RECOVERY_SEQUENCE = [None, 15, 25, 40, 50, 60]
SIGNATURES_NUMBER_MARGIN = 1.03 # 0.75

what value change to solve 1 bit example Private Key: 0xa0a9e351153934a4d5e86c4c53f21bef542e676e2639235596c5d3b81f57

my pc 4cpu , i am run this comment  
 
taskset -c 1,2,3 time python3 lattice_attack.py -f data.json  # this is correct method or not , how to run multi thread



i am asking for chatgpt

Calculation Example
Let's assume that a block size of 40 with a lattice dimension of 200 takes about 1 hour on a given machine. Extrapolating this to a block size of 60 and a lattice dimension of 352 might result in:

An increase by an order of magnitude or more due to the larger block size.
Additional runtime due to the higher lattice dimension.
Rough Estimate
Block Size 40, Dimension 200: 1 hour
Block Size 60, Dimension 352: Potentially 10 to 100 times longer, resulting in a rough estimate of 10 to 100 hours, or approximately 0.5 to 4 days.

After day 4, key found or not Huh My example Private Key

jacky19790729
Jr. Member
*
Offline Offline

Activity: 82
Merit: 8


View Profile
July 14, 2024, 12:45:20 PM
 #2

python3 gen_data.py -f data.json  -c SECP256K1 -b 1 -t LSB -n 360

Private Key: 0xa0a9e351153934a4d5e86c4c53f21bef542e676e2639235596c5d3b81f57
Preparing Data
Generating 360 signatures with curve SECP256K1
 leaking 1 bits for k (LSB)  ...
File data.json written with all data.

=== my test results ===

252  (  leak  4 bit  ) ===>          70  rsz        Success   ( Time:   8    seconds  )

253  (  leak  3 bit  ) ===>         155  rsz        Success   (Time:    661   seconds  )

254 (  leak  2 bit  ) ===>         200~1500+ rsz     Never Recovery my Private Key

255 (  leak  1 bit  ) ===>         1500+  rsz         Never Recovery my Private Key

256 (  leak  0 bit  ) ===>         1500+  rsz         Never Recovery my Private Key

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!