FYI reverting back to Version 1.14 seems to run without a problem
,Am I doing something wrong or version 1.15 is bugged?I guess the old saying of "If it ain't broke, don't fix it" is what am looking at atm.
Topic: [GUIDE] How To Create Vanity Address (Segwit) - page 2. (Read 1853 times)
Has anybody tried VanitySearch 1.15 , I kept getting access denied when trying to create a Vanity Address after using this code >> E:\Vanity>vanitysearch.exe -stop -o save.txt 3XXX <<< even after running CMD as an administrator
FYI reverting back to Version 1.14 seems to run without a problem,Am I doing something wrong or version 1.15 is bugged?
I guess the old saying of "If it ain't broke, don't fix it" is what am looking at atm.
FYI reverting back to Version 1.14 seems to run without a problem
,Am I doing something wrong or version 1.15 is bugged?I guess the old saying of "If it ain't broke, don't fix it" is what am looking at atm.
Are this for x64 windows, correct?
You know how to fix my problem?, got error when to star running
You know how to fix my problem?, got error when to star running
Quote
The program can't start because MSVCP140.dll is missing from your computer.
Try reinstalling the program to fix this problem
Try reinstalling the program to fix this problem
Same here.
Looks like you guys didn't install Visual C++ Redistributable Packages / it's corrupted, you can download it at https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads
AFAIK you need to download 2015 or 2012 version.
~
Are this for x64 windows, correct?You know how to fix my problem?, got error when to star running
Quote
The program can't start because MSVCP140.dll is missing from your computer.
Try reinstalling the program to fix this problem
Try reinstalling the program to fix this problem
~
Are this for x64 windows, correct?You know how to fix my problem?, got error when to star running
Quote
The program can't start because MSVCP140.dll is missing from your computer.
Try reinstalling the program to fix this problem
Try reinstalling the program to fix this problem
I've just tried vanitygen P2SH and 3R2c works:
Code:
vanitygen -F script 3R2c
Difficulty: 86484
Pattern: 3R2c
P2SHAddress: 3R2cNJdWKc2zLt26wq2NdaUCgRCgqdDViK
Address: 1HwqDVMCpVJULBeYpzbLNYs6L87MN7YG3x
Privkey: 5KWRuPLBsrSAoPFJqSrVuf9XYGxtfWo4S9wcPj3Zj67u4oTpN39
did you just generate an address from vanitygen?
as i know that vanitygen don't support segwit address yet
That's true, but the address from vanitygen isn't SegWit, it's just a simple P2SH (pay to script hash) address. Nested SegWit are P2SH-P2WPKH and that's not possible to create from vanitygen. But both addresses, P2SH (non-segwit) and P2SH-P2WPKH (segwit) are starting with 3...
Here's some reference to the original vanitygen discussion:
I'm not sure what the requirements are exactly, but this works:
Only CPU though, and no bc1-address. Using non-native SegWit feels a bit like a 50% solution.
Code:
./vanitygen -F script 333333
Difficulty: 264104224
Pattern: 333333
P2SHAddress: 333333dirmCEYVJGZavhjt2fmWL15boJYx
Address: 12ZEW67DZX9LP1rNQq6bSnw1mnkemKvo6H
Privkey: 5J48B7JDChgvAUGPA5p6yvjwZtyFufJizc6jFSci6Jwu9KzQdFh
Only CPU though, and no bc1-address. Using non-native SegWit feels a bit like a 50% solution.
This is not "non-native SegWit" address, is it?
This is just a standard non-segwit P2SH address, right? (non-segwit multi-signature address)
Since this is not a segwit P2SH-P2WPKH address, then it won't save us on tx size and fee
I've just tried vanitygen P2SH and 3R2c works:
Code:
vanitygen -F script 3R2c
Difficulty: 86484
Pattern: 3R2c
P2SHAddress: 3R2cNJdWKc2zLt26wq2NdaUCgRCgqdDViK
Address: 1HwqDVMCpVJULBeYpzbLNYs6L87MN7YG3x
Privkey: 5KWRuPLBsrSAoPFJqSrVuf9XYGxtfWo4S9wcPj3Zj67u4oTpN39
did you just generate an address from vanitygen? as i know that vanitygen don't support segwit address yet
I guess you tried to create a nested SegWit address like 3roosbit or 3roos, right?
For nested SegWit your second character needs to be uppercase like 3Roosbit or 3Roos. If the second character after 3.. is lowercase the creation doesn't work.
For nested SegWit your second character needs to be uppercase like 3Roosbit or 3Roos. If the second character after 3.. is lowercase the creation doesn't work.
I've asked this in vanitygen thread awhile ago and someone answered like this
3r is out of range, 3N is the highest possible prefix, 123456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnopqrstuvwxyz.
It is not about impossible sequence, address is a number in some range which is encoded using using Base58 coding.
It is not about impossible sequence, address is a number in some range which is encoded using using Base58 coding.
Code:
./vanitygen -F script -C BTC 3r
Generating BTC Address
Prefix '3r' not possible
edit: I think I was misinformed about the possible prefix
it is possible to find 3R..., but not possible for 3Ro... because the range is up to 3R2c as mentioned by roosbit
I've just tried vanitygen P2SH and 3R2c works:
Code:
vanitygen -F script 3R2c
Difficulty: 86484
Pattern: 3R2c
P2SHAddress: 3R2cNJdWKc2zLt26wq2NdaUCgRCgqdDViK
Address: 1HwqDVMCpVJULBeYpzbLNYs6L87MN7YG3x
Privkey: 5KWRuPLBsrSAoPFJqSrVuf9XYGxtfWo4S9wcPj3Zj67u4oTpN39
I guess you tried to create a nested SegWit address like 3roosbit or 3roos, right?
For nested SegWit your second character needs to be uppercase like 3Roosbit or 3Roos. If the second character after 3.. is lowercase the creation doesn't work.
For nested SegWit your second character needs to be uppercase like 3Roosbit or 3Roos. If the second character after 3.. is lowercase the creation doesn't work.
I've asked this in vanitygen thread awhile ago and someone answered like this
3r is out of range, 3N is the highest possible prefix, 123456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnopqrstuvwxyz.
It is not about impossible sequence, address is a number in some range which is encoded using using Base58 coding.
It is not about impossible sequence, address is a number in some range which is encoded using using Base58 coding.
Code:
./vanitygen -F script -C BTC 3r
Generating BTC Address
Prefix '3r' not possible
edit: I think I was misinformed about the possible prefix
it is possible to find 3R..., but not possible for 3Ro... because the range is up to 3R2c as mentioned by roosbit
-snip-
So sad that I can't create bc1qmiau...
How about this: bc1qml4uujfkgcd7pfzvsukvs9v78l8jh8htea7pjj or bc1qmlauptfw2yhhzaj6pqr2dqt6g409g88x7ytt4aSo sad that I can't create bc1qmiau...
use lowercase of (L)
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
I guess you tried to create a nested SegWit address like 3roosbit or 3roos, right? 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
For nested SegWit your second character needs to be uppercase like 3Roosbit or 3Roos. If the second character after 3.. is lowercase the creation doesn't work.
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"Have you tried this prefix method with Bitcoin-qt or Bitcoin Core?
You just need remove the prefix which indicate address type (p2pkh, p2sh, p2wpkh-p2sh, p2wpkh or p2wph) if you want import private key generated from vanitygen to Bitcoin Core
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"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
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
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
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.
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
-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
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. maybe it just wont work until a future version of bitcoin-qt
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
maybe it just wont work until a future version of bitcoin-qt
hero member
Activity: 728
Merit: 1006
BountyPortal Supporter & Hhampuz is my manager
-snip-
So sad that I can't create bc1qmiau...
How about this: bc1qml4uujfkgcd7pfzvsukvs9v78l8jh8htea7pjj or bc1qmlauptfw2yhhzaj6pqr2dqt6g409g88x7ytt4aSo sad that I can't create bc1qmiau...
use lowercase of (L)
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
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?
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
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)
Jump to: