-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
notes/scriptgroup: annotate burn_address group
- Loading branch information
1 parent
63b87ac
commit 00b103c
Showing
1 changed file
with
9 additions
and
0 deletions.
There are no files selected for viewing
9 changes: 9 additions & 0 deletions
9
...scriptgroup/d81555f1a6ae904908f9f74f3177cea9a40bb2ac2b7363bfce3f48043784fcf4.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,9 @@ | ||
### Burn Address | ||
|
||
Bitcoin addresses are generated by base58 or bech32 encoding the hash of a public key or script, along with a version and checksum. | ||
|
||
As the encoding is directly performed on this hash value, it is possible to generate a valid address for which the pre-image public key or script is unknown. This is known as a burn address. | ||
|
||
This is commonly done to create a visually distinct address, and to demonstrate some level of "nothing up my sleeve" transparency. The hash values are picked to be values that are improbably to have been generated by chance (due to the immense computational power required to find a pre-image that hashes to a specific value). | ||
|
||
While some burn addresses were used in Proof-of-Burn schemes, the majority of burn addresses are simply vanity addresses used to simply burn coins or encode a message into the blockchain. |