Vanitygen: Vanity bitcoin address generator/miner [v0.22] - page 10.

nc50lc

legendary

Activity: 2534

Merit: 6080

Self-proclaimed Genius

Quote from: ?? on ??

So i bump into Bitcoin Collider https://www.reddit.com/r/Bitcoin/comments/655j0r/large_bitcoin_collider_tried_over_3000_trillion/ on reddit & discover its members consider using FPGA for better performance, this is the first time i heard of this device. If we run their program or vanitygen on it, how many keys/s can it archived?

Some examples of FPGAs are FPGA mining cards which is mainly used for mining and as far as I know LBC was optimized (if not the old versions, the latest) to use it efficiently.
On the other hand, Vanitygen is optimized for Processors while Oclvanitygen is optimized for GPUs, I don't know if it will run with FPGA either.

So the answer would be obvious.
But there are forks that have different tweaks supporting different type of devices (even FPGAs)

manhquang2206

newbie

Activity: 3

Merit: 0

Does anybody know how to modify this?
I found a post on bitcoin stackexchange show how to create a bitcoin address from given hex private key

In vanitygen.c

Replace

Code:

EC_KEY_generate_key(pkey);

with

Code:

BIGNUM *res;
   BN_init(&start);
   res = &start;
   BN_hex2bn(&res, "3B1BCC5A67F38853810972B1DA8A67148FAD78C6CD6F22B2C823D141BE59C81C"); //Set up hex private key
   vg_set_privkey(res, pkey);

& remove case

Code:

if (++npoints >= rekey_at)

I intend to replace the input hex private key with function like hashcat to recover lost pivate key like this

Code:

"?1?1?1?1?1?1?1"+"A67F38853810972B1DA8A67148FAD78C6CD6F22B2C823D141BE59C81C"

When i test it on a single hex private key,by default the function keep multiply the key for new address instead of keep try new key completely, if i change it to my given function, it maybe took awhile for the application to generate new key again & the code doesn't even use 100% cpu power, there're no further instruction in the post. Is anybody know to how to adjust the code to check address from mutiple generated key without multiply it. If possible, the performance will stay around like original code or at least decline to 1-20 times, i wouldn't mind that. Thank You

ABCbits

legendary

Activity: 2870

Merit: 7490

Crypto Swap Exchange

Quote from: LoyceV on January 17, 2019, 04:38:03 AM

Quote from: ABCbits on January 15, 2019, 12:55:53 PM

Quote from: elda34b on January 15, 2019, 08:01:11 AM

Quote from: ?? on ??

Have anybody try to run vanitygen on Google's TPU cloud machine or any HPC service? What's the best keysearch rates has it archive so far? Huh

Why would you run it online? It is risky to do that because your data could be intercepted.
You should run vanitygen offline on a secure computer. Using OpenCL is fast enough for me.

I think his point is Google's TPU or HPU can generate vanity address at faster rate. While it's true that the information could be intercepted, using encrypted connection could solve the problem.

Using split key is a much better solution, so that Google itself can't know your private key either. They can still know you generated the address through.

I totally forget about split key. But google knowing user generate vanity address doesn't matter unless you could know bitcoin address just from partial private key, brute force to get private from an address with partial private key or have serious privacy concern.

LoyceV

legendary

Activity: 3290

Merit: 16489

Thick-Skinned Gang Leader and Golden Feather 2021

Quote from: ABCbits on January 15, 2019, 12:55:53 PM

Quote from: elda34b on January 15, 2019, 08:01:11 AM

Quote from: ?? on ??

Have anybody try to run vanitygen on Google's TPU cloud machine or any HPC service? What's the best keysearch rates has it archive so far? Huh

Why would you run it online? It is risky to do that because your data could be intercepted.
You should run vanitygen offline on a secure computer. Using OpenCL is fast enough for me.

I think his point is Google's TPU or HPU can generate vanity address at faster rate. While it's true that the information could be intercepted, using encrypted connection could solve the problem.

Using split key is a much better solution, so that Google itself can't know your private key either. They can still know you generated the address through.

elda34b

sr. member

Activity: 910

Merit: 351

Quote from: ?? on ??

Just want to find out how fast vanitygen can go, hashcat release benchmark & performance of lastest GPU card all the time, i usually use vanitygen to test my GPU card max performance when my family's internet cafe buy a new PC. I always wonder with these days strongest hardware, have we archive the speed of 1bil or even 1 trillion keys/s? Huh

I see. I'm not so sure about the speed but I really doubt we reach that point. 1 billion keys/sec is crazy.
At this moment I can't find the result on the internet either, so your best choice would be to try it out yourself.

ABCbits

legendary

Activity: 2870

Merit: 7490

Crypto Swap Exchange

Quote from: elda34b on January 15, 2019, 08:01:11 AM

Quote from: ?? on ??

Have anybody try to run vanitygen on Google's TPU cloud machine or any HPC service? What's the best keysearch rates has it archive so far? Huh

Why would you run it online? It is risky to do that because your data could be intercepted.
You should run vanitygen offline on a secure computer. Using OpenCL is fast enough for me.

I think his point is Google's TPU or HPU can generate vanity address at faster rate. While it's true that the information could be intercepted, using encrypted connection could solve the problem.

But Google's TPU is optimized for AI stuff (deep learning, neural network, machine learning, etc.).

elda34b

sr. member

Activity: 910

Merit: 351

Quote from: ?? on ??

Have anybody try to run vanitygen on Google's TPU cloud machine or any HPC service? What's the best keysearch rates has it archive so far? Huh

Why would you run it online? It is risky to do that because your data could be intercepted.
You should run vanitygen offline on a secure computer. Using OpenCL is fast enough for me.

gembitz

hero member

Activity: 1834

Merit: 639

*Brute force will solve any Bitcoin problem*

Quote from: aarons6 on January 10, 2019, 04:54:47 AM

Quote from: PietCoin97 on January 09, 2019, 05:59:15 PM

for now i will find nothing becuase the tool wont work for me at the moment

but i say you one collega found with this method 7 Addresses

restart every 30 min It's all just possibility and probability

there is zero chance your friend brute forced an entire btc address..

you are just wasting your time.

chuck norris comes to mind Cool

hehe

88nE6w2xfri6izL1Xx239ELXb

newbie

Activity: 3

Merit: 0

If someone interested in deep conversation about vanitygen and math,
welcome to subreddit I created recently.

https://www.reddit.com/r/vanitygen/

KingZee

sr. member

Activity: 938

Merit: 452

Check your coin privilege

Quote from: PietCoin97 on January 10, 2019, 05:58:10 PM

yeah i know that i dont use it anymore.

In case you try to do this in the future again, dont use half patterns.. The difference between 10^-80 and 10^-60 is almost inexistent, youre better off searching for full patterns rather than maybe landing on a close relative to your address.

PietCoin97

jr. member

Activity: 91

Merit: 3

yeah i know that i dont use it anymore.

aarons6

legendary

Activity: 1736

Merit: 1006

Quote from: PietCoin97 on January 09, 2019, 05:59:15 PM

for now i will find nothing becuase the tool wont work for me at the moment

but i say you one collega found with this method 7 Addresses

restart every 30 min It's all just possibility and probability

there is zero chance your friend brute forced an entire btc address..

you are just wasting your time.

xhomerx10

legendary

Activity: 3808

Merit: 7912

Quote from: PietCoin97 on January 09, 2019, 05:59:15 PM

for now i will find nothing becuase the tool wont work for me at the moment

but i say you one collega found with this method 7 Addresses

restart every 30 min It's all just possibility and probability

Dude. Seriously. There are

Code:

115792089237316195423570985008687907852837564279074904382605163141518161494336

possible Bitcoin addresses and you you are looking randomly for 6 million? Have you done the math?

Code:

115792089237316195423570985008687907852837564279074904382605163141518161494336 divided by 6 million=
19,298,681,539,552,699,237,261,830,834,781,317,975,472,927,379,845,817,397,100,860,523,586,360.249056

Stop. You look silly. I wager one colleague is a liar.

PietCoin97

jr. member

Activity: 91

Merit: 3

for now i will find nothing becuase the tool wont work for me at the moment

but i say you one collega found with this method 7 Addresses

restart every 30 min It's all just possibility and probability

LoyceMobile

hero member

Activity: 1659

Merit: 687

LoyceV on the road. Or couch.

So, in about 100000000000000 years you may find one, only to realize you're still a few digits short.

PietCoin97

jr. member

Activity: 91

Merit: 3

Quote from: xhomerx10 on January 09, 2019, 07:24:02 AM

Quote from: PietCoin97 on January 01, 2019, 05:37:13 PM

ok so i remove the Safe mode

I start with

Code:

./oclvanitygen -k -D 0:0 -D 0:1 -D 0:2 -D 0:3 -D 0:4 -o found.txt -f 6MIOPattern -s seed
Read 77 bytes from RNG seed file

Next match difficulty: 719170320814992132724345727918 (5999998 prefixes)
[183.69 Mkey/s][total 1069547520][Prob 0.0%][50% in 8.605509e+13y] Match idx: 6082822
CPU hash: 8e824fbbdf941ecd859e1da587e4fa0b563f13ef
GPU hash: 3b4df4363caa9e3bd9da58020d3080be8230a4ae
Found delta: 15727901 Start delta: 31457281
[179.43 Mkey/s][total 6464471040][Prob 0.0%][50% in 8.809719e+13y]

and get always the same hash 3b4df4363caa9e3bd9da58020d3080be8230a4ae

so how do you search ?

Are you trying to load a file that contains 6 million patterns to search for?

Can you give us a small sample of the patterns from your file?

of course these are the pattern the first 23 digits from all funded addresses

Code:

16rCmCmbuWDhPjWTrpQGaU3
183hmJGRuTEi2YDCWy5iozY
1FeexV6bAHb8ybZjqQMjJrc
1HQ3Go3ggs8pFnXuHVHRytP
18rnfoQgGo1HqvVQaAN4Qnx
1LdRcdxfbSnmCYYNdeYpUnz
1JCe8z4jJVNXSjohjM4i9Hh
1AC4fMwgY8j9onSbXEWeH6Z
12YygZpCEC8VED2oSMQdWCq
18mkjbVaHAcMauL6iiy7zm9
17hf5H8D6Yc4B7zHEg3orAt
13JQwoSLLR3ffXwswe2HCTK
12ib7dApVFvg82TXKycWBNp
12tkqA9xSoowkzoERHMWNKs
1AnwDVbwsLBVwRfqN2x9Eo4
14eQD1QQb8QFVG8YFwGz7sk
16FSBGvQfy4K8dYvPPWWpmz
17rm2dvb439dZqyMe2d4D6A
1Cr7EjvS8C7gfarREHCvFhd
1PeizMg76Cf96nUQrYg8xuo
18x5Wo3FLQN4t1DLZgV2MoA
1GR9qNz7zgtaW5HwwVpEJWM
1FaUfrUhv37aqFAZ9ij5955
1DWsHCjeekCe3tRzMuJktHh
1HLsDiYE8P61Z3mwqVuq1xt
1PfceCKGraSPEvx6nfjw5ZC
15xZvLJLAgxh8cxEmAbpx1H
1BZaYtmXka1y3Byi2yvXCDG
1GKztam9D8ZWK9GxsNoNZbV
1KKiEAkpnQR2FH5kpkGP644
18hRPy5sTzoYAfX18qn8eK1
1HBM45n214sV9yXoizBwTks
13sixi6TGPoWvbi2e93wdQS
1CMbVZV7xbAiFFauuAf3tgZ
15NQthxeLSwMtEaXJFM7YUC
1aXzEKiDJKzkPxTZy9zGc3y
1DWxysF7GPRYGShNxL5ux2N
1923qxU74HWWz75LgWTsPE4
19G5kkYvjawZiYKhFeh8Wmf
1F34duy2eeMz5mSrvFepVzy
1f1miYFQWTzdLiCBxtHHnNi
187Nqgq3WoKihPNMtWYfRe6
1KbrSKrT3GeEruTuuYYUSQ3
14YK4mzJGo5NKkNnmVJeuEA
12tLs9c9RsALt4ockxa1hB4
1P1iThxBH542Gmk1kZNXyji
1ucXXZQSEf4zny2HRwAQKtV
1BAFWQhH9pNkz3mZDQ1tWrt
1CPaziTqeEixPoSFtJxu74u
1Ki3WTEEqTLPNsN5cGTsMkL
1Kx4QFupZ9vKFmUDhsptfSB
1LfV1tSt3KNyHpFJnAzrqsL
1EU2pMence1UfifCco2UHJC
1DBwffK5gAsL7axG6idGFRX
1Kd6zLb9iAjcrgq8HzWnoWN
1P9fAFAsSLRmMu2P7wZ5CXD
1HLvaTs3zR3oev9ya7Pzp3G
17CzhFvGwH6TT46JtzhnhMp
15nMWix4rnpr7HaZkvfMVkd
167ZWTT8n6s4ya8cGjqNNQj
1HTzd3sKVmrTNZ6QGisPPA1
1NDyJtNTjmwk5xPNhjgAMu4
1HGVtEtKWayb56xiZ4YJQie
19MqjbtGam8oTk21QCM32fj
19rxQRpXBMQcbsYcxo6w9xL
18zuLTKQnLjp987LdxuYvje
1NpZcfBnaJeoRT9ZqwZVRMw
198aMn6ZYAczwrE5NvNTUMy
1MYv4C4hZ7hC5sbHrPkzvmN
1FUBESNxB2JkyXPc4o9wwoG
1EDRfeNkjkH2SAhSbEKzhKu
182p5CrqfDxvonznRyi5AUB
1LyTftu54VMYCv5pq3S4pMz
1Cb1G5qFK91fShyaPPZWVFw
19Te6hzGFSbryomVYqzG2kp
1JpiTWauQdtysbynNp88dWe
1N4yKFsFPjjoJyo3BAKUWpc

xhomerx10

legendary

Activity: 3808

Merit: 7912

Quote from: PietCoin97 on January 01, 2019, 05:37:13 PM

ok so i remove the Safe mode

I start with

Code:

./oclvanitygen -k -D 0:0 -D 0:1 -D 0:2 -D 0:3 -D 0:4 -o found.txt -f 6MIOPattern -s seed
Read 77 bytes from RNG seed file

Next match difficulty: 719170320814992132724345727918 (5999998 prefixes)
[183.69 Mkey/s][total 1069547520][Prob 0.0%][50% in 8.605509e+13y] Match idx: 6082822
CPU hash: 8e824fbbdf941ecd859e1da587e4fa0b563f13ef
GPU hash: 3b4df4363caa9e3bd9da58020d3080be8230a4ae
Found delta: 15727901 Start delta: 31457281
[179.43 Mkey/s][total 6464471040][Prob 0.0%][50% in 8.809719e+13y]

and get always the same hash 3b4df4363caa9e3bd9da58020d3080be8230a4ae

so how do you search ?

Are you trying to load a file that contains 6 million patterns to search for?

Can you give us a small sample of the patterns from your file?

big_daddy

hero member

Activity: 1680

Merit: 583

xUSD - The PRIVATE stable coin - Haven Protocol

I'm trying to generate my custom BTC address but with my CPU is a pain in....
Does anyone managed to run the program over the GPUs? I have AMD cards, rx470 and rx570, but I'm getting errors, the process is not starting

PietCoin97

jr. member

Activity: 91

Merit: 3

ok so i remove the Safe mode

I start with

Code:

./oclvanitygen -k -D 0:0 -D 0:1 -D 0:2 -D 0:3 -D 0:4 -o found.txt -f 6MIOPattern -s seed
Read 77 bytes from RNG seed file

Next match difficulty: 719170320814992132724345727918 (5999998 prefixes)
[183.69 Mkey/s][total 1069547520][Prob 0.0%][50% in 8.605509e+13y] Match idx: 6082822
CPU hash: 8e824fbbdf941ecd859e1da587e4fa0b563f13ef
GPU hash: 3b4df4363caa9e3bd9da58020d3080be8230a4ae
Found delta: 15727901 Start delta: 31457281
[179.43 Mkey/s][total 6464471040][Prob 0.0%][50% in 8.809719e+13y]

and get always the same hash 3b4df4363caa9e3bd9da58020d3080be8230a4ae

so how do you search ?

KingZee

sr. member

Activity: 938

Merit: 452

Check your coin privilege

Quote from: PietCoin97 on January 01, 2019, 02:31:42 PM

----

Why are you running on safe mode the second time? Try removing -S

To quote the response fom this :

Quote

oclVanitygen generates addresses by using OpenCL. OpenCL can run on GPUs, in contrast to C. After OpenCL thinks an address it created has the expected prefix, it passes the private key (actually the delta value of it), the calculated P2PKH hash and the idx value to the C part of the software. When the GPU calculated hash doesn't match the CPU calculated hash, it dumps the info for debugging.

Short Answer: It would, of course, have printed the private key if it had found an address with the expected prefix.

I also don't get what you're trying to achieve using different seeds. You want to find the same patterns from your input file, so regardless of the seed used, if vanitygen finds a pattern that matches the ones in your file, it'll add it. The seeds only help in changing where vanitygen starts to search for a solution, but provided it runs for long enough (and it looks like it'll need a massive amount of years to find what you want) it won't matter anymore.

Topic: Vanitygen: Vanity bitcoin address generator/miner [v0.22] - page 10. (Read 1153559 times)