pull down to refresh
I think I get it. It’s not a real burn address, not like an unspendable UTXO. It’s burn address just because it’s crazy hard to get a private key that derives that address.
Exactly there is no "burn address" built into bitcoin code, but there are addresses that are so improbable that there is no real way someone holds the private key.
There are tools that generate "vanity addresses" (along with private key) but typically it becomes impossible after the first few chars. So you can probably easily generate private key for bc111XXXXX address but generating bc111111111111111... is impossible.
It’s not impossible, it’s just that the number space is so enormous that it’s exceedingly unlikely that it will ever be found: every random private key you generate will map to one of 2160 possible P2PKH addresses.
Also see, Bitcoin Stack Exchange Is each Bitcoin address unique?
These funds will remain burnt even if CRQC make an appearance. The 000…000 was inserted in the position of the pubkey hash. The public key that hashes to 000…000 remains unknown.
You can see this by inspecting the details of an output that paid 111…14oLvT2`, e.g., on mempool.space:
They are not immune to QC attacks.
The easiest way for you to understand it is to play around with the concept. For example, go to https://www.md5hashgenerator.com/ and enter "hello" and hit "Generate" button. That should produce the hash 5d41402abc4b2a76b9719d911017c592.
Try enter a few hundred or thousand different strings. See if you can get a meaningful repeating pattern in your output hash.
The odds of any hash producing some sort of repeating pattern like 111111111111111.... is so low that you can assume that the you are being given a hash that the person doesn't know the source data to. Therefore its a burn address.