Topic: VanitySearch (Yet another address prefix finder) - page 25. (Read 32072 times)

Can someone help me with a small issue..

I have an old i3 2012 CPU, that is currently only generating around 650 addresses /sec with 4 threads.


https://i.imgur.com/flQUc6x.png


The thing is, more than a week ago it used to do around 21000 addresses /sec with the same 4 threads.

Why am I only able to generate 600 addresses /sec now? It used to do much more...

This is the current config I've set and not changed since:

start %USERPROFILE%\Desktop\VanitySearch.exe -c -o output.txt 1*


Why is it only doing 600 adresses /sec instead of 21000 per /sec as it used?

I don't get it.

Hi, Jean Luc

Is it possible to add a couple of extra features to VanitySearch ?:
- the ability to reuse a Base Key that has already been used, the '-s' parameter is unsuitable (it generates a new key)
- saving the parameters of the path traveled and resuming the program (power failure, the need to turn off the computer, etc.)

With the given parameters [Prob 100.0%] [99% in 00:00:00], the program continues to use gpu, but after reaching 100% and stopping the timer, no keys were found in 4 hours, is this an error or VanitySearch continues to work?

Thank

How did you get 10M addresses? I assume there might be a script that extracts addresses from the blockchain somehow, is it?

That's how it goes. Apparently AMD will stay aside

Do you plan to work AMD cards?

Yes, but not all types of addresses created using vanity address generators.
It's exclusive to SegWit addresses generated from an "Uncompressed Public key".

And yes, now, you cannot import 'uncompressed WIF prv key' as SegWit to Electrum.

Thank you for the answer. I have one more question though: when you mention the transactions rejected by most of the nodes, you mean the transactions which were created on those previous versions of VanityGen (VanitySearch) / Electrum, right? Meaning that now the problem is not present anymore. So now if I create a nested / native SegWit address with VanitySearch, then if I import it in Electrum and if I sent funds to it, I'll be able afterwards to spend the respective funds. Did I understand correctly?

About the topic you mentioned, I remember I read it a while ago, but I did not pay too much attention to it though.

That issue was brought by both old versions of Electrum and whatever Vanity address generator they've used must be because of lack of research for SegWit or lack of public info or both.

For Electrum: the older version like v3.3.6 (When SegWit was kinda new), allows the user to create an imported wallet
using an 'uncompressed WIF private key' as SegWit P2WPKH (starts with bc1) or P2WPKH-P2SH (starts with 3).
Reference: https://www.reddit.com/r/Electrum/comments/bec22p/potential_loss_of_funds_if_import_uncompressed/
That's fixed (removed) in the later versions.

For the vanity address generator: There was an option to create SegWit addresses using uncompressed public key flag as stated by others.

To answer your question, transactions created using those SegWit addresses are "non-standard" which means it will be rejected by most nodes when you try to broadcast it.
The only way to spend the funds from them is to send the 'Signed RAW Transaction' directly to a solo miner/pool and ask them to include it in a block.
Here's an example of how "hard" it is to spend them: https://bitcointalksearch.org/topic/1-btc-bounty-5192454

Just as you mentioned not wanting to read 37 pages of this topic, I myself did not want to read a step by step guide on something I already knew how to do. Others mentioned vanitygen as well. All good.

I understand the concerns...no one wants to lose money by doing something someone has already done. No doubt. Maybe if someone has "lost" money via this way, they can chime in.

Oh, I see. Well, yes, I was using VanitySearch. Also, if you read the entire topic of 1miau (the one about VanityGen), you'll see that at the end he also mentions about VanitySearch


Thank you for the confirmation. I'd like to see though if there are users which generated nested and native SegWit addresses with VanitySearch. Meaning that I'd like to know if they were able to spend funds from these addresses (the ones starting with 3 and bc1).

Was merely asking since vanitygen was mentioned a few times in regards to your post and since the 1miau post was titled "How to create your customized Bitcoin-Address (vanitygen) – step by step".

I've never had an issues receiving sending spending eating any BTC from Electrum wallet using any Legacy address generated by vanitysearch, in which I had the private keys.

So, for the fifth time I never created an address using -u parameter. This happened to 1miau and to other members which also lost funds after creating an address with this parameter, funding it with BTC, importing it into Electrum and trying to spend the funds. This never happened to me and I stated that yesterday four times (here (1), here (2), here (3) and here (4). My only problem was with the watch-only address.

Regarding the creation of nested addresses using VanitySearch (addresses starting with 3), you can use this syntax: vanitysearch.exe -stop -o save.txt 3FERY. The program can be used also for generating native SegWit addresses (you can find more info here: [GUIDE] How To Create Vanity Address (Segwit).


Yes, I knew that, but thanks for pointing it out


Roger that. So the address is watch-only just in case you insert the public key. If you insert the private key, you can use the funds. Well, it sounds good in theory, but I'm waiting someone to confirm that he sent funds to a vanity address, then he imported it in Electrum, he sent funds to it and afterwards he was able to spend funds from it I won't take this risk.

Sorry but this is simply not true. You are misreading the message Electrum presents to you. As stated in my post above as well: Electrum warns you about the fact when you use the form to enter an address it will be watch-only by default. That's all, there is no bigger conspiracy here

Thank you for the detailed information.

First of all regarding the picture labeled 3: All Electrum is saying when you enter an address to import, instead of a private key, it will be watch only. The message itself is valid for any address since you don't import the private key there is no way Electrum can use the address for spending. So regarding your first sentence in the quote above: Electrum gave a general warning on importing addresses instead of private keys. This has nothing to do with you entering a valid WIF for a private key. The import went fine and you can use the address like normal.

On to the next one: You created a new wallet and now you get a bunch of addresses. That is exactly what's expected. A wallet is simply a collection of private keys (which lead to addresses). When you create a new wallet a bunch of addresses will be allocated in that wallet. The Change-addresses are the addresses that will be used to send any left-overs to when the inputs of a transaction exceeds the outputs and fee. In short: In the first step you imported a single address, since your wallet was brand new it now only contains that single address. In the step pictured in image 5 you create a new wallet from scratch including a great number of addresses.

Regarding -u parameter: Edit: It is still there in latest version 1.18. But how did you create a 3-address using VanitySearch and -u parameter in the first place?

And finally: If you look at screenshot numbered 6 there is a "Info" button. If you press it you can see you can import a nested segwit address using "p2wpkh-p2sh:WIF"

Lol I thought it' obvious that since I'm writing in Jean_Luc's topic it means I'm using his program.

Regarding the P2PKH part: it's the same if you write this or if you write only the private key. When that Electrum windows opens (the one where you insert the address, no matter if you insert the public key, the private key or the private key with the P2PKH part) it says from the beginning that the address will be a watch-only one. So after you reach that Electrum window, without inserting any address there, you'll see the warning about having a watch-only address. As far as I understand, it's something related to Electrum, not to VanitySearch. But still, it means you can't spend funds if you send them to that address, since it is a watch-only address.

Soooo are you using VanitySearch by JeanLuc or some variation of vanitygen??!!

Also, I've never added the P2PKH: part when importing a wallet via private key; just the private key, starting with L or K. It's almost like saying it's not a valid private key and making it watch only; like if you add an address without the private key.

Ok, so I created a batch of legacy addresses with VanitySearch. I selected to import an address in Electrum. At this point, Electrum warned that the imported address is a watch-only type. After importing it, it is shown in Electrum and it has the status "receiving", which I don't know what it means. Maybe the address can only receive funds and not send funds?

Then I created a new wallet in Electrum. It generated a list of addresses which had two types: "receiving" and "change" (I don't know what represents the "change" type). What's certain is that the generated addresses had two types and that in this case, Electrum didn't warn about having a watch-only address.

You can see more details in the picture below.

Regarding the -u parameter  it still exists in VanitySearch. I don't know if it is still functional, but it is still displayed when you run the program (with -h parameter, for seeing all available commands).

Besides, I did not see any option for creating Nested SegWit addresses... Edit: it works!

Will this search for a prefix that is assigned to another coin. Vanitygen can do this with the -X command, which allows for prefix version. Does this have anything similar?