Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Speed has decreased #111

Closed
SUN-2913 opened this issue Oct 14, 2021 · 19 comments
Closed

Speed has decreased #111

SUN-2913 opened this issue Oct 14, 2021 · 19 comments
Assignees

Comments

@SUN-2913
Copy link

Hi!
In the latest beta version 0.2.211012 in BGSG mode, the speed decreased exactly 2 times compared to version 0.2.211007. The command line is the same.

@albertobsd albertobsd self-assigned this Oct 14, 2021
@albertobsd
Copy link
Owner

Thanks for report this, you are the second person who report it to me, another person report it to me in telegram. But is good to have this issue here to keep tracking it.

Damn is not the first time that i did a mess with the speed, but this time i did not touch the speed counter.

The only part that i change is the the related with the bPtable key generation and the bloomfitler multithread access in the previous version i have only one big bloom filter but in the new i made an array of 256 bloomfilters to speed up the multi-thread access.

So letme check what is happening and i will try to correct it ASAP.

Best regards!

@albertobsd
Copy link
Owner

I just check with defaults values and yes there some decrement but in my case is not the half, is some 8 or 10 %

albertobsd $ ./keyhunt -m bsgs -f tests/120.txt -b 120 -q -s 10 -S
[+] Version 0.2.211012 Chocolate ¡Beta!, developed by AlbertoBSD
[+] Quiet thread output
[+] Stats output every 10 seconds
[+] Mode BSGS secuential
[+] Opening file tests/120.txt
[+] Added 1 points from file
[+] Bit Range 120
[+] -- from : 0x800000000000000000000000000000
[+] -- to   : 0x1000000000000000000000000000000
[+] N = 0x100000000000
[+] Bloom filter for 4194304 elements : 14.00 MB
[+] Bloom filter for 209716 elements : 0.72 MB
[+] Allocating 3.00 MB for 209716 bP Points
[+] Reading bloom filter from file keyhunt_bsgs_3_4194304.blm .. Done!
[+] Reading bloom filter from file keyhunt_bsgs_1_209716.blm .. Done!
[+] Reading bP Table from file keyhunt_bsgs_2_209716.tbl .. Done!
^C] Total 1055531162664960 keys in 80 seconds: ~13 Tkeys/s (13194139533312 keys/s)
[+] Version 0.2.211007 Chocolate ¡Beta!, developed by AlbertoBSD
[+] Quiet thread output
[+] Stats output every 10 seconds
[+] Mode BSGS secuential
[+] Opening file tests/120.txt
[+] Added 1 points from file
[+] Bit Range 120
[+] -- from : 0x800000000000000000000000000000
[+] -- to   : 0x1000000000000000000000000000000
[+] N = 0x100000000000
[+] Bloom filter for 4194304 elements : 14.00 MB
[+] Bloom filter for 209716 elements : 0.72 MB
[+] Allocating 3.00 MB for 209716 bP Points
[+] Reading bloom filter from file keyhunt_bsgs_0_4194304.blm .. Done!
[+] Reading bloom filter from file keyhunt_bsgs_1_209716.blm .. Done!
[+] Reading bP Table from file keyhunt_bsgs_2_209716.tbl .. Done!
^C] Total 1178676464975872 keys in 80 seconds: ~14 Tkeys/s (14733455812198 keys/s)

Can you paste here your test case?

Best regards!

@SUN-2913
Copy link
Author

SUN-2913 commented Oct 14, 2021

It's strange, but I don't see such a speed difference right now. But I recreated the Bloom filter in the old and new versions.
I'll check it tomorrow on a more powerful computer.

Thanks.

$ ./keyhunt -m bsgs -t 4 -f tests/120.txt -n 1125899906842624 -s 10 -S -k 52 -r 800000000000000000000000000000:819999999999999999999999999999 -B random
[+] Version 0.2.211007 Chocolate ¡Beta!, developed by AlbertoBSD
[+] Threads : 4
[+] Stats output every 10 seconds
[+] K factor 52
[+] Mode BSGS random
[+] Opening file tests/120.txt
[+] Added 1 points from file
[+] Range
[+] -- from : 0x800000000000000000000000000000
[+] -- to : 0x819999999999999999999999999999
[+] N = 0x3ffffc8000000
[+] Bloom filter for 1744830464 elements : 5981.00 MB
[+] Bloom filter for 87241524 elements : 299.05 MB
[+] Allocating 1331.00 MB for 87241524 bP Points
[+] Reading bloom filter from file keyhunt_bsgs_0_1744830464.blm .. Done!
[+] Reading bloom filter from file keyhunt_bsgs_1_87241524.blm .. Done!
[+] Reading bP Table from file keyhunt_bsgs_2_87241524.tbl .. Done!
[+] Total 115967593633808384 keys in 10 seconds: ~11 Pkeys/s (11596759363380838
[+] Total 235312884169572352 keys in 20 seconds: ~11 Pkeys/s (11765644208478617
[+] Total 352406376770699264 keys in 30 seconds: ~11 Pkeys/s (11746879225689975
[+] Total 472877566273781760 keys in 40 seconds: ~11 Pkeys/s (11821939156844544
[+] Total 592222856809545728 keys in 50 seconds: ~11 Pkeys/s (11844457136190914
[+] Total 711568147345309696 keys in 60 seconds: ~11 Pkeys/s (11859469122421828
^C] Thread 0x804464b4082eb857a7178b6d84b3ad

$ ./keyhunt -m bsgs -t 4 -f tests/120.txt -n 1125899906842624 -s 10 -S -k 52 -r 800000000000000000000000000000:819999999999999999999999999999 -B random
[+] Version 0.2.211012 Chocolate ¡Beta!, developed by AlbertoBSD
[+] Threads : 4
[+] Stats output every 10 seconds
[+] K factor 52
[+] Mode BSGS random
[+] Opening file tests/120.txt
[+] Added 1 points from file
[+] Range
[+] -- from : 0x800000000000000000000000000000
[+] -- to : 0x819999999999999999999999999999
[+] N = 0x3ffffc8000000
[+] Bloom filter for 1744830464 elements : 5981.00 MB
[+] Bloom filter for 87241524 elements : 299.05 MB
[+] Allocating 1331.00 MB for 87241524 bP Points
[+] Reading bloom filter from file keyhunt_bsgs_3_1744830464.blm .. Done!
[+] Reading bloom filter from file keyhunt_bsgs_1_87241524.blm .. Done!
[+] Reading bP Table from file keyhunt_bsgs_2_87241524.tbl .. Done!
[+] Total 108086300862578688 keys in 10 seconds: ~10 Pkeys/s (10808630086257868
[+] Total 216172601725157376 keys in 20 seconds: ~10 Pkeys/s (10808630086257868
[+] Total 324258902587736064 keys in 30 seconds: ~10 Pkeys/s (10808630086257868
[+] Total 433471102417633280 keys in 40 seconds: ~10 Pkeys/s (10836777560440832
[+] Total 542683302247530496 keys in 50 seconds: ~10 Pkeys/s (10853666044950609
[+] Total 651895502077427712 keys in 60 seconds: ~10 Pkeys/s (10864925034623795
^C] Thread 0x813ed8bb220280f1de2ae67e4643b3

@hskun
Copy link

hskun commented Oct 15, 2021

here are the speed compare with JLP bsgs. All are single thread.

BSGS v1.2
BabyStep:0x1000000 (2^24.00)
Start:60000000000000
Stop :80000000000000
Keys :1
Number of CPU thread: 1
BabyStep Thread 0: 0x1 -> 0x1000000
[2.46 MKey/s][Cnt 2^24.00][06s][787.1MB]
Sort Thread 0: 00000000 -> 02000000
[60.80 MSort/s][Cnt 2^25.00][00s][787.1MB]
Warning, range is not a multiple of nbThread*1024
GiantStep Thread 0: 60000000000000
[3.57 MKey/s][Cnt 2^27.42][50s][787.1MB]
Key# 0 Pub: 0x0385A30D8413AF4F8F9E6312400F2D194FE14F02E719B24C3F83BF1FD233A8F963
Priv: 0x6ABE1F9B67E114

Done: Total time 58s

time ./keyhunt -m bsgs -t 1 -f tests/55.txt -r 60000000000000:80000000000000 -n 0x1000000000000 -s 0
[+] Version 0.2.211012 Chocolate ¡Beta!, developed by AlbertoBSD
[+] Thread : 1
[+] Turn off stats output
[+] Mode BSGS secuential
[+] Opening file tests/55.txt
[+] Added 1 points from file
[+] Range
[+] -- from : 0x60000000000000
[+] -- to : 0x80000000000000
[+] N = 0x1000000000000
[+] Bloom filter for 16777216 elements : 57.00 MB
[+] Bloom filter for 838861 elements : 2.88 MB
[+] Allocating 12.00 MB for 838861 bP Points
[+] processing 16777216/16777216 bP points : 100%
[+] Sorting 838861 elements... Done!
[+] Thread Key found privkey 6abe1f9b67e114
[+] Publickey 0385a30d8413af4f8f9e6312400f2d194fe14f02e719b24c3f83bf1fd233a8f963
All points were found

real 2m0.006s
user 1m59.191s
sys 0m0.070s

I use same number baby steps(2^24) to test.
It is about 2x slower than JLP BSGS.

@albertobsd
Copy link
Owner

albertobsd commented Oct 15, 2021

I use same number baby steps(2^24) to test. It is about 2x slower than JLP BSGS.

Nice test, here we are talking about other problem but let me develop your test a little more

BSGS has two things to test here, time in solve and memory usage.

My program 2 Minutes and 73 MB of RAM and the JLP program 1 minute but 787 MB of RAM, if I use that amount of RAM the program will be 10 times faster with the data loaded from file, even only using 146 MB the program will be 2 times faster.

Please considere this, an average user with 4 GB u 8 GB of RAM can get 10x times better speed with my code than the JLP code

The code quite similar in some parts but different in others for example use a Bloomfilter and he use a Hashtable.

That is why i add the option to save the precalculated data in a files to load it later and save time, with that option the time is very similar and the files can be use if you don't change the Baby Steps.

With files i get 1m5.159s and i'm keep using the 73 MB of RAM

time ./keyhunt -m bsgs -t 1 -f tests/55.txt -r 60000000000000:80000000000000 -n 0x1000000000000 -s 0 -q -S
[+] Version 0.2.211012 Chocolate ¡Beta!, developed by AlbertoBSD
[+] Thread : 1
[+] Turn off stats output
[+] Quiet thread output
[+] Mode BSGS secuential
[+] Opening file tests/55.txt
[+] Added 1 points from file
[+] Range
[+] -- from : 0x60000000000000
[+] -- to   : 0x80000000000000
[+] N = 0x1000000000000
[+] Bloom filter for 16777216 elements : 57.00 MB
[+] Bloom filter for 838861 elements : 2.88 MB
[+] Allocating 12.00 MB for 838861 bP Points
[+] Reading bloom filter from file keyhunt_bsgs_3_16777216.blm .. Done!
[+] Reading bloom filter from file keyhunt_bsgs_1_838861.blm .. Done!
[+] Reading bP Table from file keyhunt_bsgs_2_838861.tbl .. Done!
[+] Thread Key found privkey 6abe1f9b67e114
[+] Publickey 0385a30d8413af4f8f9e6312400f2d194fe14f02e719b24c3f83bf1fd233a8f963
All points were found

real    1m5.159s
user    1m5.078s
sys     0m0.080s

Using two times the current amount of RAM (~ 150 MB) and loading data from files only takes 30 seconds

time ./keyhunt -m bsgs -t 1 -f tests/55.txt -r 60000000000000:80000000000000 -n 0x1000000000000 -s 0 -q -S -k 2
[+] Version 0.2.211012 Chocolate ¡Beta!, developed by AlbertoBSD
[+] Thread : 1
[+] Turn off stats output
[+] Quiet thread output
[+] K factor 2
[+] Mode BSGS secuential
[+] Opening file tests/55.txt
[+] Added 1 points from file
[+] Range
[+] -- from : 0x60000000000000
[+] -- to   : 0x80000000000000
[+] N = 0x1000000000000
[+] Bloom filter for 33554432 elements : 115.00 MB
[+] Bloom filter for 1677722 elements : 5.75 MB
[+] Allocating 25.00 MB for 1677722 bP Points
[+] Reading bloom filter from file keyhunt_bsgs_3_33554432.blm .. Done!
[+] Reading bloom filter from file keyhunt_bsgs_1_1677722.blm .. Done!
[+] Reading bP Table from file keyhunt_bsgs_2_1677722.tbl .. Done!
[+] Thread Key found privkey 6abe1f9b67e114
[+] Publickey 0385a30d8413af4f8f9e6312400f2d194fe14f02e719b24c3f83bf1fd233a8f963
All points were found

real    0m34.224s
user    0m34.158s
sys     0m0.064s

Same amount of RAM of the JLP program (~725 MB) and loading data from files only takes 10 seconds

time ./keyhunt -m bsgs -t 1 -f tests/55.txt -r 60000000000000:80000000000000 -n 0x1000000000000 -s 0 -q -S -k 10
[+] Version 0.2.211012 Chocolate ¡Beta!, developed by AlbertoBSD
[+] Thread : 1
[+] Turn off stats output
[+] Quiet thread output
[+] K factor 10
[+] Mode BSGS secuential
[+] Opening file tests/55.txt
[+] Added 1 points from file
[+] Range
[+] -- from : 0x60000000000000
[+] -- to   : 0x80000000000000
[+] N = 0xfffffa000000
[+] Bloom filter for 167772160 elements : 575.00 MB
[+] Bloom filter for 8388608 elements : 28.76 MB
[+] Allocating 128.00 MB for 8388608 bP Points
[+] Reading bloom filter from file keyhunt_bsgs_3_167772160.blm .. Done!
[+] Reading bloom filter from file keyhunt_bsgs_1_8388608.blm .. Done!
[+] Reading bP Table from file keyhunt_bsgs_2_8388608.tbl .. Done!
[+] Thread Key found privkey 6abe1f9b67e114
[+] Publickey 0385a30d8413af4f8f9e6312400f2d194fe14f02e719b24c3f83bf1fd233a8f963
All points were found

real    0m10.609s
user    0m10.389s
sys     0m0.220s

Internally my program use the same code that JLP but i do others things to get a better speed in the long run

Best regards!

@hskun
Copy link

hskun commented Oct 15, 2021

I use same number baby steps(2^24) to test. It is about 2x slower than JLP BSGS.

Nice test, here we are talking about other problem but let me develop your test a little more

BSGS has two things to test here, time in solve and memory usage.

My program 2 Minutes and 73 MB of RAM and the JLP program 1 minute but 787 MB of RAM, if I use that amount of RAM the program will be 10 times faster with the data loaded from file, even only using 146 MB the program will be 2 times faster.

Please considere this, an average user with 4 GB u 8 GB of RAM can get 10x times better speed with my code than the JLP code

The code quite similar in some parts but different in others for example use a Bloomfilter and he use a Hashtable.

That is why i add the option to save the precalculated data in a files to load it later and save time, with that option the time is very similar and the files can be use if you don't change the Baby Steps.

With files i get 1m5.159s and i'm keep using the 73 MB of RAM

time ./keyhunt -m bsgs -t 1 -f tests/55.txt -r 60000000000000:80000000000000 -n 0x1000000000000 -s 0 -q -S
[+] Version 0.2.211012 Chocolate ¡Beta!, developed by AlbertoBSD
[+] Thread : 1
[+] Turn off stats output
[+] Quiet thread output
[+] Mode BSGS secuential
[+] Opening file tests/55.txt
[+] Added 1 points from file
[+] Range
[+] -- from : 0x60000000000000
[+] -- to   : 0x80000000000000
[+] N = 0x1000000000000
[+] Bloom filter for 16777216 elements : 57.00 MB
[+] Bloom filter for 838861 elements : 2.88 MB
[+] Allocating 12.00 MB for 838861 bP Points
[+] Reading bloom filter from file keyhunt_bsgs_3_16777216.blm .. Done!
[+] Reading bloom filter from file keyhunt_bsgs_1_838861.blm .. Done!
[+] Reading bP Table from file keyhunt_bsgs_2_838861.tbl .. Done!
[+] Thread Key found privkey 6abe1f9b67e114
[+] Publickey 0385a30d8413af4f8f9e6312400f2d194fe14f02e719b24c3f83bf1fd233a8f963
All points were found

real    1m5.159s
user    1m5.078s
sys     0m0.080s

Using two times the current amount of RAM (~ 150 MB) and loading data from files only takes 30 seconds

time ./keyhunt -m bsgs -t 1 -f tests/55.txt -r 60000000000000:80000000000000 -n 0x1000000000000 -s 0 -q -S -k 2
[+] Version 0.2.211012 Chocolate ¡Beta!, developed by AlbertoBSD
[+] Thread : 1
[+] Turn off stats output
[+] Quiet thread output
[+] K factor 2
[+] Mode BSGS secuential
[+] Opening file tests/55.txt
[+] Added 1 points from file
[+] Range
[+] -- from : 0x60000000000000
[+] -- to   : 0x80000000000000
[+] N = 0x1000000000000
[+] Bloom filter for 33554432 elements : 115.00 MB
[+] Bloom filter for 1677722 elements : 5.75 MB
[+] Allocating 25.00 MB for 1677722 bP Points
[+] Reading bloom filter from file keyhunt_bsgs_3_33554432.blm .. Done!
[+] Reading bloom filter from file keyhunt_bsgs_1_1677722.blm .. Done!
[+] Reading bP Table from file keyhunt_bsgs_2_1677722.tbl .. Done!
[+] Thread Key found privkey 6abe1f9b67e114
[+] Publickey 0385a30d8413af4f8f9e6312400f2d194fe14f02e719b24c3f83bf1fd233a8f963
All points were found

real    0m34.224s
user    0m34.158s
sys     0m0.064s

Same amount of RAM of the JLP program (~725 MB) and loading data from files only takes 10 seconds

time ./keyhunt -m bsgs -t 1 -f tests/55.txt -r 60000000000000:80000000000000 -n 0x1000000000000 -s 0 -q -S -k 10
[+] Version 0.2.211012 Chocolate ¡Beta!, developed by AlbertoBSD
[+] Thread : 1
[+] Turn off stats output
[+] Quiet thread output
[+] K factor 10
[+] Mode BSGS secuential
[+] Opening file tests/55.txt
[+] Added 1 points from file
[+] Range
[+] -- from : 0x60000000000000
[+] -- to   : 0x80000000000000
[+] N = 0xfffffa000000
[+] Bloom filter for 167772160 elements : 575.00 MB
[+] Bloom filter for 8388608 elements : 28.76 MB
[+] Allocating 128.00 MB for 8388608 bP Points
[+] Reading bloom filter from file keyhunt_bsgs_3_167772160.blm .. Done!
[+] Reading bloom filter from file keyhunt_bsgs_1_8388608.blm .. Done!
[+] Reading bP Table from file keyhunt_bsgs_2_8388608.tbl .. Done!
[+] Thread Key found privkey 6abe1f9b67e114
[+] Publickey 0385a30d8413af4f8f9e6312400f2d194fe14f02e719b24c3f83bf1fd233a8f963
All points were found

real    0m10.609s
user    0m10.389s
sys     0m0.220s

Internally my program use the same code that JLP but i do others things to get a better speed in the long run

Best regards!

Hi Albertobsd,
Thanks for your great program.
Yes, hashtable faster but use more ram.
So i perfer to use your program use bloom filter.
keep on fight :D

@albertobsd
Copy link
Owner

here are the speed compare with JLP bsgs. All are single thread.
I use same number baby steps(2^24) to test. It is about 2x slower than JLP BSGS.

Now i get what are you trying to say. well yes the difference form that time from one program to other is the bloom filter generation it take a little extra time generate it, that is where come from the extra time.

But the speed is more o less the same with the same baby step proof of that is in the readme where is i run the same target of 16 publickeys in the JLP readme

Amount of RAM used ~4.5 GB, time to solve the sixteen publickeys in the range of 64 bits key-space: 164 min (~2.7 hrs) using 6 threads

A litlle lest time and half of the memory.

Any way a think if we are getting something between 10 o 5 % less than the previous version, we still are getting 9x Times more speed than the keyhunt version from some 3 months ago, so i think this is OK.

But please someone post replicable example from speed reduction of the 50% from the previous version of keyhunt and this one

@albertobsd
Copy link
Owner

I just recover the 10% of lost speed.

@SUN-2913
Copy link
Author

But please someone post replicable example from speed reduction of the 50% from the previous version of keyhunt and this one

The problem could not be reproduced on other machines. Maybe it was something with the system or hardware in my case.
Anyway, thanks a lot for the keyhunt. At the moment, this is the top software in its category.

Best regards!

@SUN-2913
Copy link
Author

Off-topic question:
Alberto, do I need to recreate the bloom filter if I changed the search range and the base public key? (parameters k n unchanged)

@albertobsd
Copy link
Owner

Off-topic question: Alberto, do I need to recreate the bloom filter if I changed the search range and the base public key? (parameters k n unchanged)

No, you don't need to change the files, it is independent of the publickey, just if you change the n or k values the files are going to be created if you have the -S option

@SUN-2913 SUN-2913 changed the title Speed has decreased (BGSG mode) Speed has decreased Oct 22, 2021
@SUN-2913
Copy link
Author

SUN-2913 commented Oct 22, 2021

Hi, @albertobsd !
I found a problem with the speed in xpoint mode. There is a very big difference in speed in different versions.

user@AMD:~/Рабочий стол/keyhunt$ ./keyhunt -m xpoint -f tests/120_rec.txt -t 128 -r 0:5AF3107A4000

[+] Version 0.2.211012 Chocolate ¡Beta!, developed by AlbertoBSD
[+] Mode xpoint
[+] Threads : 128
[+] Opening file tests/120_rec.txt
[+] Allocating memory for 8000000001 elements: 152587.89 MB
[+] Bloom filter for 8000000001 elements.
[+] Loading data to the bloomfilter total: 27423.07 MB
[+] Bloomfilter completed
[+] Sorting data ... done! 8000000001 values were loaded and sorted
^Cse key: 1f01f12be2 in 4230 seconds: 974952 keys/s

user@AMD:~/Рабочий стол/keyhunt_old$ ./keyhunt -m xpoint -f tests/120_rec.txt -t 128 -r 0:5AF3107A4000
[+] Version 0.1.20210412 secp256k1
[+] Setting mode xpoint
[+] Setting 128 threads
[+] Opening file tests/120_rec.txt
[+] Allocating memory for 8000000001 elements: 152587.89 MB
[+] Initializing bloom filter for 8000000001 elements.
[+] Loading data to the bloomfilter total: 22852.56 MB
[+] Bloomfilter completed
[+] Sorting data ... done! 8000000001 values were loaded and sorted
Base key: 35016f2fcc
Base key: 6b02e0fb96 30 seconds: 100523485 keys/s
Base key: 48044f7bb9 60 seconds: 100995345 keys/s
Base key: 5605bf57ab 90 seconds: 101805078 keys/s
Base key: f072b03f2 120 seconds: 101895372 keys/s
Base key: 790898c788 150 seconds: 102145283 keys/s

@albertobsd
Copy link
Owner

Interesting i will open other issue about that problem, thanks for report it.

By the way the last update solve your speed problem in bsgs mode?

@albertobsd
Copy link
Owner

i think that this is solved now

@kpot87
Copy link

kpot87 commented Oct 29, 2021

I can say to @albertobsd that on version012 I have speed around 800pkeys from 018 till now speed increases to 1,8Ekeys(same parameter)

@nightwalker89
Copy link

nightwalker89 commented Nov 21, 2021

@albertobsd

Same command but my output is a bit different. Could you explain this diff?, is there any change in speed ? Thank you

time ./keyhunt -m bsgs -t 1 -f tests/55.txt -r 60000000000000:80000000000000 -n 0x1000000000000 -s 0 -q -S -k 10
[+] Version 0.2.211012 Chocolate ¡Beta!, developed by AlbertoBSD
[+] Thread : 1
[+] Turn off stats output
[+] Quiet thread output
[+] K factor 10
[+] Mode BSGS secuential
[+] Opening file tests/55.txt
[+] Added 1 points from file
[+] Range
[+] -- from : 0x60000000000000
[+] -- to : 0x80000000000000
[+] N = 0xfffffa000000
[+] Bloom filter for 167772160 elements : 575.00 MB
[+] Bloom filter for 8388608 elements : 28.76 MB
[+] Allocating 128.00 MB for 8388608 bP Points
[+] Reading bloom filter from file keyhunt_bsgs_3_167772160.blm .. Done!
[+] Reading bloom filter from file keyhunt_bsgs_1_8388608.blm .. Done!
[+] Reading bP Table from file keyhunt_bsgs_2_8388608.tbl .. Done!
[+] Thread Key found privkey 6abe1f9b67e114
[+] Publickey 0385a30d8413af4f8f9e6312400f2d194fe14f02e719b24c3f83bf1fd233a8f963
All points were found

real 0m10.609s
user 0m10.389s
sys 0m0.220s

My output:
Allocating is 2.00 MB

[+] Version 0.2.211117 SSE Trick or treat ¡Beta!, developed by AlbertoBSD
[+] Thread : 1
[+] Turn off stats output
[+] Quiet thread output
[+] K factor 10
[+] Mode BSGS secuential
[+] Opening file tests/55pub.txt
[+] Added 1 points from file
[+] Range
[+] -- from : 0x60000000000000
[+] -- to : 0x80000000000000
[+] N = 0xfffffa000000
[+] Bloom filter for 167772160 elements : 575.10 MB
[+] Bloom filter for 5242880 elements : 17.97 MB
[+] Bloom filter for 163840 elements : 0.88 MB
[+] Allocating 2.00 MB for 163840 bP Points
[+] processing 167772160/167772160 bP points : 100%
[+] Making checkums .. ... done
[+] Sorting 163840 elements... Done!
[+] Writing bloom filter to file keyhunt_bsgs_4_167772160.blm .... Done!
[+] Writing bloom filter to file keyhunt_bsgs_6_5242880.blm .... Done!
[+] Writing bP Table to file keyhunt_bsgs_2_163840.tbl .. Done!
[+] Writing bloom filter to file keyhunt_bsgs_7_163840.blm .... Done!
[+] Thread Key found privkey 6abe1f9b67e114
[+] Publickey 0385a30d8413af4f8f9e6312400f2d194fe14f02e719b24c3f83bf1fd233a8f963
All points were found

real 2m0.252s
user 3m51.257s
sys 0m0.878s

@albertobsd
Copy link
Owner

albertobsd commented Nov 21, 2021

Can you run the same command again? The last version remade some files so if you notice the b Points were processed again.

[+] processing 167772160/167772160 bP points : 100%

If youn run the same command again it will take less time, i guaranty that.

@nightwalker89
Copy link

nightwalker89 commented Nov 22, 2021

The different is
Allocating 2.00 MB for 163840 bP Points (Version 0.2.211117) vs Allocating 128.00 MB for 8388608 bP Points (Version 0.2.211012)
2M vs 128M.
Is this important?
I have pull and build from newest version: Version 0.2.211117

@albertobsd
Copy link
Owner

The new version use less memory

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants