[GUIDE] How To Create Vanity Address (Segwit)

[feryjhie]

Special Thanks To:
1miau to create this thread [Guide] How to create your customized Bitcoin-Address (vanitygen) – step by step and Jean_Luc to make the application vanitysearch




Have you ever seen a bitcoin address like below
3MyCoinoA167kmgPprAidSvv5NoM3Nh6N3
bc1quantum898l8mx5pkvq2x250kkqsj7enpx3u4yt

If you want to create a vanity address like that so here the steps


1. Download Vanitysearch

You can download the latest VanitySearch 1.14



2. Turn off internet connection while generating your Bitcoin address

It’s also possible to create a vanity address when your internet connection is active, but for security reasons no internet connection is recommended. It would be even safer if you run the program on a computer that was never connected to the internet, but you can decide for yourself which security level is sufficient. It's always recommended to prefer high security standards to avoid any problems resulted by hacks because it's always possible that your device is compromised.
If you want maximal security you can generate your vanity address via split-key (Here the tutorials https://bitcointalk.org/index.php?topic=5144752.msg51126883#msg51126883).


3. Open Command Prompt

You can start the Command Prompt by a right-click on the Windows icon in the lower left corner of your screen and select Command Prompt (Administrator) or simply using the key combination Windows + R.

or

if you do it like that you can skip #4 if you open the command prompt directly from where your vanity files are stored:


- Go to the folder where vanitysearch is stored.
- Press CTRL+SHIFT+RightClick on an empty space within the folder (not on the executable/files), click "Open command window here". Now the command prompt opens.

(source: nc50lc)

4. Enter Path

The paths depend on where you have stored your VanitySearch files. I have saved these on E:\ in the folder Vanity. I have to enter the following code to find the vanitysearch.exe file:

C:\users\MSI>E:
E:\ cd vanity
E:\Vanity>vanitysearch.exe

Folder Vanity
File name vanitysearch.exe




5. Creating The Vanity Address

Here the list of parameters that you can use to create the vanity Address:


For this Tutor,  i want to create the 3FERY and bc1qfery address. But you need to know that not all characters are supported for SegWit addresses:

In addition to 0, O, I and l are not allowed:

Nested SegWit (3...) has to start with an uppercase letter or a number. For example, 3Fery works but 3fery not.
Native SegWit (bc1q...) doesn' support the letters / numbers 1 (except the 1 in bc1q), b, i and o. (1)

To create the 3FERY and bc1qfery address, so we need the following commands

-stop: Stop when all prefixes are found
 -o outputfile: Output results to the specified file (in this tutor i will save the file into save.txt)
3FERY and bc1qfery (the prefix that we want to create)

Your Command should be like this

Code:

E:\Vanity>vanitysearch.exe -stop -o save.txt 3FERY 

Code:

E:\Vanity>vanitysearch.exe -stop -o save.txt bc1qFERY

if you already type the command above then press enter. if vanitysearch has done searching your address then it will look like this


and your Private Key will be stored into file save.txt in the same folder as VanitySearch


Tada and here the address that i already created before
segwit: 3FERYMacdfMG7X6u75JEnxUD8LqqLiQeWK
bech32: bc1qferyrvvz0u3wkxcc2gj3v9595j4qrjmddmsvzm


6. Save your generated public and private key

Security is always very important when it comes to Bitcoin. Keep your generated private key very safe, because it’s like the password to your Bitcoins. You can write it down on a sheet of paper, store it in a safe place and save it also on a USB stick that you only use for your private keys.


7. Done!

Now, you have successfully created your own Bitcoin address. If you want to access it (like via Electrum) you can have a look here

in addition, i already creates my own vanity address
1FfFfFf26sVGsGKaR2MxNWESRhnDHdVBz
3FERY5GPg4e1KwxXPKb2pb46tntR44U3st
bc1qferyj60j2ecmlsh3tld256spe0zn3s7n6uf0z4

[1miau]

Very well explained!
I created some SegWit vanity addresses just a few days ago for my hot wallet (3HotfU4tPCaQdBE98WmYcmDzeC8C8UAx3F) and VanitySearch is just awesome. So much faster than vanitygen and SegWit addresses are possible.

But I noticed some additional "restrictions" for SegWit addresses, maybe you can add them:

Nested SegWit (3...) has to start with an uppercase letter or a number. For example 3Fery works but 3fery not.
Native SegWit (bc1q...) has some more "restrictions" and in addition to O, 0, I and l the letters / numbers 1 (except the 1 in bc1q), b, i and o won't work. So sad that I can't create bc1qmiau... 

[Rath_]

Would you mind adding information about obtaining a private key using the split key method? It's very useful if one doesn't have a powerful PC and want someone else to find the desired address. It's used by Loyce and DarkStar in this thread.

[feryjhie]

Would you mind adding information about obtaining a private key using the split key method? It's very useful if one doesn't have a powerful PC and want someone else to find the desired address. It's used by Loyce and DarkStar in this thread.

Oke i will try to make the tutor for creating vanity address using the split key method. Maybe it will be done tomorrow.

[o_e_l_e_o]

You've already linked to 1miau's thread which includes a section on being offline, but I think it would be worthwhile for you to include a similar statement in your own thread. Generating private keys (or even having private keys stored) on a computer with an active internet connection is a big security risk. At a minimum you should be running this program offline, but preferably on a permanently air-gapped device. If your air-gapped device isn't powerful enough to generate an address in a reasonable amount of time, then you can at least generate a split key whilst air-gapped.

[feryjhie]

You've already linked to 1miau's thread which includes a section on being offline, but I think it would be worthwhile for you to include a similar statement in your own thread. Generating private keys (or even having private keys stored) on a computer with an active internet connection is a big security risk. At a minimum you should be running this program offline, but preferably on a permanently air-gapped device. If your air-gapped device isn't powerful enough to generate an address in a reasonable amount of time, then you can at least generate a split key whilst air-gapped.

thank you i already add the part that we can generate an address while offline.
For the split key, i will try to make the tutorials later

[feryjhie]

because I see there are some people suggest making a tutorial about generating an address by using split-key.
The steps almost the same until in option 5 in this thread, so below are the steps


Generate a vanity address for a third party using split-key

as in this tutorials, i will take "fery" as the person that wants to create an address and "Jhie" as the person that creates the address using split-key


1. Generate Key Pair

Fery needs to generate a key pair in his computer then send to Jhie with the prefix bc1qtut0r.
So fery needs the following commands:

-s seed: Specify a seed for the base key (in this tutor i will use "FeryVanity")
-kp: Generate key pair

so the commands should be like this:

Code:

vanitysearch.exe -s "FeryVanity" -kp

if you already type the command above then press enter. if vanitysearch has done searching Key Pair then it will look like this

E:\Vanity>vanitysearch.exe -s "FeryVanity" -kp
Priv : Kzt1NiGnqSFgCi8rZwN5BBPFRbQYev6UC5tasD8ntuX7ZKMFa75x
Pub  : 03DB3DB24C230A2E16C3206D8EDC34ED38CEDC348F99C6A4DE9A30F363B63D623A

then save the generate key pair into a notepad


2. Generate the Address

After Fery found the Public Key, he needs to send it to Jhie so he will start the vanitysearch using Fery Public Key and the wanted Prefix (bc1qtut0r)
so Jhie needs the following commands:

-sp startPubKey: Start the search with a pubKey (for private key splitting)
 -stop: Stop when all prefixes are found
 -o outputfile: Output results to the specified file

so the commands should be like this:

Code:

VanitySearch.exe -sp 03DB3DB24C230A2E16C3206D8EDC34ED38CEDC348F99C6A4DE9A30F363B63D623A  -stop -o keyinfo.txt bc1qtut0r

if you already type the command above then press enter. if vanitysearch has done searching Partial Private Key then it will look like this


after that, it will generate a new file in the folder "keyinfo.txt" that contain a partial private key and the file will look like this


After Jhie generate the partial key he will send it to Fery


3. Generate the Final Private Key

After Fery received the partial Private key he needs to make a notepad file with the private key in it. In this case, we will still use the file keyinfo.txt.
Then Fery will reconstruct the final private key using her private key (the one generated in step 1) and the partial private key that we saved in keyinfo.txt

So Fery Needs the following Command:

-rp privkey partialkeyfile: Reconstruct final private key(s) from partial key(s) info.

so the commands should be like this:

Code:

VanitySearch.exe -rp Kzt1NiGnqSFgCi8rZwN5BBPFRbQYev6UC5tasD8ntuX7ZKMFa75x keyinfo.txt

if you already type the command above then press enter. the final Private key will be shown and it will look like this



Don't forget to save the private key

Code:

E:\Vanity - Copy>VanitySearch.exe -rp Kzt1NiGnqSFgCi8rZwN5BBPFRbQYev6UC5tasD8ntuX7ZKMFa75x keyinfo.txt

Pub Addr: bc1qtut0rvsvh5g805ssvpnz3uecgxuhe2dghev867
Priv (WIF): p2wpkh:L3kBT5VLfZBnrLZDaQQpnLgVYMVD2ZHME4mDwBx3XCSqRJSHxhWu
Priv (HEX): 0xC2B308D58D67B25A5206F436A0FDFC506997A014ED06307922B8B00494237EA3

4. Done!

Now, you have successfully created your own Bitcoin address. If you want to access it (like via Electrum) you can have a look here


*Reference
https://github.com/JeanLucPons/VanitySearch
https://bitcointalk.org/index.php?topic=5144752
https://bitcointalk.org/index.php?topic=5096373.0

[hodld0r]

i made a bech32 key with vanitysearch and imported the wif into bitcoin-qt 0.18.0 but it ends up giving me the old style with the 1 prefix.  i have bech32 enabled as default in the options; if i let the wallet generate a random key for me it is bech32.  so how to import a key as bech32 ?

[feryjhie]

i made a bech32 key with vanitysearch and imported the wif into bitcoin-qt 0.18.0 but it ends up giving me the old style with the 1 prefix.  i have bech32 enabled as default in the options; if i let the wallet generate a random key for me it is bech32.  so how to import a key as bech32 ?

you must import the private key full like "p2wpkh-p2sh:5priv.key" or "p2wpkh:5priv.key"

[nc50lc]

i made a bech32 key with vanitysearch and imported the wif into bitcoin-qt 0.18.0 but it ends up giving me the old style with the 1 prefix.  i have bech32 enabled as default in the options; if i let the wallet generate a random key for me it is bech32.  so how to import a key as bech32 ?

you must import the private key full like "p2wpkh-p2sh:5priv.key" or "p2wpkh:5priv.key"

AFAIK this will only work with Electrum.
Have you tried this prefix method with Bitcoin-qt or Bitcoin Core?

[joniboini]

i made a bech32 key with vanitysearch and imported the wif into bitcoin-qt 0.18.0 but it ends up giving me the old style with the 1 prefix.  i have bech32 enabled as default in the options; if i let the wallet generate a random key for me it is bech32.  so how to import a key as bech32 ?

Try this guide: [GUIDE] Importing Electrum Segwit Private Key Into Bitcoin Core (And Vice Versa)

[feryjhie]

i made a bech32 key with vanitysearch and imported the wif into bitcoin-qt 0.18.0 but it ends up giving me the old style with the 1 prefix.  i have bech32 enabled as default in the options; if i let the wallet generate a random key for me it is bech32.  so how to import a key as bech32 ?

Try this guide: [GUIDE] Importing Electrum Segwit Private Key Into Bitcoin Core (And Vice Versa)

I just try it but it does not work, i try using electrum 3.3.6 and i got this responds back Traceback (most recent call last):

AFAIK this will only work with Electrum.
Have you tried this prefix method with Bitcoin-qt or Bitcoin Core?

I haven't tried it yet with Bitcoin-qt or Bitcoin Core because i don't use it

[Thirdspace]

i made a bech32 key with vanitysearch and imported the wif into bitcoin-qt 0.18.0 but it ends up giving me the old style with the 1 prefix.  i have bech32 enabled as default in the options; if i let the wallet generate a random key for me it is bech32.  so how to import a key as bech32 ?

do this: addwitnessaddress yourOldStyle1PrefixAddress
it should return the bech32 address as a result, which indicates address has been imported successfully

[pandukelana2712]

-snip-
So sad that I can't create bc1qmiau... 

How about this: bc1qml4uujfkgcd7pfzvsukvs9v78l8jh8htea7pjj or bc1qmlauptfw2yhhzaj6pqr2dqt6g409g88x7ytt4a

use lowercase of (L)

[hodld0r]

i tried all the things suggested here and nothing worked.  addwitnessaddress command doesnt exist in bitcoin-qt, the electrum script in the other thread just returns p2pkh: prefix to the same private key, and bitcoin-qt does not recognize either p2wpkh: or p2pkh:

maybe it just wont work until a future version of bitcoin-qt

[jademaxsuy]

i tried all the things suggested here and nothing worked.  addwitnessaddress command doesnt exist in bitcoin-qt, the electrum script in the other thread just returns p2pkh: prefix to the same private key, and bitcoin-qt does not recognize either p2wpkh: or p2pkh:

maybe it just wont work until a future version of bitcoin-qt

As per post as suggested that it needs a good PC for this to work out. Maybe your PC does not compatible in creating a btc vanity address or try checking the steps again and double check if it has being done correctly. There are times that process might not be followed like forgetting a tiny details in the process.

[hodld0r]

ok i figured out how to import bech32 in the core client.

  -walletimplicitsegwit
       Support segwit when restoring wallet backups and importing keys
       (default: 0)

if you use that commandline option and import the normal wif as usual it will give you the bech32 pubkey, though when i go to the "receiving keys" window it lists all 3 possibilities, a key with a 1 prefix, another key with a 3 prefix, and the actual bech32 key i am after.  might not be a way to stop it from doing that.. is kind of annoying but whatever

[bL4nkcode]

Native SegWit (bc1q...) has some more "restrictions" and in addition to O, 0, I and l the letters / numbers 1 (except the 1 in bc1q), b, i and o won't work. So sad that I can't create bc1qmiau... 

What an unfortunate, can't create even mine as bc1qbL4nk for native but will do on nested one.

[roosbit]

nice tutorial managed to create my first vanity segwit address

Unfortunately could not get something close to my name because of the (Unreachable, 31h1 to 3R2c only)"

thought the restriction was for these characters>>" 0, O, I and l are not allowed"

Anyway, now just playing around with this trying to find me some cool address

[feryjhie]

i made a bech32 key with vanitysearch and imported the wif into bitcoin-qt 0.18.0 but it ends up giving me the old style with the 1 prefix.  i have bech32 enabled as default in the options; if i let the wallet generate a random key for me it is bech32.  so how to import a key as bech32 ?

you must import the private key full like "p2wpkh-p2sh:5priv.key" or "p2wpkh:5priv.key"

AFAIK this will only work with Electrum.
Have you tried this prefix method with Bitcoin-qt or Bitcoin Core?

i saw someone who using bitcoin core or Bitcoin-qt and doing this and his address added into their wallet
the steps below

It's possible, you just need to use importprivkey command on Bitcoin Core console. I've tried it with example from private key and i got correct address.

• Import private key (and rescan blockchain)

Code:

importprivkey L2qvghanHHov914THEzDMTpAyoRmxo7Rh85FLE9oKwYUrycWqudp

• Import private key, giving label to the address and skip scanning blockchain to find all transaction correlated to theaddress

Code:

importprivkey L37xBVcFGeAZ9Tii7igqXBWmfiBhiwwiKQmchNXPV2LNREXQDLCp "Main address" false