Timeline for What is the relationship between a Bitcoin Private Key / Public Key / Address?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 25, 2021 at 13:46 | comment | added | Murch♦ | Indeed, thank you for pointing that out. I've corrected my post. | |
| Nov 25, 2021 at 13:45 | history | edited | Murch♦ | CC BY-SA 4.0 |
Correct number of hash applications to go from public key to public key hash. H/T hft
|
| Nov 24, 2021 at 22:13 | comment | added | hft | you are welcome. One other nitpick: it is just SHA256, not SHA256d that is applied prior to the RIPEMD-160 hash when forming the unchecksummed address hash. | |
| Nov 24, 2021 at 21:39 | comment | added | Murch♦ | Thank you for the note, @hft, I hope this is better. | |
| Nov 24, 2021 at 21:39 | history | edited | Murch♦ | CC BY-SA 4.0 |
Correct the range of valid private keys to be delimited by the order of the generator
|
| Nov 24, 2021 at 20:56 | comment | added | hft | See section 2.4.1 here: secg.org/sec2-v2.pdf | |
| Nov 24, 2021 at 20:55 | comment | added | hft | I think the range of the private key is actually limited to the order "n" of the generator, which is close to 2**256, but not equal to it. The order is 115792089237316195423570985008687907852837564279074904382605163141518161494337 | |
| Dec 29, 2020 at 13:55 | history | edited | Murch♦ | CC BY-SA 4.0 |
deleted 4 characters in body
|
| Dec 29, 2020 at 13:50 | history | answered | Murch♦ | CC BY-SA 4.0 |