Bitcoin Forum
December 11, 2016, 08:31:28 AM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 [85] 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 ... 155 »
  Print  
Author Topic: Vanitygen: Vanity bitcoin address generator/miner [v0.22]  (Read 810084 times)
Trillium
Hero Member
*****
Offline Offline

Activity: 546



View Profile
June 09, 2014, 02:08:49 AM
 #1681

I can confirm that output means you have a wrong driver version. If the newer driver versions are all that work on Win 8/8.1 then I guess you'll have to find yourself another OS.

BTC:1AaaAAAAaAAE2L1PXM1x9VDNqvcrfa9He6
1481445088
Hero Member
*
Offline Offline

Posts: 1481445088

View Profile Personal Message (Offline)

Ignore
1481445088
Reply with quote  #2

1481445088
Report to moderator
1481445088
Hero Member
*
Offline Offline

Posts: 1481445088

View Profile Personal Message (Offline)

Ignore
1481445088
Reply with quote  #2

1481445088
Report to moderator
1481445088
Hero Member
*
Offline Offline

Posts: 1481445088

View Profile Personal Message (Offline)

Ignore
1481445088
Reply with quote  #2

1481445088
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
MICRO
Legendary
*
Offline Offline

Activity: 1078


Primedice support.


View Profile WWW
June 09, 2014, 08:48:11 AM
 #1682

I can confirm that output means you have a wrong driver version. If the newer driver versions are all that work on Win 8/8.1 then I guess you'll have to find yourself another OS.
It works just fine on my w8.1 . I guess its problem with his graphic driver or his gpu.

ned.ryerson
Member
**
Offline Offline

Activity: 79


View Profile
June 09, 2014, 06:49:29 PM
 #1683

How do you import an exported, encrypted private key from vanitygen?
MICRO
Legendary
*
Offline Offline

Activity: 1078


Primedice support.


View Profile WWW
June 09, 2014, 07:11:53 PM
 #1684

How do you import an exported, encrypted private key from vanitygen?

How to import it into wallet ?

ned.ryerson
Member
**
Offline Offline

Activity: 79


View Profile
June 09, 2014, 07:12:56 PM
 #1685

How do you import an exported, encrypted private key from vanitygen?

How to import it into wallet ?
Correct.  Bitcoind just gave me an error when I tried to do it.  I assumed it would prompt for the passphrase.
MICRO
Legendary
*
Offline Offline

Activity: 1078


Primedice support.


View Profile WWW
June 09, 2014, 07:16:05 PM
 #1686

How do you import an exported, encrypted private key from vanitygen?

How to import it into wallet ?
Correct.  Bitcoind just gave me an error when I tried to do it.  I assumed it would prompt for the passphrase.

Not sure about bitcoind, but i think u need to decrypt it first. Than to import private key.

MICRO
Legendary
*
Offline Offline

Activity: 1078


Primedice support.


View Profile WWW
June 09, 2014, 07:17:01 PM
 #1687

Here is how to do it :

If you have an encrypted wallet (recommended), you need to unlock it temporarily before importing private keys. The RPC command for unlocking an encrypted wallet is walletpassphrase <passphrase> <timeout>. Typing this directly in a bash terminal will leave your wallet passphrase directly in the bash history but there are a couple of techniques you can use to avoid this. Simply add a space before the command:

(space)bitcoind walletpassphrase yourpassphrase 120
Another alternative is to use a bash variable:

read x
(input your passphrase)
bitcoind walletpassphrase "$x" 120   # Do not set the timeout too long or too short.

ned.ryerson
Member
**
Offline Offline

Activity: 79


View Profile
June 09, 2014, 07:26:06 PM
 #1688

Here is how to do it :

If you have an encrypted wallet (recommended), you need to unlock it temporarily before importing private keys. The RPC command for unlocking an encrypted wallet is walletpassphrase <passphrase> <timeout>. Typing this directly in a bash terminal will leave your wallet passphrase directly in the bash history but there are a couple of techniques you can use to avoid this. Simply add a space before the command:

(space)bitcoind walletpassphrase yourpassphrase 120
Another alternative is to use a bash variable:

read x
(input your passphrase)
bitcoind walletpassphrase "$x" 120   # Do not set the timeout too long or too short.
That will allow you to add keys to the wallet, but you still need to "decrypt" the encrypted output of vanitygen somehow....
MICRO
Legendary
*
Offline Offline

Activity: 1078


Primedice support.


View Profile WWW
June 09, 2014, 07:37:46 PM
 #1689

Here is how to do it :

If you have an encrypted wallet (recommended), you need to unlock it temporarily before importing private keys. The RPC command for unlocking an encrypted wallet is walletpassphrase <passphrase> <timeout>. Typing this directly in a bash terminal will leave your wallet passphrase directly in the bash history but there are a couple of techniques you can use to avoid this. Simply add a space before the command:

(space)bitcoind walletpassphrase yourpassphrase 120
Another alternative is to use a bash variable:

read x
(input your passphrase)
bitcoind walletpassphrase "$x" 120   # Do not set the timeout too long or too short.
That will allow you to add keys to the wallet, but you still need to "decrypt" the encrypted output of vanitygen somehow....

If u encrypted it with password u can use that to decrypt , if u generated part keys u will need to put them together here: https://www.bitaddress.org/

gmaxwell
Moderator
Legendary
*
qt
Offline Offline

Activity: 2030



View Profile
June 09, 2014, 07:58:50 PM
 #1690

Still no compressed keys?  I'm kinda surprised considering how much faster it makes the searching.
MICRO
Legendary
*
Offline Offline

Activity: 1078


Primedice support.


View Profile WWW
June 09, 2014, 08:02:00 PM
 #1691

Still no compressed keys?  I'm kinda surprised considering how much faster it makes the searching.

Yeah it would make life much more easier. How hard is to implement that ?
I did not saw any devs commenting on this thread in a long time.

gmaxwell
Moderator
Legendary
*
qt
Offline Offline

Activity: 2030



View Profile
June 09, 2014, 08:11:12 PM
 #1692

Yeah it would make life much more easier. How hard is to implement that ?
I did not saw any devs commenting on this thread in a long time.
I have a hack of an implementation for cpu only— I don't have any gpus anymore, so doing more than that wasn't interesting to me. https://people.xiph.org/~greg/compressed.keys.patch
malevolent
can into space
Staff
Legendary
*
Offline Offline

Activity: 1624



View Profile
June 09, 2014, 08:13:18 PM
 #1693

Still no compressed keys?  I'm kinda surprised considering how much faster it makes the searching.

https://bitcointalk.org/index.php?topic=301068.0 ?


MICRO
Legendary
*
Offline Offline

Activity: 1078


Primedice support.


View Profile WWW
June 09, 2014, 08:14:51 PM
 #1694

Yeah it would make life much more easier. How hard is to implement that ?
I did not saw any devs commenting on this thread in a long time.
I have a hack of an implementation for cpu only— I don't have any gpus anymore, so doing more than that wasn't interesting to me. https://people.xiph.org/~greg/compressed.keys.patch


Tnx, i will take a look at it when i get bit more time. I think it will be much much faster .

MICRO
Legendary
*
Offline Offline

Activity: 1078


Primedice support.


View Profile WWW
June 09, 2014, 08:18:23 PM
 #1695

Still no compressed keys?  I'm kinda surprised considering how much faster it makes the searching.

https://bitcointalk.org/index.php?topic=301068.0 ?


That might also fix this guy problem:

can`t get 12.8 and 12.10 drivers to work on win 8.1 at all - no ocl devices detected...
any workaround?
13.1 and 13.6 - devices detected, but won`t work with ocl

Thank you.

I had the same problem than i updated to 8.1 update 1 . And it was working.


8.1 update 1 - 12.8 and 12.10 wont work (

Do u have latest graphic drivers?

what you mean?
I have tried 12.8 and 12.10 (on "win 8.1 update 1") and could not get any  software to recognize ocl devices.... (cgminer 3.7.2, oclvanitygen) (even these drivers were working good with cgminer 3.7.2 on "win 8")
I have tried 13.12 14.4 14.6beta drivers - ocl devices are recognized under win 8.1 update 1 and working fine with cgminer 3.7.2 for example. But even oclvanitygen recognizes ocl devices - it won`t produce any keys. I`m getting following errors:

[25.60 Mkey/s][total 113246208]                                                Match idx: 0
CPU hash: 62877214296428cff20ae302409afcabd66b05f1
GPU hash: 86c80e8df57566f7401c78c932b0862b13269b7e
Found delta: 6291453 Start delta: 1
Match idx: 0
CPU hash: a7154bbe3446797050205a116adc2a4b0e05Match idx: 0
CPU hash: eaf026c81206d7baf5a8ee137fa62d7b1efa1359
e11b
GPU hash: 2b5e766241541bf70a8ccc2489acMatch idx: 0
CPU hash: d73417646c48df0a688e6eca77b02291e3041f88
GPU hash: 9da6ec6c7c488c63ce5cfea3a1c4ec55f9734956
e87fc51bdf0c
Found delta: 6290172 Start delta: 1


As wiki states:

For AMD Catalyst 13.1+ you need to run the AMD APP SDK Runtime from Catalyst 12.10 in order to get this program to work. (So all your Catalyst drivers would be brand new except for the SDK Runtime.) This is discussed on GitHub. For Linux, use AMD APP SDK 2.7.
(https://en.bitcoin.it/wiki/Vanitygen)

there is incompatability of new drivers and oclvanitygen

So I also tried to install 2.7 and 2.8 amd app sdk on 12.10 13.12 14.4 drivers - with no success.

Basically what I`m asking - is there any solution to use oclvanitygen on win 8.1 update 1, or whatever latest patched and updated windows 8.1 is named.

That is rly weird. We need somebody from devs of vanitygen to help u out.



micax1
Hero Member
*****
Offline Offline

Activity: 532


View Profile
June 09, 2014, 08:58:57 PM
 #1696


That might also fix this guy problem:


Unfortunately same - and there is a guy with the same difficulties also:
https://bitcointalk.org/index.php?topic=301068.msg6821183#msg6821183

█▌
_
█▌█▌█▌
_
█▌█▌█▌
_
█▌█▌█▌
tspacepilot
Legendary
*
Offline Offline

Activity: 1246


I will write code in exchange for bitcoins.


View Profile
June 09, 2014, 09:13:38 PM
 #1697

I want to ask a question which will probably get people calling me stoopid or whatever but here I go:

Is there a danger of another person using vanitygen with the same input you gave it to generate your public/private key?  For example, assume I created a vanitygen address:

1Vanity...

Someone sees my address and correctly assumes I generated it with vanitygen:

./vanitygen 1Vanity

They now just have to run ./vanitygen 1Vanity and wait a while until they get my public/private keys.

Is that right or wrong?

I guess my assumption here is that while the space of possible random btc addresses is so large, the space of vanity addresses for a given prefix is smaller and perhaps dangerously small?  Also, I don't know how vanitygen searches the space but perhaps it's likely to find the addresses for a given prefix in a similar order each time?

Thanks for any insight.  You guys are smarter then me.

MICRO
Legendary
*
Offline Offline

Activity: 1078


Primedice support.


View Profile WWW
June 09, 2014, 09:23:35 PM
 #1698

I want to ask a question which will probably get people calling me stoopid or whatever but here I go:

Is there a danger of another person using vanitygen with the same input you gave it to generate your public/private key?  For example, assume I created a vanitygen address:

1Vanity...

Someone sees my address and correctly assumes I generated it with vanitygen:

./vanitygen 1Vanity

They now just have to run ./vanitygen 1Vanity and wait a while until they get my public/private keys.

Is that right or wrong?

I guess my assumption here is that while the space of possible random btc addresses is so large, the space of vanity addresses for a given prefix is smaller and perhaps dangerously small?  Also, I don't know how vanitygen searches the space but perhaps it's likely to find the addresses for a given prefix in a similar order each time?

Thanks for any insight.  You guys are smarter then me.

Its not dangerous at all. Its impossible to find whole bitcoin address.

In order for somebody to get private key for ur 1Vanity addy he would need to copy ur whole addy like 1Vanity15af4a5df63adf5645adf... Not only 1Vanity coz there are ALOT of addresses that can start with 1Vanity.

Its imposible for somebody to find key for ur 1Vanity addy , he can make alot of addresses that start with 1Vanity but they wont be the same as urs.

tspacepilot
Legendary
*
Offline Offline

Activity: 1246


I will write code in exchange for bitcoins.


View Profile
June 09, 2014, 09:53:38 PM
 #1699

I want to ask a question which will probably get people calling me stoopid or whatever but here I go:

Is there a danger of another person using vanitygen with the same input you gave it to generate your public/private key?  For example, assume I created a vanitygen address:

1Vanity...

Someone sees my address and correctly assumes I generated it with vanitygen:

./vanitygen 1Vanity

They now just have to run ./vanitygen 1Vanity and wait a while until they get my public/private keys.

Is that right or wrong?

I guess my assumption here is that while the space of possible random btc addresses is so large, the space of vanity addresses for a given prefix is smaller and perhaps dangerously small?  Also, I don't know how vanitygen searches the space but perhaps it's likely to find the addresses for a given prefix in a similar order each time?

Thanks for any insight.  You guys are smarter then me.

Its not dangerous at all. Its impossible to find whole bitcoin address.

In order for somebody to get private key for ur 1Vanity addy he would need to copy ur whole addy like 1Vanity15af4a5df63adf5645adf... Not only 1Vanity coz there are ALOT of addresses that can start with 1Vanity.

Its imposible for somebody to find key for ur 1Vanity addy , he can make alot of addresses that start with 1Vanity but they wont be the same as urs.

Thanks for the reply MICRO, but I'm suspicious about your information because it seems vague and lacking in detail.  For example, you say that something is impossible but I think you mean infeasibly improbable.  Since I'm looking for details and proofs, I guess I find myself still wanting.  Nonetheless, the point of your reply is noted: apparantly reducing the address space by a prefix is insignficant.  Can anyone fill in the numbers to make this clear?

Second point seems implied in your answer but isn't explicit, apparantly vanitygen is going to generate matching addresses in some pseudo random order.

Also, I decided to put this to the empirical test.  Now running vanitygen with 1Micro Smiley

TheRealSteve
Hero Member
*****
Offline Offline

Activity: 686

FUN > ROI


View Profile
June 09, 2014, 10:11:55 PM
 #1700

Thanks for the reply MICRO, but I'm suspicious about your information because it seems vague and lacking in detail.  For example, you say that something is impossible but I think you mean infeasibly improbable.
Yes, that's what they meant.  Note that for all practical purposes, you can consider that to be on the level of 'impossible'.  I.e. say you roll a million dice - is it possible that you'll roll a 4 on all million?  Sure, it's possible.  Now consider that the issue we're discussing here is several magnitudes more difficult still Smiley

Since I'm looking for details and proofs, I guess I find myself still wanting.  Nonetheless, the point of your reply is noted: apparantly reducing the address space by a prefix is insignficant.
You would have to look for technical discussions about finding collisions for the private key in general.  The fact that the address starts with a vanity doesn't actually 'reduce the search space'.  I.e. you can't say 'generate only keys for which the address starts with this vanity'.  The way it works is that it generates a whole lot of keys, calculates the address, and then checks if that address happens to start with the desired vanity.

If you could do it the other way around, then 1SomeVan1ty is every bit as vulnerable as, say, 1x3pqDdtUza - a non-vanity (well, unless somebody considers that to be a vanity, of course) - and thus all Bitcoin addresses would be vulnerable.

In addition, while you can possibly get a collision on the address, you still can't spend from that address unless you have the correct private key.  So even if you do happen to get a full match on the address, you might still not have the correct private key to go with it. (addresses are hashes of the public key, which have a smaller space than the public key, so at least there's a greater potential for a collision on the address)

Pages: « 1 ... 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 [85] 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 ... 155 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!