How was this address created

[voprosbitcoin]

I came across this address 1BitcoinEaterAddressDontSendf59kue
To generate a 1BitcoinEaterAddressDontSend address using VanityGen, you will need 3.3 E+33 or 3.3 decillion years.
Please tell me how you can generate an address of this length and with what?
Here is a link to the transactions https://btc.com/1BitcoinEaterAddressDontSendf59kuE
or do I not understand something?

[1714124756]

1714124756

[1714124756]

1714124756

[1714124756]

1714124756

[1714124756]

1714124756

[1714124756]

1714124756

[1714124756]

1714124756

[AB de Royse777]

This address only received bitcoin and never sent any coin. This is actually a burning address, an address without private key. You can send coins but you can not receive coins from this address.

Anyone can send coin to any address which starts with the standard format for bitcoin address.

1helloThisISaTestAddressAgainDoNotSendAnyCoin59Test - if I am not wrong then anyone can send sats to this address too which I just made up.

[NeuroticFish]

Yep, for burn address the creation is much easier. I've done a quick search and I've found a very good old answer on how this kind of addresses can be created.
Again, it's a burn address, so the chance somebody would ever spend those coins is very close to 0.

And the promised post:

Google is always your best friend:
https://en.bitcoin.it/wiki/Proof_of_burn

This one is step by step:
https://bitcoin.stackexchange.com/questions/1851/how-to-generate-a-valid-bitcoin-address-for-destroying-bitcoins

A gist:
https://gist.github.com/CoinWhisperer/6d673f1f3d13da1611cd

[voprosbitcoin]

This address only received bitcoin and never sent any coin. This is actually a burning address, an address without private key. You can send coins but you can not receive coins from this address.

Anyone can send coin to any address which starts with the standard format for bitcoin address.

1helloThisISaTestAddressAgainDoNotSendAnyCoin59Test - if I am not wrong then anyone can send sats to this address too which I just made up.

Thanks for the answer. I understand about the address. I do not understand why and who needed to send coins to this address?

[AB de Royse777]

This could be another address: 1testBitcoinAddressDoNotSendSatsEv
I just created it for fun, no private key.

34 characters, without the uppercase letter "O", uppercase letter "I", lowercase letter "l", and the number "0".

Thanks for the answer. I understand about the address. I do not understand why and who needed to send coins to this address?

Maybe it's fun for these people who sent the coins to that address. We are amazing creature.

[NeuroticFish]

1helloThisISaTestAddressAgainDoNotSendAnyCoin59Test - if I am not wrong then anyone can send sats to this address too which I just made up.

Be careful, AFAIK the last part of the address is a checksum and if it's not correct, most wallets will not allow sending coins there.

[AB de Royse777]

Be careful, AFAIK the last part of the address is a checksum and if it's not correct, most wallets will not allow sending coins there.

I know people try stupid things however I hope in this case we will not see any stupid to send any coin. :-D

I checked with Electrum and it always gives this error of "invalid line..." even with the address OP posted. So, I assume Electrum has some built-in feature to prevent this sorts of lose.

[ranochigo]

I know people try stupid things however I hope in this case we will not see any stupid to send any coin. :-D

I checked with Electrum and it always gives this error of "invalid line..." even with the address OP posted. So, I assume Electrum has some built-in feature to prevent this sorts of lose.

The address that OP posted has the checksum (ie. the final few characters) in the wrong capitalisation. It is easy to generate a burn address with a correct checksum and it is the intended purpose; for address to be valid and allow funds to be burned. Electrum (or any other wallets) do not have any feature to prevent people from sending funds to burn address. They do however, have features to prevent users attempting to send Bitcoins to invalid addresses which would be rejected by the network anyways.

Just for the sake of clarity, there is a private key associated with that address. The only thing is that there is a very low probability that anyone would currently have access to that private key.

[nc50lc]

Please tell me how you can generate an address of this length and with what?

They call those addresses "Proof of Burn" and they can be created by either scripts, tools or online sites like https://gobittest.appspot.com/ProofOfBurn.
As the name implies: "Burn", it means that bitcoins sent into those addresses were practically burned or better "bury" since they were created without knowing the private key.

That link seems to have problem with long prefix, there are Python scripts that's available online that you can use an alternative.
I'll edit this if I found the link.

-Edit-

Here's the Python code (not mine): https://gist.github.com/CoinWhisperer/6d673f1f3d13da1611cd

[AB de Royse777]

Just for the sake of clarity, there is a private key associated with that address. The only thing is that there is a very low probability that anyone would currently have access to that private key.

In other words the private key is not known to anyone :-D

At this point I understand that the addresses I have posted are not valid at all and the network will reject them of course even if any wallet allows the tx. Never mind, it was just fun :-P

[Herbert2020]

They call those addresses "Proof of Burn"

these addresses should never be referred to as proof of burn because even though they are essentially doing the same thing, they are doing it the worst way possible since each time these addresses receive a payment that is one extra burden on each bitcoin node per output and they have to keep these garbage UTXOs in their database and load it each time forever.

whereas the correct way that is using OP_RETURN doesn't have this issue since nodes recognize these as provably unspendable and such outputs are never added to their database.

[o_e_l_e_o]

At this point I understand that the addresses I have posted are not valid at all and the network will reject them of course even if any wallet allows the tx.

A bitcoin address in Base58Check format is more than just a random string of characters. Much like how you can't have any 24 word seed phrase because part of the last word also encodes the checksum, you can't have any string of characters become an address because the last few characters encode a checksum - hence the "Check" in "Base58Check".

To convert a public key to a address, you must first take the SHA256 hash, followed by the RIPEMD160 hash. You then add a 0x00 byte to start, take the SHA256 hash twice, and append the first four bytes of the double hashed result as the checksum. You then convert the whole thing from hex in to Base58. As a result, the final 5 or 6 characters of the address are the checksum, and therefore cannot be random.

Have a look at this page for some more info: https://gobittest.appspot.com/Address

[AB de Royse777]

Have a look at this page for some more info: https://gobittest.appspot.com/Address

Finally, I think I was able to create a valid address which does not have a known private key to me :-P

Check this: 1DoNotSendBTCToThisAddressRPkuP5V
Warning: no private key, so anything goes there will be lost forever.

[o_e_l_e_o]

Finally, I think I was able to create a valid address which does not have a known private key to me :-P

Yup, that address is valid. The last 6 characters - PkuP5V - are the checksum. The R just before that is not part of the checksum, so could be changed to any character, provided you then recalculated the checksum. For example, this is also a valid address:

1DoNotSendBTCToThisAddressXMKKsPW

[nc50lc]

They call those addresses "Proof of Burn"

these addresses should never be referred to as proof of burn because even though they are essentially doing the same thing, they are doing it the worst way possible since each time these addresses receive a payment that is one extra burden on each bitcoin node per output and they have to keep these garbage UTXOs in their database and load it each time forever.

I can't agree more, the name sounds wrong to me for the famous use-case.
Probably because historically, they were used as another form of "mining", an alternative to POW / POS.
Explained better in the Wiki (source): https://en.bitcoin.it/wiki/Proof_of_burn#Introduction_and_motivation

[Abdussamad]

I came across this address 1BitcoinEaterAddressDontSendf59kue
To generate a 1BitcoinEaterAddressDontSend address using VanityGen, you will need 3.3 E+33 or 3.3 decillion years.
Please tell me how you can generate an address of this length and with what?
Here is a link to the transactions https://btc.com/1BitcoinEaterAddressDontSendf59kuE
or do I not understand something?

vanity gen tries to generate both private keys and corresponding public keys that hash to an address with the prefix you want. that's why it takes so long because it's essentially a bruteforce effort.

making an address where you don't care about the private key is relatively easy. it's just a large number with a checksum.

[bct_ail]

If I take a look in the blockchainexplorer from https://btc.com/1BitcoinEaterAddressDontSendf59kuE, I see many others strange addresses like 1111111111111111111114oLvT2  and 1CounterpartyXXXXXXXXXXXXXXXUWLpV and they are getting the same amount of bitcoin.
Adress https://btc.com/1PZLTxKhvToB1y5NpUGrRG1LM7wRhjrDjQ seems to be loved to send bitcoin tot hem and like it to send the same amount. Pretty strange.

Would like to know the total amount of bitcoin which is locked in burn adresses.

[LoyceV]

If I take a look in the blockchainexplorer from https://btc.com/1BitcoinEaterAddressDontSendf59kuE, I see many others strange addresses like 1111111111111111111114oLvT2  and 1CounterpartyXXXXXXXXXXXXXXXUWLpV and they are getting the same amount of bitcoin.
Adress https://btc.com/1PZLTxKhvToB1y5NpUGrRG1LM7wRhjrDjQ seems to be loved to send bitcoin tot hem and like it to send the same amount. Pretty strange.

Would like to know the total amount of bitcoin which is locked in burn adresses.

You can play around with List of all Bitcoin addresses with a balance:
Some of the addresses with highest funds:

Code:

1111111111111111111114oLvT2     6972783279
123AnditsGone111111111111111Ymiao1      4403101
11111111111111111111BZbvjr      1035064
1DayahDover11111111111111112JYRq2       314159
1Forever11111111111111111113RMwCB       314159
11LoveYou1111111111111111111GPc4r       314159
1BitcoinEaterAddressDontSendf59kuE      1324802316
1CounterpartyXXXXXXXXXXXXXXXUWLpVr      213091304589
1ChancecoinXXXXXXXXXXXXXXXXXZELUFD      48019562827
1MetronotesxxxxxxxxxxxxxxxxxY4qPvn      200000000
1NewbiecoinXXXXXXXXXXXXXXXXDN67UA8      131817000
1BURNFoWXXXXXXXXXXXXXXXXXXXY5LRms       36810050
1BURNTSH1RTxxxxxxxxxxxxxxxxuckhAY       10060099
1BurnPepexxxxxxxxxxxxxxxxxxxAK33R       4331378
1EricLombrozoXXXXXXXXXXXXXXXWACBVB      2500000
1LTBBURNxxxxxxxxxxxxxxxxxxxxQiaRZ       1965660
1969SandraSandicXXXXXXXXXXXXXvdEiU      1500000
1JeSuisChar1ieXXXXXXXXXXXXXXZCQPGy      1200000
1CJbitcoinxxxxxxxxxxxxxf345bTqkHtb      705010
1BURNSogXXXXXXXXXXXXXXXXXXXXW3ny2Y      434480
1CJpurseioxxxxxxxxxxxxx89877Z1rLzQ      427215
1haiLLordkekxxxxxxxxxxxxxxxtn8WwC       190870
1hyugaxxxxxxxxxxxxxxxxxxxxxtkbLXZ       114190
1See1xxxx1memo1xxxxxxxxxxxxxBuhPF       107118
1xxxxxxxxxxxxxxxxxxxxxxxxxy1kmdGr       106118
1dot1xxxxx1sv1xxxxxxxxxxxxxwYqEEt       106118
1MorveusWasHereXXXXXXXXXXXXXXnn9Zd      100000
1G1itch1sAShitXXXXXXXXXXXXXZhFj71       100000
1Tommy1SGreedyXXXXXXXXXXXXXUaCcpi       100000
1CzarpartyxxxxxxxxxxxxxxxxxxVpVnVc      100000

[pooya87]

Would like to know the total amount of bitcoin which is locked in burn adresses.

You can play around with List of all Bitcoin addresses with a balance:

this needs a dictionary search.
it requires a heavily parallelized code that goes through all the address strings and selects the first couple of characters and tries to see if it can find them in a dictionary (list of known words) then only prints it if the number of words are big enough to be considered an address without key.