arno/bitcoinbook
1
0
Fork 0
mirror of https://github.com/bitcoinbook/bitcoinbook synced 2025-02-17 01:52:09 +00:00
Code Issues Releases Wiki Activity

Edited appdx-bx.asciidoc with Atlas code editor

Browse Source
This commit is contained in:
judymcconville@roadrunner.com 2017-05-02 14:00:26 -07:00
parent c90548c2e6
commit 386b3a057a
1 changed files with 181 additions and 181 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

362
appdx-bx.asciidoc
View File

@ -1,181 +1,181 @@
[[appdx_bx]] [[appdx_bx]]
[appendix] [appendix]
== Bitcoin Explorer (bx) Commands == Bitcoin Explorer (bx) Commands((("Bitcoin Explorer (bx) commands", id="BX19")))
---- ----
Usage: bx COMMAND [--help] Usage: bx COMMAND [--help]
Info: The bx commands are: Info: The bx commands are:
address-decode address-decode
address-embed address-embed
address-encode address-encode
address-validate address-validate
base16-decode base16-decode
base16-encode base16-encode
base58-decode base58-decode
base58-encode base58-encode
base58check-decode base58check-decode
base58check-encode base58check-encode
base64-decode base64-decode
base64-encode base64-encode
bitcoin160 bitcoin160
bitcoin256 bitcoin256
btc-to-satoshi btc-to-satoshi
ec-add ec-add
ec-add-secrets ec-add-secrets
ec-multiply ec-multiply
ec-multiply-secrets ec-multiply-secrets
ec-new ec-new
ec-to-address ec-to-address
ec-to-public ec-to-public
ec-to-wif ec-to-wif
fetch-balance fetch-balance
fetch-header fetch-header
fetch-height fetch-height
fetch-history fetch-history
fetch-stealth fetch-stealth
fetch-tx fetch-tx
fetch-tx-index fetch-tx-index
hd-new hd-new
hd-private hd-private
hd-public hd-public
hd-to-address hd-to-address
hd-to-ec hd-to-ec
hd-to-public hd-to-public
hd-to-wif hd-to-wif
help help
input-set input-set
input-sign input-sign
input-validate input-validate
message-sign message-sign
message-validate message-validate
mnemonic-decode mnemonic-decode
mnemonic-encode mnemonic-encode
ripemd160 ripemd160
satoshi-to-btc satoshi-to-btc
script-decode script-decode
script-encode script-encode
script-to-address script-to-address
seed seed
send-tx send-tx
send-tx-node send-tx-node
send-tx-p2p send-tx-p2p
settings settings
sha160 sha160
sha256 sha256
sha512 sha512
stealth-decode stealth-decode
stealth-encode stealth-encode
stealth-public stealth-public
stealth-secret stealth-secret
stealth-shared stealth-shared
tx-decode tx-decode
tx-encode tx-encode
uri-decode uri-decode
uri-encode uri-encode
validate-tx validate-tx
watch-address watch-address
wif-to-ec wif-to-ec
wif-to-public wif-to-public
wrap-decode wrap-decode
wrap-encode wrap-encode
---- ----
For more information, see the https://github.com/libbitcoin/libbitcoin-explorer[Bitcoin Explorer homepage] and https://github.com/libbitcoin/libbitcoin-explorer/wiki[Bitcoin Explorer user documentation]. For more information, see the https://github.com/libbitcoin/libbitcoin-explorer[Bitcoin Explorer homepage] and https://github.com/libbitcoin/libbitcoin-explorer/wiki[Bitcoin Explorer user documentation].
=== Examples of bx Command Use === Examples of bx Command Use
Let's look at some examples of using Bitcoin Explorer commands to experiment with keys and addresses. Let's look at some examples of using Bitcoin Explorer commands to experiment with keys and addresses.
Generate a random "seed" value using the +seed+ command, which uses the operating system's random number generator. Pass the seed to the +ec-new+ command to generate a new private key. We save the standard output into the file _private_key_: Generate a random "seed" value using the +seed+ command, which uses the operating system's random number generator. Pass the seed to the +ec-new+ command to generate a new private key. We save the standard output into the file _private_key_:
---- ----
$ bx seed | bx ec-new > private_key $ bx seed | bx ec-new > private_key
$ cat private_key $ cat private_key
73096ed11ab9f1db6135857958ece7d73ea7c30862145bcc4bbc7649075de474 73096ed11ab9f1db6135857958ece7d73ea7c30862145bcc4bbc7649075de474
---- ----
Now, generate the public key from that private key using the +ec-to-public+ command. We pass the _private_key_ file into the standard input and save the standard output of the command into a new file _public_key_: Now, generate the public key from that private key using the +ec-to-public+ command. We pass the _private_key_ file into the standard input and save the standard output of the command into a new file _public_key_:
---- ----
$ bx ec-to-public < private_key > public_key $ bx ec-to-public < private_key > public_key
$ cat public_key $ cat public_key
02fca46a6006a62dfdd2dbb2149359d0d97a04f430f12a7626dd409256c12be500 02fca46a6006a62dfdd2dbb2149359d0d97a04f430f12a7626dd409256c12be500
---- ----
We can reformat the +public_key+ as an address using the +ec-to-address+ command. We pass the _public_key_ into standard input: We can reformat the +public_key+ as an address using the +ec-to-address+ command. We pass the _public_key_ into standard input:
---- ----
$ bx ec-to-address < public_key $ bx ec-to-address < public_key
17re1S4Q8ZHyCP8Kw7xQad1Lr6XUzWUnkG 17re1S4Q8ZHyCP8Kw7xQad1Lr6XUzWUnkG
---- ----
Keys generated in this manner produce a type-0 nondeterministic wallet. That means that each key is generated from an independent seed. Bitcoin Explorer commands can also generate keys deterministically, in accordance with BIP-32. In this case, a "master" key is created from a seed and then extended deterministically to produce a tree of subkeys, resulting in a type-2 deterministic wallet. Keys generated in this manner produce a type-0 nondeterministic wallet. That means that each key is generated from an independent seed. Bitcoin Explorer commands can also generate keys deterministically, in accordance with BIP-32. In this case, a "master" key is created from a seed and then extended deterministically to produce a tree of subkeys, resulting in a type-2 deterministic wallet.
First, we use the +seed+ and +hd-new+ commands to generate a master key that will be used as the basis to derive a hierarchy of keys: First, we use the +seed+ and +hd-new+ commands to generate a master key that will be used as the basis to derive a hierarchy of keys:
---- ----
$ bx seed > seed $ bx seed > seed
$ cat seed $ cat seed
eb68ee9f3df6bd4441a9feadec179ff1 eb68ee9f3df6bd4441a9feadec179ff1
$ bx hd-new < seed > master $ bx hd-new < seed > master
$ cat master $ cat master
xprv9s21ZrQH143K2BEhMYpNQoUvAgiEjArAVaZaCTgsaGe6LsAnwubeiTcDzd23mAoyizm9cApe51gNfLMkBqkYoWWMCRwzfuJk8RwF1SVEpAQ xprv9s21ZrQH143K2BEhMYpNQoUvAgiEjArAVaZaCTgsaGe6LsAnwubeiTcDzd23mAoyizm9cApe51gNfLMkBqkYoWWMCRwzfuJk8RwF1SVEpAQ
---- ----
We now use the +hd-private+ command to generate a hardened "account" key and a sequence of two private keys within the account: We now use the +hd-private+ command to generate a hardened "account" key and a sequence of two private keys within the account:
---- ----
$ bx hd-private --hard < master > account $ bx hd-private --hard < master > account
$ cat account $ cat account
xprv9vkDLt81dTKjwHB8fsVB5QK8cGnzveChzSrtCfvu3aMWvQaThp59ueufuyQ8Qi3qpjk4aKsbmbfxwcgS8PYbgoR2NWHeLyvg4DhoEE68A1n xprv9vkDLt81dTKjwHB8fsVB5QK8cGnzveChzSrtCfvu3aMWvQaThp59ueufuyQ8Qi3qpjk4aKsbmbfxwcgS8PYbgoR2NWHeLyvg4DhoEE68A1n
$ bx hd-private --index 0 < account $ bx hd-private --index 0 < account
xprv9xHfb6w1vX9xgZyPNXVgAhPxSsEkeRcPHEUV5iJcVEsuUEACvR3NRY3fpGhcnBiDbvG4LgndirDsia1e9F3DWPkX7Tp1V1u97HKG1FJwUpU xprv9xHfb6w1vX9xgZyPNXVgAhPxSsEkeRcPHEUV5iJcVEsuUEACvR3NRY3fpGhcnBiDbvG4LgndirDsia1e9F3DWPkX7Tp1V1u97HKG1FJwUpU
$ bx hd-private --index 1 < account $ bx hd-private --index 1 < account
xprv9xHfb6w1vX9xjc8XbN4GN86jzNAZ6xHEqYxzbLB4fzHFd6VqCLPGRZFsdjsuMVERadbgDbziCRJru9n6tzEWrASVpEdrZrFidt1RDfn4yA3 xprv9xHfb6w1vX9xjc8XbN4GN86jzNAZ6xHEqYxzbLB4fzHFd6VqCLPGRZFsdjsuMVERadbgDbziCRJru9n6tzEWrASVpEdrZrFidt1RDfn4yA3
---- ----
Next we use the +hd-public+ command to generate the corresponding sequence of two public keys: Next we use the +hd-public+ command to generate the corresponding sequence of two public keys:
---- ----
$ bx hd-public --index 0 < account $ bx hd-public --index 0 < account
xpub6BH1zcTuktiFu43rUZ2gXqLgzu5F3tLEeTQ5t6iE3aQtM2VMTxMcyLN9fYHiGhGpQe9QQYmqL2eYPFJ3vezHz5wzaSW4FiGrseNDR4LKqTy xpub6BH1zcTuktiFu43rUZ2gXqLgzu5F3tLEeTQ5t6iE3aQtM2VMTxMcyLN9fYHiGhGpQe9QQYmqL2eYPFJ3vezHz5wzaSW4FiGrseNDR4LKqTy
$ bx hd-public --index 1 < account $ bx hd-public --index 1 < account
xpub6BH1zcTuktiFx6CzhPbGjG3UYQ13WR16CmtbPiagEKpEVtpyjshWyMaMV1cn7nUPUkgQHPVXJVqsrA8xWbGQDhohEcDFTEYMvYzwRD7Juf8 xpub6BH1zcTuktiFx6CzhPbGjG3UYQ13WR16CmtbPiagEKpEVtpyjshWyMaMV1cn7nUPUkgQHPVXJVqsrA8xWbGQDhohEcDFTEYMvYzwRD7Juf8
---- ----
The public keys can also be derived from their corresponding private keys using the +hd-to-public+ command: The public keys can also be derived from their corresponding private keys using the +hd-to-public+ command:
---- ----
$ bx hd-private --index 0 < account | bx hd-to-public $ bx hd-private --index 0 < account | bx hd-to-public
xpub6BH1zcTuktiFu43rUZ2gXqLgzu5F3tLEeTQ5t6iE3aQtM2VMTxMcyLN9fYHiGhGpQe9QQYmqL2eYPFJ3vezHz5wzaSW4FiGrseNDR4LKqTy xpub6BH1zcTuktiFu43rUZ2gXqLgzu5F3tLEeTQ5t6iE3aQtM2VMTxMcyLN9fYHiGhGpQe9QQYmqL2eYPFJ3vezHz5wzaSW4FiGrseNDR4LKqTy
$ bx hd-private --index 1 < account | bx hd-to-public $ bx hd-private --index 1 < account | bx hd-to-public
xpub6BH1zcTuktiFx6CzhPbGjG3UYQ13WR16CmtbPiagEKpEVtpyjshWyMaMV1cn7nUPUkgQHPVXJVqsrA8xWbGQDhohEcDFTEYMvYzwRD7Juf8 xpub6BH1zcTuktiFx6CzhPbGjG3UYQ13WR16CmtbPiagEKpEVtpyjshWyMaMV1cn7nUPUkgQHPVXJVqsrA8xWbGQDhohEcDFTEYMvYzwRD7Juf8
---- ----
We can generate a practically limitless number of keys in a deterministic chain, all derived from a single seed. This technique is used in many wallet applications to generate keys that can be backed up and restored with a single seed value. This is easier than having to back up the wallet with all its randomly generated keys every time a new key is created. We can generate a practically limitless number of keys in a deterministic chain, all derived from a single seed. This technique is used in many wallet applications to generate keys that can be backed up and restored with a single seed value. This is easier than having to back up the wallet with all its randomly generated keys every time a new key is created.
The seed can be encoded using the +mnemonic-encode+ command: The seed can be encoded using the +mnemonic-encode+ command:
---- ----
$ bx hd-mnemonic < seed > words $ bx hd-mnemonic < seed > words
adore repeat vision worst especially veil inch woman cast recall dwell appreciate adore repeat vision worst especially veil inch woman cast recall dwell appreciate
---- ----
The seed can then be decoded using the +mnemonic-decode+ command: The seed can then be decoded using the +mnemonic-decode+ command:
---- ----
$ bx mnemonic-decode < words $ bx mnemonic-decode < words
eb68ee9f3df6bd4441a9feadec179ff1 eb68ee9f3df6bd4441a9feadec179ff1
---- ----
Mnemonic encoding can make the seed easier to record and even remember. Mnemonic encoding can make the seed easier to record and even remember.((("", startref="BX19")))