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

[gri0]

Really nice program! Thank you samr7!
I have a two questions.
1. Why I can't to specify a pattern begins from "3"
2. Why you are limit a pattern length?
I want to extend that. I don't care about calculating the time remaining. Is it difficult to patch the code?

[OgNasty]

Really nice program! Thank you samr7!
I have a two questions.
1. Why I can't to specify a pattern begins from "3"
2. Why you are limit a pattern length?
I want to extend that. I don't care about calculating the time remaining. Is it difficult to patch the code?

samr7 won't be responding to you, so I will. 
1.  You can.  ($ ./vanitygen -X 5 31 -k)
2.  The pattern length is limited for probably a few reasons.  However, the biggest reason in my opinion is to stop people from thinking they can use this to crack someone's address within their lifetime.  Which would cause them to waste electricity for no reason.

[gri0]

samr7 won't be responding to you, so I will. 
1.  You can.  ($ ./vanitygen -X 5 31 -k)
2.  The pattern length is limited for probably a few reasons.  However, the biggest reason in my opinion is to stop people from thinking they can use this to crack someone's address within their lifetime.  Which would cause them to waste electricity for no reason.

1. Thank you, OgNasty
2. Lol nice pic, Unfortunately the text on the pic is too huge for demotivator.

But what if someone will find some regularity in a pseudo-random number generator?
Or just running the code at an old 386DX computer for a few seconds and will find the key? Perhaps? It is. The chance is 1:2^160 but it is theoretically possible.
This soft can do more than just generate a cute BTC address, but not enough flexible for now.

[Shockaftermoon]

I've been trying to figure out what I'm doing wrong with my GPU... it's an AMD A6-3420M Radeon(tm) HD Graphics. When I try and do -D 0:0 and/or -D 0:1 it say 'could not open device '0:0', ignoring. It shows my GPU as '1:' so I'm assuming I need to use the command 1:1, right?

I've seen a couple of people who've had to use 1:0 2:0 3:0 to describe their graphics cards.

Your 0:0 might be your CPU, you can squeeze a few extra hashes out of it, but the system slows right down.

I didn't seem to be able to figure out how to use the GPU at all in oclvanitygen. I did -v -D 0:0 -D 0:1 1test, -v -D 0:0 -D 1:0 1test, and a few other variations but they don't work for me. I've found some guides but I really can't figure out what I'm doi wrong. Ikv used my CPU with vanitygen64 with no issues so assumed using the GPU would be basically the same!

Start simple

Code:

oclvanitygen 1Boat

You should get this: (and by this I mean something similar)

Code:

Difficulty: 4476342
Available OpenCL platforms:
0: [Advanced Micro Devices, Inc.] AMD Accelerated Parallel Processing
  0: [Advanced Micro Devices, Inc.] Tahiti
  1: [Advanced Micro Devices, Inc.] Tahiti
  2: [AuthenticAMD] AMD A4-3300 APU with Radeon(tm) HD Graphics

Choosing just the last one I then get

Code:

oclvanitygen -D 0:2 1Boat

You should get something like this:

Code:

Difficulty: 4476342
Compiling kernel, can take minutes...done!
Pattern: 1Boat
Address: 1BoatZkAneV9PsCp6LKenR3rxQXs6mQoiy
Privkey: 5K7aGsmQvymQx12WRQhZ6VZ3EdeLgwJjGANMHmLd92yNwSnsj6F

-snip-

Thanks so much for going through that in depth for me! I finally got it figured out this is going to be fun to go through different settings now that I have the basics down!

workin here

[aarons6]

samr7 won't be responding to you, so I will.  
1.  You can.  ($ ./vanitygen -X 5 31 -k)
2.  The pattern length is limited for probably a few reasons.  However, the biggest reason in my opinion is to stop people from thinking they can use this to crack someone's address within their lifetime.  Which would cause them to waste electricity for no reason.

1. Thank you, OgNasty
2. Lol nice pic, Unfortunately the text on the pic is too huge for demotivator.

But what if someone will find some regularity in a pseudo-random number generator?
Or just running the code at an old 386DX computer for a few seconds and will find the key? Perhaps? It is. The chance is 1:2^160 but it is theoretically possible.
This soft can do more than just generate a cute BTC address, but not enough flexible for now.

there is a better chance you can walk out of your front door and get hit by a meteorite..

[gri0]

there is a better chance you can walk out of your front door and get hit by a meteorite..

There is no case of human death by a meteorite. How have you calculate the chance?
I have never read the books such cases have been recorded.
Any proofs? 

[LoyceV]

Or just running the code at an old 386DX computer for a few seconds and will find the key? Perhaps? It is. The chance is 1:2^160 but it is theoretically possible.

For some reason this always pops up. Fact is: it hasn't happened in the 7 years Bitcoin exists, and it won't happen. Ever.
The chance is small. Very small. Smaller than you can imagine.

There is no case of human death by a meteorite. How have you calculate the chance?
I have never read the books such cases have been recorded.
Any proofs? 

Not reading about it doesn't mean it doesn't exist. In 2013 a meteor in Russia was caught on camera. The 20 metre wide rock entered at 12 miles per second and exploded with the energy of 500 kilotonnes of TNT. It indured 1210 people.
Most people know the most famous story: Tunguska event in 1908.

The problem with statistics is: people tend to think the unlikely thing will happen if it benefits them. For example: winning the lottery with a 1 in 50 million chance. "Hey, that could be me!"
Getting killed in traffic (30,000 people per year in the USA alone): "Nah, that won't be me!".

This links gives some examples of real events with a 1 in a million chance. And that's just 1 in a million, which is millions upon millions times more likely than finding a private key that belongs to an existing address.

[.m.]

Do you think with quantum computers the odds can be better ?

[gri0]

Or just running the code at an old 386DX computer for a few seconds and will find the key? Perhaps? It is. The chance is 1:2^160 but it is theoretically possible.

For some reason this always pops up. Fact is: it hasn't happened in the 7 years Bitcoin exists, and it won't happen. Ever.
The chance is small. Very small. Smaller than you can imagine.

There is no case of human death by a meteorite. How have you calculate the chance?
I have never read the books such cases have been recorded.
Any proofs? 

Not reading about it doesn't mean it doesn't exist. In 2013 a meteor in Russia was caught on camera. The 20 metre wide rock entered at 12 miles per second and exploded with the energy of 500 kilotonnes of TNT. It indured 1210 people.
Most people know the most famous story: Tunguska event in 1908.

The problem with statistics is: people tend to think the unlikely thing will happen if it benefits them. For example: winning the lottery with a 1 in 50 million chance. "Hey, that could be me!"
Getting killed in traffic (30,000 people per year in the USA alone): "Nah, that won't be me!".

This links gives some examples of real events with a 1 in a million chance. And that's just 1 in a million, which is millions upon millions times more likely than finding a private key that belongs to an existing address.

Not only USA have a meteors. 

[Timelord2067]

Do you think with quantum computers the odds can be better ?

Fuzzy logic:  A value is both a zero and a one... therefore, you will both have and not have the answer - it sort of sounds like when Yoda speaks...

"My Finger, you will pull..."

[Chris!]

AFAIK any graphics cards are ok, their age and type determine some basics such as their speed and whether or not you should use the "original" or the Og Nasty variant.

I've never been able to use an Intel GPU for some reason. What is this OgNasty variant of Vanitygen, where do I find it, what is it called and what's better about it? Faster results?

Does anyone know if you would be able to use an ARM Mali 450 GPU in an android TV box to find vanity addresses? I guess it would be impossible because of it being android. I saw that there was an android variant a long time ago but I couldn't get it to work (because of how old it was I'm sure).

[Timelord2067]

[quote author=Timelord2067 link=topic=25804.msg16098047#msg16098047 date=1472638349]
AFAIK any graphics cards are ok, their age and type determine some basics such as their speed and whether or not you should use the "original" or the Og Nasty variant.

I've never been able to use an Intel GPU for some reason. What is this OgNasty variant of Vanitygen, where do I find it, what is it called and what's better about it? Faster results?

Does anyone know if you would be able to use an ARM Mali 450 GPU in an android TV box to find vanity addresses? I guess it would be impossible because of it being android. I saw that there was an android variant a long time ago but I couldn't get it to work (because of how old it was I'm sure).
[/quote]

a quick search of the 150 pages of this thread for the search term "lifeboat" finds this post:

[quote author=cancerbola link=topic=25804.msg13792127#msg13792127 date=1454751405]
Does any one know what's up with this? https://talkimg.com/images/2023/05/17/blob2378f32c9541f584.png?2

Even when trying to generate a short prefix like 1Tst, it always says something about a "delta" and restarts... I'm using oclvanitygen btw.

The Radeon driver changed a year ago... use "-S" and it will work (albeit slower)

Or you can search through this thread for a 3rd party who updated the code/driver (if you trust that sort of thing)

This is the Lifeboat Foundation's updated application.  It will work on Windows with the current Radeon drivers if you trust them enough to run it.

https://lifeboat.com/oclvanitygen


If you are running Linux, nonnakip has created this document to help you get the default oclvanitygen working.

https://nastyfans.org/download/oclvanitygen.txt
[/quote]

OK?

[.m.]

I probably can search my historical experiments if needed.

[Chris!]

AFAIK any graphics cards are ok, their age and type determine some basics such as their speed and whether or not you should use the "original" or the Og Nasty variant.

I've never been able to use an Intel GPU for some reason. What is this OgNasty variant of Vanitygen, where do I find it, what is it called and what's better about it? Faster results?

Does anyone know if you would be able to use an ARM Mali 450 GPU in an android TV box to find vanity addresses? I guess it would be impossible because of it being android. I saw that there was an android variant a long time ago but I couldn't get it to work (because of how old it was I'm sure).

a quick search of the 150 pages of this thread for the search term "lifeboat" finds this post:

Does any one know what's up with this? https://i.imgur.com/G2lGy9L.png?2

Even when trying to generate a short prefix like 1Tst, it always says something about a "delta" and restarts... I'm using oclvanitygen btw.

The Radeon driver changed a year ago... use "-S" and it will work (albeit slower)

Or you can search through this thread for a 3rd party who updated the code/driver (if you trust that sort of thing)

This is the Lifeboat Foundation's updated application.  It will work on Windows with the current Radeon drivers if you trust them enough to run it.

https://lifeboat.com/oclvanitygen


If you are running Linux, nonnakip has created this document to help you get the default oclvanitygen working.

https://nastyfans.org/download/oclvanitygen.txt

OK?

Ah, lifeboat is the name. Ok gotchya. So I'm assuming it's better in some way than the original Vanitygen. I'll do some research and see what I can get done with this. Thanks again!

[gri0]

Code:

oclvanitygen -D 0:2 1Boat

You should get something like this:

Code:

Difficulty: 4476342
Compiling kernel, can take minutes...done!
Pattern: 1Boat
Address: 1BoatZkAneV9PsCp6LKenR3rxQXs6mQoiy
Privkey: 5K7aGsmQvymQx12WRQhZ6VZ3EdeLgwJjGANMHmLd92yNwSnsj6F

-snip-

Is the way to convert a PrivKey to the format supported by thin client Electrum or Mycelium?

[achow101]

Code:

oclvanitygen -D 0:2 1Boat

You should get something like this:

Code:

Difficulty: 4476342
Compiling kernel, can take minutes...done!
Pattern: 1Boat
Address: 1BoatZkAneV9PsCp6LKenR3rxQXs6mQoiy
Privkey: 5K7aGsmQvymQx12WRQhZ6VZ3EdeLgwJjGANMHmLd92yNwSnsj6F

-snip-

Is the way to convert a PrivKey to the format supported by thin client Electrum or Mycelium?

It already is in the supported format. It is in WIF, which is supported by nearly every single Bitcoin wallet.

[gri0]

Is the way to convert a PrivKey to the format supported by thin client Electrum or Mycelium?

It already is in the supported format. It is in WIF, which is supported by nearly every single Bitcoin wallet.

No they don't. Mycelium needs masterseed. And Electrum needs walletpassphrase.

[LoyceV]

No they don't. Mycelium needs masterseed. And Electrum needs walletpassphrase.

When you first start Electrum, it gives you the option: you can use either walletpassphrase or import your own private keys. Unfortunately, you can't use both.
My guess it they try to protect people against stupidity user error. This way, a user can't think the walletpassphrase is enough to backup the imported private keys.
It's also the main reason I don't use Electrum, I want a wallet that imports keys and handles new addresses by itself too.

If the wallet doesn't allow the WIF private key to be imported, no other format is going to do it.

[.m.]

So it is enough just to create another wallet and import generated private key - isn't it ?

[DarkStar_]

So it is enough just to create another wallet and import generated private key - isn't it ?

Yes. Electrum works fine with importing your own private keys if you decide to do it when you open the wallet.