|
|
|
@ -752,9 +752,9 @@ version prefixes and the resulting base58 characters are shown in
|
|
|
|
|
</table>
|
|
|
|
|
++++
|
|
|
|
|
|
|
|
|
|
Putting together public keys, hash-based commitments, and base58check
|
|
|
|
|
encoding, we can see the illustration of the conversion of a public key
|
|
|
|
|
into a Bitcoin address((("public key cryptography", "base58check encoding", startref="pub-key-base58")))((("base58check encoding", startref="base58-ch4")))((("encoding", "base58check", startref="encode-base58")))((("version prefixes", startref="version-prefix"))) in <<pubkey_to_address>>.
|
|
|
|
|
Combining public keys, hash-based commitments, and base58check
|
|
|
|
|
encoding, <<pubkey_to_address>> illustrates the conversion of a public key
|
|
|
|
|
into a Bitcoin ((("public key cryptography", "base58check encoding", startref="pub-key-base58")))((("base58check encoding", startref="base58-ch4")))((("encoding", "base58check", startref="encode-base58")))((("version prefixes", startref="version-prefix")))address.
|
|
|
|
|
|
|
|
|
|
[[pubkey_to_address]]
|
|
|
|
|
.Public key to Bitcoin address: conversion of a public key into a Bitcoin address
|
|
|
|
|