Author

Topic: can I generate my own Bitcoin Adress? (Read 474 times)

legendary
Activity: 3038
Merit: 4418
Crypto Swap Exchange
June 24, 2020, 11:39:34 AM
#10
If you will make a vanity gen addy then do it by yourself because they are some online services who offer vanity addys, but it isn't a good idea to let them generate your private key.
Split key generation is safe. If you were to use an online service, find one with split key generation available. It wouldn't be possible for anyone to spend the funds from your vanity address without your part private key.

Avoid those who generate the entire private key for you at all cost. There are quite a few scam sites which will capture your private keys.
legendary
Activity: 3346
Merit: 3130
June 24, 2020, 10:25:20 AM
#9
@ranochigo
thank you. It makes sense

If you will make a vanity gen addy then do it by yourself because they are some online services who offer vanity addys, but it isn't a good idea to let them generate your private key.

Do not get attached to your addresses. You should use a new address for each transaction. Just a small tip to stay secure Smiley

And these are words from satoshi nakamoto, bitcoin wasn't made to recycle the same addy, the right way to use it is by generating a new address for each transaction.
legendary
Activity: 3612
Merit: 5297
https://merel.mobi => buy facemasks with BTC/LTC
June 24, 2020, 06:27:50 AM
#8
Do not get attached to your addresses. You should use a new address for each transaction. Just a small tip to stay secure Smiley

This is true because of 2 reasons:
  • You'll decrease your privacy if you re-use your address
  • As soon as you spend an unspent output funding your address, your public key is included into the spending transaction. It's not a problem per sé, but it would make the theoretical chance of somebody finding your private key a little bit bigger... Still the odds are incredibly small (small enough to say they're ~0). So, in reality, i wouldn't worry about this, it's just that the theoretical odds have increased, but not enough to start worrying

This being said, vanity addresses usually do get re-used. For example, i re-use my vanity address all the time, i do coinjoin or mix most of my funds before i transfer them to my hardware wallet tough. And i don't really care for the fact my public key is known...
https://blockchair.com/bitcoin/address/1MocACiWLM8bYn8pCrYjy6uHq4U3CkxLaa
newbie
Activity: 27
Merit: 0
June 24, 2020, 06:21:55 AM
#7
Do not get attached to your addresses. You should use a new address for each transaction. Just a small tip to stay secure Smiley
legendary
Activity: 3472
Merit: 10611
June 14, 2020, 09:08:00 PM
#6
@ranochigo
thank you. It makes sense
You should be able to set around 6 hex digit easily with a normal gpu

addresses use either base58 or bech32 encoding. they do NOT use hexadecimal. so when you want to create a vanity address (an address with custom characters) you have to use base58/bech32 characters.
legendary
Activity: 2352
Merit: 6089
bitcoindata.science
jr. member
Activity: 72
Merit: 2
June 14, 2020, 02:04:19 PM
#4
@ranochigo
thank you. It makes sense
You should be able to set around 6 hex digit easily with a normal gpu
newbie
Activity: 10
Merit: 2
June 14, 2020, 11:54:19 AM
#3
@ranochigo
thank you. It makes sense
legendary
Activity: 3038
Merit: 4418
Crypto Swap Exchange
June 14, 2020, 11:52:36 AM
#2
Its called a vanity addresses. Since you can't reverse engineer your public key hash to your ECDSA private and public key, the only way to obtain a vanity address is to bruteforce and generate millions of addresses. That is the main reason.

It gets harder the more letters you specify.
newbie
Activity: 10
Merit: 2
June 14, 2020, 11:43:30 AM
#1
hey,
I do understand, that if I want a to get a Bitcoin Adress, me or the a generator chooses by chance a number from a very big pool of number possibilities, then get multilied with a Bais Point on the elliptic curve and so on. But I wondered what if I want to have an Adress like: 1234BATMAN567? I know that a derivation from BItcoin Adress to the private key is not possible. But is that the only reason?
Jump to: