Ninjastic
Search content
Sort by
Showing 6 of 6 results by De_Freedom
Post
Topic
Board Development & Technical Discussion
Re: Pollard's kangaroo ECDLP solver
by
De_Freedom
on 20/03/2024, 16:22:01 UTC
WanderingPhilospher thanks for your answer.

To succeed with further puzzles we definitely need an upgrade in tools, something combining different algorithms in one search also a pooling idea to eliminate already scanned ranges. 
Post
Topic
Board Development & Technical Discussion
Re: Pollard's kangaroo ECDLP solver
by
De_Freedom
on 10/03/2024, 09:46:03 UTC
I probably miss something here, but please explain why do you guys use Kangaroo while there is another tool Keyhunt, which BSGS option is very very fast. With above average hardware, you can get around 10 exa keys per second. That is 10,000,000,000,000,000,000 keys per second.  I have never seen such numbers with Kangaroo.
Post
Topic
Board Project Development
Re: Keyhunt - development requests - bug reports
by
De_Freedom
on 01/03/2024, 13:03:33 UTC
Thanks, regarding vanity, speed is slightly better for me than address mode.
Post
Topic
Board Project Development
Re: Keyhunt - development requests - bug reports
by
De_Freedom
on 01/03/2024, 12:25:36 UTC
I have tried Vanity search with range specified and it has found address that is out of range:

Code:
./keyhunt -m vanity -f tests/van.txt -l compress -R -b 66 -e -s 10 -q -t 32 -n 0x400000000000
[+] Version 0.2.230519 Satoshi Quest, developed by AlbertoBSD
[+] Mode vanity
[+] Search compress only
[+] Random mode
[+] Endomorphism enabled
[+] Stats output every 10 seconds
[+] Quiet thread output
[+] Threads : 32
[+] N = 0x400000000000
[+] Bit Range 66
[+] -- from : 0x20000000000000000
[+] -- to   : 0x40000000000000000
[+] Bloom filter for 1 elements.
[+] Loading data to the bloomfilter total: 0.03 MB
[+] Total 488007616512 keys in 3320 seconds: ~146 Mkeys/s (146990245 keys/s)
Vanity Private Key: 164ddd867ec35f2e98f582c4d0d737f56f10d6a3cd2be340adf436912436f49
pubkey: 03cb9c45ef630131d33cf1e0b062165cea96a2cc3daf89448063180f48ad11d7ce
Address 13zb1hQbAP3nYzCWptx59aR1qG7J4UCY6h
rmd160 20d45a6a75b7519bfed7f99e576f1acd0aad1428
[+] Total 896877281280 keys in 6110 seconds: ~146 Mkeys/s (146788425 keys/s)

Post
Topic
Board Project Development
Re: Keyhunt - development requests - bug reports
by
De_Freedom
on 17/01/2024, 14:02:31 UTC
Thanks WanderingPhilospher. But oh my god, we stand no chance to crack 130 puzzle any time soon.
Post
Topic
Board Project Development
Re: Keyhunt - development requests - bug reports
by
De_Freedom
on 17/01/2024, 11:37:22 UTC
Hello, I tried to calculate (using AI help) and I get that at 48 exa keys per second the range will be completed shortly. Where is the mistake?

(2^130 - 1) - 2^129

2^130 is 340282366920938463463374607431768211456

Subtracting 1 gives us:

340282366920938463463374607431768211455

2^129 is 170141183460469231731687303715884105728

Subtracting the start from the end:

340282366920938463463374607431768211455 - 170141183460469231731687303715884105728

= 170,141,183,460,469,231,731,687,303,715,884,105,727

Total keys / Keys scanned per second

170,141,183,460,469,231,731,687,303,715,884,105,727 / 48,000,000,000,000,000,000

= 3,542 seconds


Quote from: 1qaz on November 07, 2023, 10:16:40 PM
Quote from: GR Sasa on November 07, 2023, 09:39:24 AM
Quote from: MrlostinBTC on November 05, 2023, 01:22:44 PM
Bsgs is now holding 18 exa keys/s stable.

Running a program to searches 18 exa keys/s is impressive!

I have 16 GB and Core i7, and get only 70 Peta key/s  

18 ExKeys/s this is a drop in the ocean, the range is huge, brute force is currently not the best choice for solving the puzzle. Even if random is not a very good idea, you need to look for another approach

P.s.
https://i.ibb.co/pfR0VDp/2023-11-08-00-14-18.png