Keyhunt - development requests - bug reports - page 4.

ccinet

newbie

Activity: 33

Merit: 0

Quote from: AndrewWeb on March 08, 2024, 07:03:13 PM

Quote from: ccinet on March 08, 2024, 06:49:35 PM

Quote from: AndrewWeb on March 08, 2024, 06:17:42 PM

Ok, I made a 65.txt file in folder keyhunt and used this code

./keyhunt -m bsgs -f 65.txt -r 1a830000000000000

It found the puzzel 65 privatkey right away. I can see it in the file KEYFOUNDKEYFOUND.txt

brilliant!

Could you explain why you just have a part of the puzzle 32 address here ?

./keyhunt -m vanity -r AB958105:C52F1A9F -R -v 1FRoHA9xew -l compress -t 4 -e -n 0x400

It is intended for custom addresses like 1Magni1 but the rest of the public address is not known

AndrewWeb

jr. member

Activity: 43

Merit: 1

Quote from: ccinet on March 08, 2024, 06:49:35 PM

Quote from: AndrewWeb on March 08, 2024, 06:17:42 PM

Ok, I made a 65.txt file in folder keyhunt and used this code

./keyhunt -m bsgs -f 65.txt -r 1a830000000000000

It found the puzzel 65 privatkey right away. I can see it in the file KEYFOUNDKEYFOUND.txt

brilliant!

Could you explain why you just have a part of the puzzle 32 address here ?

./keyhunt -m vanity -r AB958105:C52F1A9F -R -v 1FRoHA9xew -l compress -t 4 -e -n 0x400

ccinet

newbie

Activity: 33

Merit: 0

Quote from: AndrewWeb on March 08, 2024, 06:17:42 PM

Ok, I made a 65.txt file in folder keyhunt and used this code

./keyhunt -m bsgs -f 65.txt -r 1a830000000000000

It found the puzzel 65 privatkey right away. I can see it in the file KEYFOUNDKEYFOUND.txt

brilliant!

AndrewWeb

jr. member

Activity: 43

Merit: 1

Ok, I made a 65.txt file in folder keyhunt and used this code

./keyhunt -m bsgs -f 65.txt -r 1a830000000000000

It found the puzzel 65 privatkey right away. I can see it in the file KEYFOUNDKEYFOUND.txt

ccinet

newbie

Activity: 33

Merit: 0

Quote from: AndrewWeb on March 08, 2024, 05:19:56 PM

Quote from: ccinet on March 08, 2024, 05:15:26 PM

Quote from: ?? on ??

Quote from: citb0in on March 08, 2024, 03:54:08 PM

RTFM ?
do a test with lower key and see what happens?

Found it !

"FAQ

Where the privatekeys will be saved? R: In a file called KEYFOUNDKEYFOUND.txt"

Exact. KEYFOUNDKEYFOUND.tx
what did you find? the puzzle 130? Grin

Not yet

Give me a code to do a test with lower key.

There is no such thing as that, if you want to narrow the range you should look at (2^130)-(2^129) or 680564733841876926926749214863536422913,
the lucky number can be randomly anywhere in that range.
The problem is that 0.0000000001% of the range is 68056473384187692692674921486.
There are still more grains of sand there than there are on all the beaches in the world combined. Cry

AndrewWeb

jr. member

Activity: 43

Merit: 1

Quote from: ccinet on March 08, 2024, 05:15:26 PM

Quote from: ?? on ??

Quote from: citb0in on March 08, 2024, 03:54:08 PM

RTFM ?
do a test with lower key and see what happens?

Found it !

"FAQ

Where the privatekeys will be saved? R: In a file called KEYFOUNDKEYFOUND.txt"

Exact. KEYFOUNDKEYFOUND.tx
what did you find? the puzzle 130? Grin

Not yet

Give me a code to do a test with lower key.

ccinet

newbie

Activity: 33

Merit: 0

Quote from: ?? on ??

Quote from: citb0in on March 08, 2024, 03:54:08 PM

RTFM ?
do a test with lower key and see what happens?

Found it !

"FAQ

Where the privatekeys will be saved? R: In a file called KEYFOUNDKEYFOUND.txt"

Exact. KEYFOUNDKEYFOUND.tx
what did you find? the puzzle 130? Grin

AndrewWeb

jr. member

Activity: 43

Merit: 1

Quote from: ccinet on March 08, 2024, 04:25:16 PM

Quote from: AndrewWeb on March 08, 2024, 03:36:59 PM

Quote from: ccinet on March 08, 2024, 01:56:07 PM

Quote from: AndrewWeb on March 08, 2024, 09:18:08 AM

Ok, I installed Keyhunt on Bodhi Linux 7.0 copied file 130.txt from folder test to folder keyhunt and executed ./keyhunt -m bsgs -f 130.txt -b 130 -R

When it finds the key, will it create a file with the found key in the keyhunt folder ? Like the file VANITYKEYFOUND.txt in the keyhunt folder ?

./keyhunt -m bsgs -f 130.txt -b 130 -R You're going to need luck Roll Eyes

The VANITYKEYFOUND.txt file is generated only when the hunter finds a key in vanity mode.

Yes I understand that. But will it generate KEYFOUND.txt in bsgs mode ?

Try puzzle 32 near the key to see how it works

./keyhunt -m vanity -r AB958105:C52F1A9F -R -v 1FRoHA9xew -l compress -t 4 -e -n 0x400

Isn't that vanity mode ? Do you have a code for bsgs mode ? that will find a key right away.

BTW: your vanity code found 32. I can see it in the file VANITYKEYFOUND.txt

Quote from: citb0in on March 08, 2024, 03:54:08 PM

RTFM ?
do a test with lower key and see what happens?

Found it !

"FAQ

Where the privatekeys will be saved? R: In a file called KEYFOUNDKEYFOUND.txt"

ccinet

newbie

Activity: 33

Merit: 0

Quote from: AndrewWeb on March 08, 2024, 03:36:59 PM

Quote from: ccinet on March 08, 2024, 01:56:07 PM

Quote from: AndrewWeb on March 08, 2024, 09:18:08 AM

Ok, I installed Keyhunt on Bodhi Linux 7.0 copied file 130.txt from folder test to folder keyhunt and executed ./keyhunt -m bsgs -f 130.txt -b 130 -R

When it finds the key, will it create a file with the found key in the keyhunt folder ? Like the file VANITYKEYFOUND.txt in the keyhunt folder ?

./keyhunt -m bsgs -f 130.txt -b 130 -R You're going to need luck Roll Eyes

The VANITYKEYFOUND.txt file is generated only when the hunter finds a key in vanity mode.

Yes I understand that. But will it generate KEYFOUND.txt in bsgs mode ?

Try puzzle 32 near the key to see how it works

./keyhunt -m vanity -r AB958105:C52F1A9F -R -v 1FRoHA9xew -l compress -t 4 -e -n 0x400

citb0in

hero member

Activity: 630

Merit: 731

Bitcoin g33k

RTFM ?
do a test with lower key and see what happens?

AndrewWeb

jr. member

Activity: 43

Merit: 1

Quote from: ccinet on March 08, 2024, 01:56:07 PM

Quote from: AndrewWeb on March 08, 2024, 09:18:08 AM

Ok, I installed Keyhunt on Bodhi Linux 7.0 copied file 130.txt from folder test to folder keyhunt and executed ./keyhunt -m bsgs -f 130.txt -b 130 -R

When it finds the key, will it create a file with the found key in the keyhunt folder ? Like the file VANITYKEYFOUND.txt in the keyhunt folder ?

./keyhunt -m bsgs -f 130.txt -b 130 -R You're going to need luck Roll Eyes

The VANITYKEYFOUND.txt file is generated only when the hunter finds a key in vanity mode.

Yes I understand that. But will it generate KEYFOUND.txt in bsgs mode ?

ccinet

newbie

Activity: 33

Merit: 0

Quote from: AndrewWeb on March 08, 2024, 09:18:08 AM

Ok, I installed Keyhunt on Bodhi Linux 7.0 copied file 130.txt from folder test to folder keyhunt and executed ./keyhunt -m bsgs -f 130.txt -b 130 -R

When it finds the key, will it create a file with the found key in the keyhunt folder ? Like the file VANITYKEYFOUND.txt in the keyhunt folder ?

./keyhunt -m bsgs -f 130.txt -b 130 -R You're going to need luck Roll Eyes

The VANITYKEYFOUND.txt file is generated only when the hunter finds a key in vanity mode.

AndrewWeb

jr. member

Activity: 43

Merit: 1

Ok, I installed Keyhunt on Bodhi Linux 7.0 copied file 130.txt from folder test to folder keyhunt and executed ./keyhunt -m bsgs -f 130.txt -b 130 -R

When it finds the key, will it create a file with the found key in the keyhunt folder ? Like the file VANITYKEYFOUND.txt in the keyhunt folder ?

albert0bsd

hero member

Activity: 861

Merit: 662

Quote from: GTX1060x2 on March 04, 2024, 11:31:06 AM

Added Vanity search : 13zb1hQ
...
Vanity Private Key: fffffffffffffffffffffffffffffffebaaedce6af48a0380b2513a178946f75
...

First if you are going to use vanity use more than 15 characters not just 7 or 8.

Seconds yes that key is outside of the range because keythunt for address/rmd160/xpoint search on both sides of the curve it do this because if I only seach for one side of the curve the performance would be lesst than the half of it ( It will have less than the half of the current speed ).

It think on this like a feature not a bug... so please use more than 15 characers for your vanity search.

Quote from: albert0bsd on March 05, 2024, 12:05:40 PM

Quote from: GTX1060x2 on March 04, 2024, 11:31:06 AM

Added Vanity search : 13zb1hQ
...
Vanity Private Key: fffffffffffffffffffffffffffffffebaaedce6af48a0380b2513a178946f75
...

First if you are going to use vanity use more than 15 characters not just 7 or 8.

Seconds yes that key is outside of the range because keythunt for address/rmd160/xpoint search on both sides of the curve it do this because if I only seach for one side of the curve the performance would be lesst than the half of it ( It will have less than the half of the current speed ).

It think on this like a feature not a bug... so please use more than 15 characers for your vanity search.

Quote from: Ra al Ghul on March 04, 2024, 09:58:08 PM

Alberto is a Legend would love to meet him one day

Its not a big deal, I am just another random guy with regular life problems

satashi_nokamato

jr. member

Activity: 47

Merit: 2

Quote from: ccinet on March 04, 2024, 03:26:37 PM

Quote from: GTX1060x2 on March 04, 2024, 11:31:06 AM

Code:

./keyhunt -m vanity -l compress -r 30000000000000000:3ffffffffffffffff -R -v 13zb1hQ -n 0x6000000 -q -s 10 -t4
[+] Mode vanity
[+] Search compress only
[+] Random mode
[+] Added Vanity search : 13zb1hQ
[+] Quiet thread output
[+] Stats output every 10 seconds
[+] Threads : 4
[+] N = 0x6000000
[+] Range 
[+] -- from : 0x30000000000000000
[+] -- to   : 0x3ffffffffffffffff
[+] Bloom filter for 1 elements.
[+] Loading data to the bloomfilter total: 0.03 MB
[+] Total 5566996480 keys in 310 seconds: ~17 Mkeys/s (17958053 keys/s)
Vanity Private Key: fffffffffffffffffffffffffffffffebaaedce6af48a0380b2513a178946f75
pubkey: 03b32edf683e27c1c866c915f093c3e88d4dbedbb81cc48e5f7355dbfd731ab8ba
Address 13zb1hQVwAhBbaDUusG6ogrq3ZnN1WJy5w
rmd160 20d45a6a6f3f0f3f3fbf3d6d7ba46818b1dc1d5c

The first number in the range is greater than the second, it seems that this caused abnormal operation.
Strange Huh

Your key is still in the given range if you subtract it from N, you will see this one

Code:

0x000000000000000000000000000000000000000000000003b4ad4aeb57a1d1cc
Public_key=
02b32edf683e27c1c866c915f093c3e88d4dbedbb81cc48e5f7355dbfd731ab8ba
Compressed_address=
1N2DPnTjPep2ZWr9JwCGFzAJF39xkspPMc

You should read the instructions about how to use -N value to avoid going out of range.

Ra al Ghul

newbie

Activity: 2

Merit: 0

Alberto is a Legend would love to meet him one day

ccinet

newbie

Activity: 33

Merit: 0

Quote from: GTX1060x2 on March 04, 2024, 11:31:06 AM

Code:

./keyhunt -m vanity -l compress -r 30000000000000000:3ffffffffffffffff -R -v 13zb1hQ -n 0x6000000 -q -s 10 -t4
[+] Mode vanity
[+] Search compress only
[+] Random mode
[+] Added Vanity search : 13zb1hQ
[+] Quiet thread output
[+] Stats output every 10 seconds
[+] Threads : 4
[+] N = 0x6000000
[+] Range 
[+] -- from : 0x30000000000000000
[+] -- to   : 0x3ffffffffffffffff
[+] Bloom filter for 1 elements.
[+] Loading data to the bloomfilter total: 0.03 MB
[+] Total 5566996480 keys in 310 seconds: ~17 Mkeys/s (17958053 keys/s)
Vanity Private Key: fffffffffffffffffffffffffffffffebaaedce6af48a0380b2513a178946f75
pubkey: 03b32edf683e27c1c866c915f093c3e88d4dbedbb81cc48e5f7355dbfd731ab8ba
Address 13zb1hQVwAhBbaDUusG6ogrq3ZnN1WJy5w
rmd160 20d45a6a6f3f0f3f3fbf3d6d7ba46818b1dc1d5c

The first number in the range is greater than the second, it seems that this caused abnormal operation.
Strange Huh

albert0bsd

hero member

Activity: 861

Merit: 662

Quote from: whanau on March 04, 2024, 01:27:40 PM

In the post:
Range
-- from : 0x1
-- to : 0xfffffffffffffffffffffffffffffffebaaedce6af48a03bbfd25e8cd0364141

And what you expected? found the key in seconds?

Genius...... That is the whole range if there is a program to found a key in seconds the bitcoin and all alt-coins will worth ZERO

Please don't ask stupid questions here

whanau

member

Activity: 118

Merit: 30

Quote from: albert0bsd on March 04, 2024, 10:06:59 AM

Quote from: whanau on March 03, 2024, 09:45:23 PM

Bug?

Where in the command do you set the range?

Roll Eyes

In the post:
Range
-- from : 0x1
-- to : 0xfffffffffffffffffffffffffffffffebaaedce6af48a03bbfd25e8cd0364141

also I tried
./keyhunt -m xpoint -f testkey.txt -r 1:100

Version 0.2.230519 Satoshi Quest, developed by AlbertoBSD
Mode xpoint
N = 0x100000000
Range
-- from : 0x1
-- to : 0x100
Allocating memory for 1 elements: 0.00 MB
Bloom filter for 1 elements.
Loading data to the bloomfilter total: 0.03 MB
Sorting data ... done! 1 values were loaded and sorted

^C] Total 218610688 keys in 30 seconds: ~7 Mkeys/s (7287022 keys/s)

Thank you for your help

GTX1060x2

newbie

Activity: 5

Merit: 1

Code:

./keyhunt -m vanity -l compress -r 30000000000000000:3ffffffffffffffff -R -v 13zb1hQ -n 0x6000000 -q -s 10 -t4
[+] Mode vanity
[+] Search compress only
[+] Random mode
[+] Added Vanity search : 13zb1hQ
[+] Quiet thread output
[+] Stats output every 10 seconds
[+] Threads : 4
[+] N = 0x6000000
[+] Range 
[+] -- from : 0x30000000000000000
[+] -- to   : 0x3ffffffffffffffff
[+] Bloom filter for 1 elements.
[+] Loading data to the bloomfilter total: 0.03 MB
[+] Total 5566996480 keys in 310 seconds: ~17 Mkeys/s (17958053 keys/s)
Vanity Private Key: fffffffffffffffffffffffffffffffebaaedce6af48a0380b2513a178946f75
pubkey: 03b32edf683e27c1c866c915f093c3e88d4dbedbb81cc48e5f7355dbfd731ab8ba
Address 13zb1hQVwAhBbaDUusG6ogrq3ZnN1WJy5w
rmd160 20d45a6a6f3f0f3f3fbf3d6d7ba46818b1dc1d5c

Topic: Keyhunt - development requests - bug reports - page 4. (Read 11879 times)