Topic: VanitySearch (Yet another address prefix finder) - page 29. (Read 32072 times)

4Bk/s as in Billions? that's quite impressive. what is your rig consist of?

thx 4 .18 !

though having the same problem i had with cuda 10.2 when self compiled but this time with you'r realeased 18.exe (cuda 11 is installed and working fine)

-check all fine
prefix search all fine (though not testet over 50 prefixes)
searching very few adresses runs a while but even below 100 adresses:

VanitySearch v1.18
Search: 73 addresses (Lookup size 37,[1,7]) [Compressed or Uncompressed]
Start Tue Jun 23 13:24:08 2020
Base Key: Randomly changed every 44400 Mkeys
Number of CPU thread: 0
GPU: GPU #0 GeForce RTX 2080 Ti (68x64 cores) Grid(544x512)
[852.29 Mkey/s][GPU 852.29 Mkey/s][Total 2^31.67][Prob 0.0%][50% in 3.76903e+31y][Found 0]  GPUEngine: Launch: an illegal memory access was encountered

is there maybe some cuda environment setting i'm missing or havent set ?!

thx up front...

Hi,

why is the software failing when I am looking for more than 50 prefixes?
It looses speed dramatically. With my Rig I have 4 Bk/s and the speed goes as I increase the number of prefixes.
Can you please fix it? So that it doesnt matter if you are looking for 50 prefixes or 5 000 000. Otherwise oclvanitygen would be better for a large number of prefixes.....

I released the 1.18
- Port to CUDAv11
- Fixed wrong rare points

https://github.com/JeanLucPons/VanitySearch/releases

If you can compile the last release, you can do:

Priv: 0x1A838B13505B26867
How to translate into an understandable type type HuhHuhHuh
Private Key WIF
51 characters base58, starts with a '5'   5HscGG8iqA7YnZPN9ZEPdJSHVsb5zuUVST9XFB4M1tQUWUbFsh3
Private Key WIF Compressed
52 characters base58, starts with a 'K' or 'L'   KwUNeMo5dZDuJ5wiLmG6sDxbpSHT4acLXLQcVZPmLutcR3MHSHN3
Private Key Hexadecimal Format (64 characters [0-9A-F]):  078B13055AB016486AF996FCD19DBD8AD528BE1D4F014845BC1D1E06E7BE38A8

If you collected * bat * as the above program does not start, help correct and fix the ERROR.

@Konstanting2


First try this:

Kangaroo.exe -l  

If is says: GPU #0

Then try this command:

Kangaroo.exe -t 0 -d 14 -gpu -ws -w 65save.txt -wi 30 -o 64save.txt 65.txt


If it says: GPU #1

Then:

Kangaroo.exe -t 0 -d 14 -gpu -gpuId 1 -ws -w 65save.txt -wi 30 -o 64save.txt 65.txt




This thread is for VanitySearch, you may get more help if you post here:

Jean Luc  Kangaroo:


https://bitcointalksearch.org/topic/pollards-kangaroo-ecdlp-solver-5244940

 

Hello to all! To my questions, while there is no answer, help who can. I tried to compile the file myself, but it does not start, what did I do wrong? To output information to a separate file
Kangaroo.exe -t 0 -d 14 -gpu -gpuId 0 -w 65save.txt -wi 30 65.txt -o 64save.txt
save the kangaroo in a working file also did not start
Kangaroo.exe -t 0 -d 14 -gpu -gpuId 0 -w 65save.txt -wi 30 65.txt -ws:64save.txt

Kangaroo v1.9
Kangaroo [-v] [-t nbThread] [-d dpBit] [gpu] [-check]
         [-gpuId gpuId1[,gpuId2,...]] [-g g1x,g1y[,g2x,g2y,...]]
         inFile
 -v: Print version
 -gpu: Enable gpu calculation
 -gpuId gpuId1,gpuId2,...: List of GPU(s) to use, default is 0
 -g g1x,g1y,g2x,g2y,...: Specify GPU(s) kernel gridsize, default is 2*(MP),2*(Core/MP)
 -d: Specify number of leading zeros for the DP method (default is auto)
 -t nbThread: Secify number of thread
 -w workfile: Specify file to save work into (current processed key only)
 -i workfile: Specify file to load work from (current processed key only)
 -wi workInterval: Periodic interval (in seconds) for saving work
 -ws: Save kangaroos in the work file
 -wsplit: Split work file of server and reset hashtable
 -wm file1 file2 destfile: Merge work file
 -wmdir dir destfile: Merge directory of work files
 -wt timeout: Save work timeout in millisec (default is 3000ms)
 -winfo file1: Work file info file
 -m maxStep: number of operations before give up the search (maxStep*expected operation)
 -s: Start in server mode
 -c server_ip: Start in client mode and connect to server server_ip
 -sp port: Server port, default is 17403
 -nt timeout: Network timeout in millisec (default is 3000ms)
 -o fileName: output result to fileName
 -l: List cuda enabled devices
 -check: Check GPU kernel vs CPU
 inFile: intput configuration file

Please, if possible with examples of use. HELP!!!!
A few days ago I asked for help. After all, it’s not difficult for you. Thank you so much in advance !!!!!!!!

Are you planning to make the OpenGL version?

@arulbero unlock your PMs please.

Aaa, you mean Kangaroo program by Jean Luc? It is just an another approach to find private key which generates given address. Recently the discussion in the topic is mostly theoretical, how to improve algorithm. On github of this project Jean Luc mentioned some documents/papers which you may want to read to learn more about this way of solving problem.

isn't what we use VanitySearch for? Or by 'to generate key for address' you mean to generate private key for a given address?

To generate key for address with a given prefix. You may use it if you want to have a bitcoin address which starts with 1Shlomo ;-)

I'm still struggling to understand what exactly does this program do.
Have read the thread, it only created more confusion especially with those kangaroos.
Could anyone please explain it in a nutshell, what it's for?

This utility is to find the key when you know the public key. Next puzzle is #120 ~1 or 2 month on 256 Tesla V100
If you want to attack #64, consider using https://github.com/Telariust/VanitySearch-bitcrack or bitcrack

Doesn't this utility do that?
https://bitcointalksearch.org/topic/pollards-kangaroo-ecdlp-solver-5244940

Everybody wants to find the address from the puzzle 

Dear Jean Luc, please do a search --keyspace. You are a real programmer. You can do it. I ask you to. Hope to find the key with the program BitCrack lost(((  Want to find the address from the puzzle... 

People must have used a tool or script to create a so-called "Proof-of-Burn" address.
Those tools are designed to compute the checksum and the preferred remaining characters of your prefix.

Here's one example of Proof-of-Burn tool: https://gobittest.appspot.com/ProofOfBurn (wont work for long prefixes)

---

For the "combination", there's a checksum like they explained.
And the checksum is what makes addresses safe from typo errors just like when you changed one character of 1BitcoinEaterAddressDontSendf59kuE

Here's an easy understandable and reproducible example: (let's use 1BitcoinEatenAddressDontSendaBQGRD)

• 1. Address:                        1BitcoinEatenAddressDontSendaBQGRD
• 2. Base58 decode:              00759d6677091e973b7e390bf4ba0d30280f5e3abfa8c70cf0
• 3. Remove the checksum:   00759d6677091e973b7e390bf4ba0d30280f5e3abf
• 4. SHA256 of the above:     d820699ba4bf3c9ecf058677b48e6de5c8fb1a978cb837172dc0f14d181a5478
• 5. SHA256 of the above:     a8c70cf092774dccafc0ba609ada689a9be1d579e18af6aeee25d32f46272e41
• 6. Compare the checksum and first 4bytes of the above:  a8c70cf0  =  a8c70cf0

As you can see, any character from the address can't be changed without changing the last 4 bytes which is a SHA256d of the Base58 encoded data.
If you change at least one character, the checksum wont match that will make the address invalid.

If you use 1BitcoinEatenAddressDontSendf59kuE like your example, the checksum will not match.

• 1. Address:                        1BitcoinEatenAddressDontSendf59kuE
• 2. Base58 decode:              00759d6677091e973b7e390bf4ba0d30280f5e3ac0682bd8a1
• 3. Remove the checksum:   00759d6677091e973b7e390bf4ba0d30280f5e3ac0
• 4. SHA256 of the above:     fd7041a06bc30e9863de29ba2ea126d5db8fd0b2031160ff0becd23e0e912eec
• 5. SHA256 of the above:     71f7e0262d59454339013c08b5768ab0d8ccb203fe144d23ef02f4fef41a616e
• 6. Compare the checksum and first 4bytes of the above:  71f7e026  ≠  682bd8a1

In this case, the address is invalid.