Vanity Pool - vanity address generator pool

[th3nolo]

Sorry, I have no experience with that particular software. I'm using old-school vanitygen, which is written in C.

A segmentation violation usually means the application has tried to write (and possibly read) an area of memory that is outside the area allocated to it. "addr=0x8" looks like an odd address to be accessing.

I don't know much about Go - is the source compiled to an executable? If so, there may be problems using a newer compiler to build from older source (or vice versa).

Yes, the source code it's compiled to an executable.
I will try to use an older version of GO if the executable it works I will let you know.
Also, I'll try to push the instructions on Github to ease the work to anyone.

[1715152660]

1715152660

[1715152660]

1715152660

[1715152660]

1715152660

[b2oba92i]

No new messages since a while, has anyone used it in 2021 ?

[ThePiachu]

No new messages since a while, has anyone used it in 2021 ?

The Pool should still be up, haven't heard of anyone complain about it in awhile.

[Timelord2067]

No new messages since a while, has anyone used it in 2021 ?

The Pool should still be up, haven't heard of anyone complain about it in awhile.

Just because some of us have given up trying to connect to your pool (or having been unable to submit a result when one is found) does not equate to "no one having any complaints"

It might be worth checking in on this thread once in a while given the last time you posted in this thread was 2018-05-20, 07:10:04.  (i.e. three years and three days ago)

 

[vjudeu]

Is it possible to get bech32 address in this pool? Now I am mining "bc1qtapr00t" on my CPU, but willing to pay someone for a few hundred of such vanity addresses.

[vjudeu]

It's ironic to generate Bech32 v0 (bc1q) address with prefix "tapr00t" because Taproot use Bech32 v1 (bc1p).

As long as taproot is not active, using bc1p address is nonstandard and any miner could take that coins without any signatures. Also, it is the only way I know about to show support for taproot without being a miner and without increasing transaction size.

[LoyceV]

Is it possible to get bech32 address in this pool? Now I am mining "bc1qtapr00t" on my CPU, but willing to pay someone for a few hundred of such vanity addresses.

DarkStar_ tried to use split key on Segwit addresses. It looks like it's possible, but you'll need to put the private keys back together in VanitySearch yourself. For a couple hundred addresses that might be too much.

I've never tried Segwit vanity myself, but "1taproot" would take 45 days for 50% chance on my old laptop GPU. Have you considered a pay by the hour VPS with GPU? I've looked into Scaleway a while back, but never tried it.
I can't tell you if VanitySearch will work on that GPU though.

[NotATether]

I can't tell you if VanitySearch will work on that GPU though.

It will work, the P100 has a high enough CUDA compete cap to run Vanitysearch.

[vjudeu]

I've never tried Segwit vanity myself, but "1taproot" would take 45 days for 50% chance on my old laptop GPU.

You probably miscalculated something (or maybe I am extremely lucky), because when using vanitybech it took me one week per address on my CPU. One Segwit char means five bits, so seven chars means 35 bits, around 32 bits per day, so around 8 days.

[LoyceV]

I've never tried Segwit vanity myself, but "1taproot" would take 45 days for 50% chance on my old laptop GPU.

You probably miscalculated something (or maybe I am extremely lucky), because when using vanitybech it took me one week per address on my CPU. One Segwit char means five bits, so seven chars means 35 bits, around 32 bits per day, so around 8 days.

Oclvanitygen gives me the estimate for 50% chance, so I didn't miscalculate it. But I've seen modern videocards that are 100 times faster than mine.
If you're using CPU, you could probably get much better results by switching to GPU.

Can I be curious: What's your plan with hundreds of bc1qtapr00t addresses?

[nc50lc]

-snip- because when using vanitybech it took me one week per address on my CPU. One Segwit char means five bits, so seven chars means 35 bits, around 32 bits per day, so around 8 days.

"bc1qtapr00t" has a quite low difficulty of 34359738368 with VanitySearch (Official Thread link).
That'll only take a few minutes using a modern Nvidia GPU or about an hour with an Intel 4th Gen processor or equivalent.

What I'm saying is, paying $100+ isn't necessary.

Sample (please don't use):

Code:

PubAddress: bc1qtapr00t3ly2ravzkzv5nurcqmxqgm5l3yczt4c
Priv (WIF): p2wpkh:L2GfeCMuGH5uFds5GBnND1vKGt8V5FXxy9ZhG6a1ErbFEFBq8m2T
Priv (HEX): 0x96B52ED9C212D3D51FA26E14C2E7EAFF9309FEA9D93A6E677CB294D8FFA7CD4C

[Toshko]

How long is this going to take?

Difficulty: 55527913158 [Prob 2.9%][50% in 2.4d]

[nc50lc]

How long is this going to take?

Difficulty: 55527913158 [Prob 2.9%][50% in 2.4d]

Always base it on that "50% in <n>d".
In your case, It may take more more than 2 to 5 days or if you're lucky, within a few hours if you're lucky.

[NotATether]

How long is this going to take?

Difficulty: 55527913158 [Prob 2.9%][50% in 2.4d]

It's displayed as time to 50% because of the birthday paradox, where the probabilities are such that you'll find a surprisingly large amount of items by that mark.

Beyond the 50% mark, it tends to take much longer periods of time to exhaust 100%, and not necessarily the same time it took to exhaust 50%.

[Toshko]

This really doesn't seem long for a 14 year old laptop and a 6 letter phrase. Isn't it supposed to be more difficult?

[NotATether]

This really doesn't seem long for a 14 year old laptop and a 6 letter phrase. Isn't it supposed to be more difficult?

Depends on whether you're searching for bc1 or 1 address. bc1 is not case sensitive which greatly contributes to faster times since the program does not have to consider every combination of uppercase and lowercase letter, but a normal 1 search is case sensitive.

Considering that 4-5 characters (+ case sensitive) can be found almost instantly, it's not surprising that 50% of 6-char search space is exhausted in a few days on old hardware. Newer computers have faster cores with more threads and can search the same 50% of space in several hours.

[Toshko]

This really doesn't seem long for a 14 year old laptop and a 6 letter phrase. Isn't it supposed to be more difficult?

Depends on whether you're searching for bc1 or 1 address. bc1 is not case sensitive which greatly contributes to faster times since the program does not have to consider every combination of uppercase and lowercase letter, but a normal 1 search is case sensitive.

Considering that 4-5 characters (+ case sensitive) can be found almost instantly, it's not surprising that 50% of 6-char search space is exhausted in a few days on old hardware. Newer computers have faster cores with more threads and can search the same 50% of space in several hours.

Thank you - this is really a great explanation right here.

[JuanPabloCuervo]

-----
i know it´s a crazy idea, but i can´t resist asking...

¿why Not Brute-Force the 1 Million BTC Satoshi Nakamoto address ?
they are waiting...

i know it takes a trillion years with 1x GPU,
but...
a Pool with million workers..

much more interesting / fun than mining on nicehashminer

Reward is 0 until Private Keys are found..
Reward = coins found / workers worked time.

No login, No registration.
Worker = 1My_BTC_address.worker_name
because there are many Elvis Satoshi Nakamoto Impersonators with Big Teeth Lawyers.
https://en.wikipedia.org/wiki/Elvis_impersonator

must be Tor socks, onion
private/home Proxy also nice.

IF the keys are found, and they have your IP,
there will be million More Elvis Satoshi Nakamoto´s,
and a trillion lawsuits.

IF Satoshi Nakamoto is still alive, in Guantanamo Bay or something,
https://en.wikipedia.org/wiki/Guantánamo_Bay
they will get the Keys,
just needs more motivation.

the owner of the PrvKeys just needs to move the coins to a different wallet,
and all the Brute-Force effort is lost/gone.
No risk for the Owner of the coins, IF still alive and has control of the keys.

Probably there are Secret efforts to BruteForce the keys,
why Not make more competition.?

1BitcoinEaterAddressDontSend
Difficulty: 1.6209E+47
Time: 3.3E+33
3.3 decillion years.

https://en.bitcoin.it/wiki/Vanitygen


if we dont start Now, those Decillion years will never end.

another option is the BitFinex / MtGox stolen coins.
same effort but reward is Not as Big & Juicy.

-----------------------
Related:
https://bitcointalk.org/index.php?topic=25804
https://bitcointalk.org/index.php?topic=90587.0
https://bitcointalk.org/index.php?topic=84569.0

[NotATether]

i know it takes a trillion years with 1x GPU,
but...
a Pool with million workers..

much more interesting / fun than mining on nicehashminer

Unless some parts or range of these private keys are already known the difficulty is still going to be too high for a million pool workers, I mean it's still 2^256 keys ftw, you might as well find everyone else's private keys along the way and demonstrate the weakness of Secp256k1.

[vjudeu]

What's your plan with hundreds of bc1qtapr00t addresses?

The problem with vanity addresses is that if you have some unique prefix, then you can be easily identified. But: if there are many people using the same prefix, if there is even some small network using only such prefixes, then it becomes harder. Reusing addresses is a bad idea, because all of them are linked. But if you want to have vanity address and you want to avoid address reuse, then you need many of such addresses, as many as the number of transactions you want to do. If you have some small network where everyone uses "bc1qtapr00t" addresses, then anyone knows that you are a part of such network, but nobody knows who you are or with who you transacted.

My plan is to create mainnet-based test network, where you deposit coins by sending them to bc1qtapr00t, then you can make test transactions inside this network, and then you withdraw your coins by moving them on mainnet. That kind of test coins will be backed 1:1 by BTC, but will have some features that are not present on mainnet. To keep coins inside of this test network, many addresses are needed to avoid address reuse. Vanity addresses are needed for advertising: in this way you can show people that there is for example some network with taproot features.

Taproot was just an example, more features will come, and then there will be no need to mine some test coins again, because you could easily move coins from "bc1qtapr00t" test chain to "bc1qtestnet", just by creating a single BTC transaction. Also, some parts of that chain could be discarded in the future, because when coins will move on BTC, then old coins from that test chain could be removed without causing any problems in full chain validation and initial test chain download.