Script: 410000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000ac
Total Lost: 0.0001 BTC
Transactions: 1
How did this script burn BTC?
The Zero Public Key
All valid Bitcoin Public keys begin with 0x02 or 0x03 for compressed keys, or 0x04 for uncompressed keys. These prefixes are followed by 32 to 33 bytes of data that represent the x and y coordinates of a point on the secp256k1 elliptic curve.
However, it is possible to use an invalid public key in a Bitcoin Script, such as 0x00 followed by 64 bytes of zeros. The resulting script, when expressed as a Pay-to-Public-Key (P2PK) output, can be used to receive BTC but never spend it as it is impossible to produce a valid signature that will match the zero public key.
ECDSA Incompatibility
The Bitcoin Protocol relies on the secp256k1 elliptic curve for its cryptographic operations. This curve belongs to the larger family of elliptic curves.
Bitcoin also employs a number of hashing operations such as SHA-256 and RIPEMD-160. These operations are used in various places across the protocol, including in the creation of addresses and their corresponding Bitcoin Scripts.
In some cases, it is possible to select values that are invalid for the secp256k1 curve as inputs to the hashing operations. This can lead to unexpected results, such as the creation of addresses that can be used to receive BTC, but are never able to spend it.
View revision history| Transaction ID | Block Height | Amount |
|---|---|---|
| 347939105c1c90282698ef83d59d525aa5022002318949cb6c9dde271535432f | 244017 |
0.0001 BTC
now
$6.09
|