Bitcoin Forum
April 24, 2018, 07:10:01 AM *
News: Latest stable version of Bitcoin Core: 0.16.0  [Torrent]. (New!)
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 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 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 ... 178 »
  Print  
Author Topic: Vanitygen: Vanity bitcoin address generator/miner [v0.22]  (Read 1107516 times)
K1773R
Legendary
*
Offline Offline

Activity: 1764
Merit: 1000


/dev/null


View Profile
March 18, 2015, 10:40:50 AM
 #2041

vanitygen problem it generate same address again
... removed crap ...
in this case, you have a serious problem.
either your PRNG implementation in OpenSSL is broken or your system RNG entroy sources is borked.
of course, both can be the case and are not mutually exclusive.

even worse, this is a good sign that very likely all of the crypto modules your software/OS uses will be weak! its not only vanitygen who is affected by this.

[GPG Public Key]  [Devcoin Builds]  [BBQCoin Builds]  [Multichain Blockexplorer]  [Multichain Blockexplorer - PoS Coins]  [Ufasoft Miner Linux Builds]
BTC/DVC/TRC/FRC: 1K1773RbXRZVRQSSXe9N6N2MUFERvrdu6y ANC/XPM AK1773RTmRKtvbKBCrUu95UQg5iegrqyeA NMC: NK1773Rzv8b4ugmCgX789PbjewA9fL9Dy1 LTC: LKi773RBuPepQH8E6Zb1ponoCvgbU7hHmd EMC: EK1773RxUes1HX1YAGMZ1xVYBBRUCqfDoF BQC: bK1773R1APJz4yTgRkmdKQhjhiMyQpJgfN
1524553801
Hero Member
*
Offline Offline

Posts: 1524553801

View Profile Personal Message (Offline)

Ignore
1524553801
Reply with quote  #2

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

Posts: 1524553801

View Profile Personal Message (Offline)

Ignore
1524553801
Reply with quote  #2

1524553801
Report to moderator
1524553801
Hero Member
*
Offline Offline

Posts: 1524553801

View Profile Personal Message (Offline)

Ignore
1524553801
Reply with quote  #2

1524553801
Report to moderator
1524553801
Hero Member
*
Offline Offline

Posts: 1524553801

View Profile Personal Message (Offline)

Ignore
1524553801
Reply with quote  #2

1524553801
Report to moderator
TheRealSteve
Hero Member
*****
Offline Offline

Activity: 686
Merit: 500

FUN > ROI


View Profile
March 18, 2015, 10:48:16 AM
 #2042

vanitygen problem it generate same address again
It's a mostly-random process, so that can happen.  In addition there's collisions on address space, though in this case it looks like it ended up with the same private key as well.

Could you share the command line you had used for those two runs?

I don't know off hand what the statistical odds are of that happening with vanitygen, but they should be very, very slim to the point that I'd wonder if somehow the RNG's entropy pool was weak (essentially what K1773R said while I wrote this)...but then it should be happening more often.   ( You can provide another source of entropy for the seed based on a file )

So, either something weird's going on, or you hit a one-in-a-largenumberhere fluke Smiley

K1773R
Legendary
*
Offline Offline

Activity: 1764
Merit: 1000


/dev/null


View Profile
March 18, 2015, 10:55:49 AM
 #2043

vanitygen problem it generate same address again
It's a mostly-random process, so that can happen.  In addition there's collisions on address space, though in this case it looks like it ended up with the same private key as well.

Could you share the command line you had used for those two runs?

I don't know off hand what the statistical odds are of that happening with vanitygen, but they should be very, very slim to the point that I'd wonder if somehow the RNG's entropy pool was weak (essentially what K1773R said while I wrote this)...but then it should be happening more often.   ( You can provide another source of entropy for the seed based on a file )

So, either something weird's going on, or you hit a one-in-a-largenumberhere fluke Smiley
If he has a bad PRNG implementation inside OpenSSL then using a different entropy source to seed the PRNG wont fix the problem.

[GPG Public Key]  [Devcoin Builds]  [BBQCoin Builds]  [Multichain Blockexplorer]  [Multichain Blockexplorer - PoS Coins]  [Ufasoft Miner Linux Builds]
BTC/DVC/TRC/FRC: 1K1773RbXRZVRQSSXe9N6N2MUFERvrdu6y ANC/XPM AK1773RTmRKtvbKBCrUu95UQg5iegrqyeA NMC: NK1773Rzv8b4ugmCgX789PbjewA9fL9Dy1 LTC: LKi773RBuPepQH8E6Zb1ponoCvgbU7hHmd EMC: EK1773RxUes1HX1YAGMZ1xVYBBRUCqfDoF BQC: bK1773R1APJz4yTgRkmdKQhjhiMyQpJgfN
gmaxwell
Moderator
Legendary
*
qt
Offline Offline

Activity: 2436
Merit: 1183



View Profile
March 18, 2015, 11:34:17 AM
 #2044

It's a mostly-random process, so that can happen.  In addition there's collisions on address space, though in this case it looks like it ended up with the same private key as well.
Not in any practical sense.

If something was broken that did do that on his system, both execution traces would be the same.

In this case the posts just clearly appeared to be an excuse to encourage people to run backdoored private key generating code (which I've removed from the thread).

Bitcoin will not be compromised
TheRealSteve
Hero Member
*****
Offline Offline

Activity: 686
Merit: 500

FUN > ROI


View Profile
March 18, 2015, 12:14:40 PM
 #2045

In this case the posts just clearly appeared to be an excuse to encourage people to run backdoored private key generating code (which I've removed from the thread).
Ah that sneaky bugger.  Thanks for catching that, I didn't even bother with the chunk-o-code Smiley

If he has a bad PRNG implementation inside OpenSSL then using a different entropy source to seed the PRNG wont fix the problem.
True, it should only affect the seed - that's still important if you don't trust that part.

K1773R
Legendary
*
Offline Offline

Activity: 1764
Merit: 1000


/dev/null


View Profile
March 18, 2015, 01:33:42 PM
 #2046

It's a mostly-random process, so that can happen.  In addition there's collisions on address space, though in this case it looks like it ended up with the same private key as well.
Not in any practical sense.

If something was broken that did do that on his system, both execution traces would be the same.

In this case the posts just clearly appeared to be an excuse to encourage people to run backdoored private key generating code (which I've removed from the thread).
i've edited my post accordingly by just removing everything aside the headline.

[GPG Public Key]  [Devcoin Builds]  [BBQCoin Builds]  [Multichain Blockexplorer]  [Multichain Blockexplorer - PoS Coins]  [Ufasoft Miner Linux Builds]
BTC/DVC/TRC/FRC: 1K1773RbXRZVRQSSXe9N6N2MUFERvrdu6y ANC/XPM AK1773RTmRKtvbKBCrUu95UQg5iegrqyeA NMC: NK1773Rzv8b4ugmCgX789PbjewA9fL9Dy1 LTC: LKi773RBuPepQH8E6Zb1ponoCvgbU7hHmd EMC: EK1773RxUes1HX1YAGMZ1xVYBBRUCqfDoF BQC: bK1773R1APJz4yTgRkmdKQhjhiMyQpJgfN
Just Magicmann
Sr. Member
****
Offline Offline

Activity: 378
Merit: 250


https://keybase.io/magicmann


View Profile WWW
March 21, 2015, 07:41:02 AM
 #2047

I'm having issues using my GTX 660 to assist in generating a vanity address. I marked -d 1:0 (already determined correct device) and all it does is show me the commands for vanitygen. I'm using version .20 if that makes a difference.

Command I'm using:
>vanitygen64 -v -d 1:0 -X 115 oMagicmann

Don't deal with me until I verify with Keybase.io.
Muhammed Zakir
Hero Member
*****
Offline Offline

Activity: 560
Merit: 504


I prefer Zakir over Muhammed when mentioning me!


View Profile WWW
March 21, 2015, 08:01:13 AM
 #2048

I'm having issues using my GTX 660 to assist in generating a vanity address. I marked -d 1:0 (already determined correct device) and all it does is show me the commands for vanitygen. I'm using version .20 if that makes a difference.

Command I'm using:
>vanitygen64 -v -d 1:0 -X 115 oMagicmann

Can you try this?

Code:
vanitygen64 -v -D 1:0 -X 115 oMagicmann

Just Magicmann
Sr. Member
****
Offline Offline

Activity: 378
Merit: 250


https://keybase.io/magicmann


View Profile WWW
March 21, 2015, 05:30:24 PM
 #2049

I'm having issues using my GTX 660 to assist in generating a vanity address. I marked -d 1:0 (already determined correct device) and all it does is show me the commands for vanitygen. I'm using version .20 if that makes a difference.

Command I'm using:
>vanitygen64 -v -d 1:0 -X 115 oMagicmann

Can you try this?

Code:
vanitygen64 -v -D 1:0 -X 115 oMagicmann

I've done both a lower and upper case D and get the same result.

Don't deal with me until I verify with Keybase.io.
TheRealSteve
Hero Member
*****
Offline Offline

Activity: 686
Merit: 500

FUN > ROI


View Profile
March 21, 2015, 05:42:28 PM
 #2050

I'm having issues using my GTX 660 [...]

Command I'm using:
>vanitygen64 -v -d 1:0 -X 115 oMagicmann
Is that the exact command you're using?  If so... you're trying to use the CPU binary to do GPU vanity generation.  Try again with oclvanitygen64

Just Magicmann
Sr. Member
****
Offline Offline

Activity: 378
Merit: 250


https://keybase.io/magicmann


View Profile WWW
March 23, 2015, 12:16:53 AM
 #2051

I'm having issues using my GTX 660 [...]

Command I'm using:
>vanitygen64 -v -d 1:0 -X 115 oMagicmann
Is that the exact command you're using?  If so... you're trying to use the CPU binary to do GPU vanity generation.  Try again with oclvanitygen64

Did it with oclvanitygen and it works. Thanks for correcting my mistake!  Smiley

Don't deal with me until I verify with Keybase.io.
tspacepilot
Legendary
*
Offline Offline

Activity: 1456
Merit: 1013


I may write code in exchange for bitcoins.


View Profile
March 23, 2015, 06:28:42 PM
 #2052

I've had vanitygen looking for a particular vanity prefix (6 letters) for about 5 days (not on the greatest hardware, admittedly, i'm getting 350Kkeys/s).  Nevertheless, I've been at 99.4% probability for 2 days now still with no results.  Could something be wrong or am I just unlucky?

Code:
[349.32 Kkey/s][total 144105239092][Prob 99.4%]
TwinWinNerD
Legendary
*
Offline Offline

Activity: 1652
Merit: 1001


CEO Bitpanda.com


View Profile WWW
March 23, 2015, 06:32:20 PM
 #2053

I've had vanitygen looking for a particular vanity prefix (6 letters) for about 5 days (not on the greatest hardware, admittedly, i'm getting 350Kkeys/s).  Nevertheless, I've been at 99.4% probability for 2 days now still with no results.  Could something be wrong or am I just unlucky?

Code:
[349.32 Kkey/s][total 144105239092][Prob 99.4%]


Unlucky. The 99.4% doesn't that you are close to finding it. Acutally no matter how long you have already searched, it will always take the same average time from that moment on.

The 99.4% means that if you searched for the amount of time you did, the chance of you finding one key would be 99.4%. So you are just a few standarddeviations from your average. No need to be alarmed.

tspacepilot
Legendary
*
Offline Offline

Activity: 1456
Merit: 1013


I may write code in exchange for bitcoins.


View Profile
March 23, 2015, 06:57:24 PM
 #2054

I've had vanitygen looking for a particular vanity prefix (6 letters) for about 5 days (not on the greatest hardware, admittedly, i'm getting 350Kkeys/s).  Nevertheless, I've been at 99.4% probability for 2 days now still with no results.  Could something be wrong or am I just unlucky?

Code:
[349.32 Kkey/s][total 144105239092][Prob 99.4%]


Unlucky. The 99.4% doesn't that you are close to finding it. Acutally no matter how long you have already searched, it will always take the same average time from that moment on.

The 99.4% means that if you searched for the amount of time you did, the chance of you finding one key would be 99.4%. So you are just a few standarddeviations from your average. No need to be alarmed.

Ok, I think I understand you.  I have searched for this long and have .994 probability of having found one key.  However, I've actually found 0 keys and 1 key isn't that far away from 0 keys (these are the values which aren't so far apart in std.devs, yes?) so I guess I shall just let this thing keep on computing.
TheRealSteve
Hero Member
*****
Offline Offline

Activity: 686
Merit: 500

FUN > ROI


View Profile
March 23, 2015, 06:58:58 PM
 #2055

Just for kicks, what is the exact command line you're using?

tspacepilot
Legendary
*
Offline Offline

Activity: 1456
Merit: 1013


I may write code in exchange for bitcoins.


View Profile
March 23, 2015, 07:01:40 PM
 #2056

Just for kicks, what is the exact command line you're using?

Code:
tspacepilot@god:~/src/vanitygen$ ./vanitygen -v 1WALNUT
Prefix difficulty:          27763956579 1WALNUT
Difficulty: 27763956579
Using 2 worker thread(s)
TheRealSteve
Hero Member
*****
Offline Offline

Activity: 686
Merit: 500

FUN > ROI


View Profile
March 23, 2015, 07:12:07 PM
 #2057

Code:
tspacepilot@god:~/src/vanitygen$ ./vanitygen -v 1WALNUT
Yeah, probably just bad luck then. 7-character prefix will take a while on most hardware and the bad end of variance scales accordingly.

If you're keen on having it, generate a private/public key pair, post the public key here, and maybe some kind folks will attempt a search for you.  See the discussion on split key generation a page or 2 back for details.

tspacepilot
Legendary
*
Offline Offline

Activity: 1456
Merit: 1013


I may write code in exchange for bitcoins.


View Profile
March 23, 2015, 07:19:08 PM
 #2058

Code:
tspacepilot@god:~/src/vanitygen$ ./vanitygen -v 1WALNUT
Yeah, probably just bad luck then. 7-character prefix will take a while on most hardware and the bad end of variance scales accordingly.

If you're keen on having it, generate a private/public key pair, post the public key here, and maybe some kind folks will attempt a search for you.  See the discussion on split key generation a page or 2 back for details.

Right on, for the moment I've got no rush so I'll just let it crank away for a while.  If I get desperate sometime a week or so from now then I may just take you up on that.  Thanks TheRealSteve.
Kangaderoo
Member
**
Offline Offline

Activity: 85
Merit: 10


View Profile
March 23, 2015, 07:27:54 PM
 #2059

Code:
tspacepilot@god:~/src/vanitygen$ ./vanitygen -v 1WALNUT
Yeah, probably just bad luck then. 7-character prefix will take a while on most hardware and the bad end of variance scales accordingly.

If you're keen on having it, generate a private/public key pair, post the public key here, and maybe some kind folks will attempt a search for you.  See the discussion on split key generation a page or 2 back for details.

Right on, for the moment I've got no rush so I'll just let it crank away for a while.  If I get desperate sometime a week or so from now then I may just take you up on that.  Thanks TheRealSteve.

I'm not sure what version you are running, but I checked on my system:

Code:
$ ./vanitygen -v 1WALNUT
Prefix difficulty:         888446610538 1WALNUT
Difficulty: 888446610538

$ ./vanitygen -v  -i 1WALNUT
Prefix difficulty:          27763956579 1WALNUT

The difficulty with and without the -i (ignore case) is different, and my ignore case is giving the same difficulty as your code dump.
It seems your version is looking for the all caps, but is showing difficulty equal to my ignore case command.
So all the probability is calculated based on a wrong number, it will probably take about 888/27 = 38 times longer to find a single key.
based on ~350Kkey/s about 20 days to hit the 50%



Slow but steady Android coin mining with NeoNeonMiner
BTC:1NeoArmnGyWHKfbje9JNWqw3tquMY7jHCw
tspacepilot
Legendary
*
Offline Offline

Activity: 1456
Merit: 1013


I may write code in exchange for bitcoins.


View Profile
March 23, 2015, 09:57:52 PM
 #2060

Code:
tspacepilot@god:~/src/vanitygen$ ./vanitygen -v 1WALNUT
Yeah, probably just bad luck then. 7-character prefix will take a while on most hardware and the bad end of variance scales accordingly.

If you're keen on having it, generate a private/public key pair, post the public key here, and maybe some kind folks will attempt a search for you.  See the discussion on split key generation a page or 2 back for details.

Right on, for the moment I've got no rush so I'll just let it crank away for a while.  If I get desperate sometime a week or so from now then I may just take you up on that.  Thanks TheRealSteve.

I'm not sure what version you are running, but I checked on my system:

Code:
$ ./vanitygen -v 1WALNUT
Prefix difficulty:         888446610538 1WALNUT
Difficulty: 888446610538

$ ./vanitygen -v  -i 1WALNUT
Prefix difficulty:          27763956579 1WALNUT

The difficulty with and without the -i (ignore case) is different, and my ignore case is giving the same difficulty as your code dump.
It seems your version is looking for the all caps, but is showing difficulty equal to my ignore case command.
So all the probability is calculated based on a wrong number, it will probably take about 888/27 = 38 times longer to find a single key.
based on ~350Kkey/s about 20 days to hit the 50%


Interesting.  I'm using a version that I checked out from git just last week.  I installed the build-deps for debian and then ran make and I was off and running.

Oh this, I look closer and I see that I've also got -i set, whoopsy!  That explains the descrepancy.  Given the fact that you can't have lower case "l" in a bitcoin address, I may just need to look into that split key thingy and/or use a better computer for this project Smiley

Thanks for pointing this out!
Pages: « 1 ... 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 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 ... 178 »
  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!