arno/bitcoinbook
1
0
Fork 0
mirror of https://github.com/bitcoinbook/bitcoinbook synced 2025-01-26 15:41:34 +00:00
Code Issues Releases Wiki Activity

CH04::privkeys: remove address function from here

Browse Source 
We'll describe the commitment in the P2PKH section and base58check in
its section.
This commit is contained in:
David A. Harding 2023-02-07 14:40:42 -10:00
parent 1b4e3b7b2b
commit 03259f9e60
1 changed files with 3 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
ch04.asciidoc
View File

@ -71,17 +71,7 @@ pairs, each consisting of a private key and a public key. The private
key (k) is a number, usually derived from a number picked at random. key (k) is a number, usually derived from a number picked at random.
From the private key, we From the private key, we
use elliptic curve multiplication, a one-way cryptographic function, to use elliptic curve multiplication, a one-way cryptographic function, to
generate a public key (K). From the public key (K), we use a one-way generate a public key (K).
cryptographic hash function to generate a Bitcoin address (A). In this
section, we will start with generating the private key, look at the
elliptic curve math that is used to turn that into a public key, and
finally, generate a Bitcoin address from the public key. The
relationship between private key, public key, and Bitcoin address is
shown in <<k_to_K_to_A>>.
[[k_to_K_to_A]]
.Private key, public key, and Bitcoin address
image::images/mbc2_0401.png["privk_to_pubK_to_addressA"]
.Why Use Asymmetric Cryptography (Public/Private Keys)? .Why Use Asymmetric Cryptography (Public/Private Keys)?
**** ****
@ -352,9 +342,8 @@ resulting public key, a point on the curve. Because the generator point
is always the same for all bitcoin users, a private key _k_ multiplied is always the same for all bitcoin users, a private key _k_ multiplied
with _G_ will always result in the same public key _K_. The relationship with _G_ will always result in the same public key _K_. The relationship
between _k_ and _K_ is fixed, but can only be calculated in one between _k_ and _K_ is fixed, but can only be calculated in one
direction, from _k_ to _K_. That's why a Bitcoin address (derived from direction, from _k_ to _K_. That's why a Bitcoin public key can be
_K_) can be shared with anyone and does not reveal the user's private shared with anyone and does not reveal the user's private key (_k_).
key (_k_).
[TIP] [TIP]
==== ====