mirror of
https://github.com/seigler/dash-docs
synced 2025-07-27 01:36:13 +00:00
Revert "Merge pull #793: Dev Docs: New Glossary & JS Search Box"
This reverts commite3dcf0ce1f, reversing changes made toc71e9fdf2d. Once again we had a broken new plugin that Travis CI and local building didn't catch.
This commit is contained in:
David A. Harding
parent
e3dcf0ce1f
commit
961d6c988f
126 changed files with 470 additions and 3827 deletions
17
README.md
17
README.md
|
|
@ -220,7 +220,7 @@ environment variables:
|
|||
|
||||
## Developer Documentation
|
||||
|
||||
Most parts of the documentation can be found in the [_includes](https://github.com/bitcoin/bitcoin.org/tree/master/_includes)
|
||||
Each part of the documentation can be found in the [_includes](https://github.com/bitcoin/bitcoin.org/tree/master/_includes)
|
||||
directory. Updates, fixes and improvements are welcome and can submitted using [pull requests](#working-with-github) on GitHub.
|
||||
|
||||
**Mailing List**: General discussions can take place on the
|
||||
|
|
@ -238,21 +238,6 @@ can also be submitted to this guide to keep it up to date.
|
|||
_includes/references.md. Terms which should automatically link to these
|
||||
references are defined in _autocrossref.yaml .
|
||||
|
||||
### New Glossary Entries
|
||||
|
||||
Add new English glossary entries in the `_data/glossary/en/` directory.
|
||||
Copy a previous glossary entry to get the correct YAML variables
|
||||
(suggest using block.yaml as a template).
|
||||
|
||||
Non-English glossary entries are not currently supported. You'll have
|
||||
to update the glossary.rb plugin and templates to support them.
|
||||
|
||||
### New Developer Search terms
|
||||
|
||||
You can add new search terms or categories directly to the `devsearches`
|
||||
array in `_config.yaml`. Comments in that file should provide full
|
||||
documentation.
|
||||
|
||||
## Translation
|
||||
|
||||
### How To Translate
|
||||
|
|
|
|||
|
|
@ -8,11 +8,17 @@
|
|||
#
|
||||
## To prevent a ref for term, use: "term: DO NOT AUTOCROSSREF"
|
||||
|
||||
51 percent attack:
|
||||
'`addr` message': addr message
|
||||
'`addr` messages': addr message
|
||||
address:
|
||||
addresses: address
|
||||
'`alert` message': alert message
|
||||
'`alert` messages': alert message
|
||||
'`amount`': pp amount
|
||||
base-58: base58check
|
||||
base58: base58check
|
||||
base58check:
|
||||
## bitcoin -- Recommend against bitcoin (singular) because of confusion between protocol, software, denomination
|
||||
bitcoins:
|
||||
bitcoin QR code: URI QR code
|
||||
|
|
@ -20,17 +26,75 @@ bitcoin QR codes: URI QR code
|
|||
'`bitcoin:` URI': bitcoin uri
|
||||
'`bitcoin:` URIs': bitcoin uri
|
||||
bitcoinj:
|
||||
block:
|
||||
block chain:
|
||||
block-chain: block chain
|
||||
block header:
|
||||
block headers: block header
|
||||
block height:
|
||||
'`block` message': block message
|
||||
'`block` messages': block message
|
||||
block reward:
|
||||
block time:
|
||||
block version:
|
||||
blocks: block
|
||||
blocks-first: blocks-first sync
|
||||
blocks-first sync:
|
||||
blocks-first IBD: blocks-first sync
|
||||
bloom filter:
|
||||
broadcast:
|
||||
broadcasts: broadcast
|
||||
broadcasting:
|
||||
certificate chain:
|
||||
chain code:
|
||||
change address:
|
||||
change addresses: change address
|
||||
change output:
|
||||
change outputs: change output
|
||||
child key:
|
||||
child keys: child key
|
||||
child private and public keys: child key
|
||||
child public key:
|
||||
child public keys: child public key
|
||||
coinbase: coinbase transaction
|
||||
coinbase block height:
|
||||
coinbase transaction:
|
||||
coinbase transactions: coinbase transaction
|
||||
coinbase field:
|
||||
compactsize uint: compactsize unsigned integer
|
||||
compactsize unsigned integer:
|
||||
compactsize unsigned integers: compactsize unsigned integer
|
||||
compressed public key:
|
||||
compressed public keys: compressed public key
|
||||
confirm:
|
||||
confirmed:
|
||||
confirmation:
|
||||
confirmations:
|
||||
confirmed transactions:
|
||||
consensus:
|
||||
consensus rules:
|
||||
data-pushing op code:
|
||||
data-pushing op codes: data-pushing op code
|
||||
denomination:
|
||||
denominations: denomination
|
||||
DER:
|
||||
DER format: der
|
||||
DER-formatted: der
|
||||
difficulty:
|
||||
dns seed:
|
||||
dns seeds: dns seed
|
||||
double spend:
|
||||
double-spend: double spend
|
||||
double spending: double spend
|
||||
double-spent: double spend
|
||||
ECDSA:
|
||||
epoch time: unix epoch time
|
||||
escrow contract:
|
||||
'`expires`': pp expires
|
||||
extended key:
|
||||
extended keys: extended key
|
||||
extended private key:
|
||||
extended public key:
|
||||
fiat:
|
||||
'`filteradd` message': filteradd message
|
||||
'`filteradd` messages': filteradd message
|
||||
|
|
@ -38,6 +102,9 @@ fiat:
|
|||
'`filterclear` messages': filterclear message
|
||||
'`filterload` message': filterload message
|
||||
'`filterload` messages': filterload message
|
||||
fork:
|
||||
forks: fork
|
||||
genesis block:
|
||||
'`getblocks` message': getblocks message
|
||||
'`getblocks` messages': getblocks message
|
||||
'`getdata` message': getdata message
|
||||
|
|
@ -46,10 +113,25 @@ fiat:
|
|||
'`getheaders` messages': getheaders message
|
||||
'`getaddr` message': getaddr message
|
||||
'`getaddr` messages': getaddr message
|
||||
hard fork:
|
||||
hard forks: hard fork
|
||||
hardened extended private key:
|
||||
HD protocol:
|
||||
header chain:
|
||||
headers-first: headers-first sync
|
||||
headers-first sync:
|
||||
headers-first IBD: headers-first sync
|
||||
'`headers` message': headers message
|
||||
'`headers` messages': headers message
|
||||
high-priority transaction: high-priority transactions
|
||||
high-priority transactions:
|
||||
IBD: initial block download
|
||||
initial block download:
|
||||
inputs: input
|
||||
input:
|
||||
intermediate certificate:
|
||||
intermediate certificates: intermediate certificate
|
||||
internal byte order:
|
||||
'`inv` message': inv message
|
||||
'`inv` messages': inv message
|
||||
IP address: DO NOT AUTOCROSSREF
|
||||
|
|
@ -58,44 +140,82 @@ IPv4 address: DO NOT AUTOCROSSREF
|
|||
IPv4 addresses: DO NOT AUTOCROSSREF
|
||||
IPv6 address: DO NOT AUTOCROSSREF
|
||||
IPv6 addresses: DO NOT AUTOCROSSREF
|
||||
inventories: inventory
|
||||
inventory:
|
||||
key index:
|
||||
key pair:
|
||||
'`label`': label
|
||||
leaf certificate:
|
||||
locktime:
|
||||
long-term fork:
|
||||
mainnet:
|
||||
man in the middle: man-in-the-middle
|
||||
man-in-the-middle:
|
||||
master chain code:
|
||||
master private key:
|
||||
'`memo`': pp memo
|
||||
'`mempool` message': mempool message
|
||||
'`mempool` messages': mempool message
|
||||
'`message`': message
|
||||
message header:
|
||||
message headers: message header
|
||||
message payload:
|
||||
'`merchant_data`': pp merchant data
|
||||
merkle block:
|
||||
merkle blocks: merkle block
|
||||
'`merkleblock` message': merkleblock message
|
||||
'`merkleblock` messages': merkleblock message
|
||||
merkle root:
|
||||
merkle tree:
|
||||
merge:
|
||||
Merge avoidance:
|
||||
micropayment channel:
|
||||
micropayment channels: micropayment channel
|
||||
mine:
|
||||
miner:
|
||||
miners: miner
|
||||
minimum fee:
|
||||
mining: mine
|
||||
millibitcoin: millibitcoins
|
||||
millibitcoins:
|
||||
'`MSG_BLOCK`': msg_block
|
||||
'`MSG_FILTERED_BLOCK`': msg_filtered_block
|
||||
'`MSG_TX`': msg_tx
|
||||
multisig:
|
||||
multisig p2sh: p2sh multisig
|
||||
nbits:
|
||||
network:
|
||||
'`notfound` message': notfound message
|
||||
'`notfound` messages': notfound message
|
||||
'number (bitcoins)': proper money handling
|
||||
null data:
|
||||
'`op_checkmultisig`': op_checkmultisig
|
||||
'`op_checksig`': op_checksig
|
||||
op code:
|
||||
op codes: op code
|
||||
'`op_dup`': op_dup
|
||||
'`op_equal`': op_equal
|
||||
'`op_equalverify`': op_equalverify
|
||||
'`op_hash160`': op_hash160
|
||||
'`op_return`': op_return
|
||||
'`op_verify`': op_verify
|
||||
orphan block:
|
||||
orphan blocks: orphan block
|
||||
outpoint:
|
||||
outpoints: outpoint
|
||||
outputs: output
|
||||
output:
|
||||
output index:
|
||||
p2pkh:
|
||||
p2sh:
|
||||
p2sh multisig:
|
||||
parent chain code:
|
||||
parent key:
|
||||
parent private key:
|
||||
parent private and public keys: parent key
|
||||
parent public key:
|
||||
payment protocol:
|
||||
"payment protocol's": payment protocol
|
||||
PaymentDetails:
|
||||
PaymentRequest:
|
||||
PaymentRequests: paymentrequest
|
||||
|
|
@ -111,6 +231,10 @@ pki:
|
|||
'`pong` message': pong message
|
||||
'`pong` messages': pong message
|
||||
previous block header hash:
|
||||
private key:
|
||||
private keys: private key
|
||||
proof of work:
|
||||
proof-of-work: proof of work
|
||||
protocol buffer: protobuf
|
||||
protocol buffers: protobuf
|
||||
protocol version 106: section protocol versions
|
||||
|
|
@ -123,26 +247,84 @@ protocol version 60001: section protocol versions
|
|||
protocol version 60002: section protocol versions
|
||||
protocol version 70001: section protocol versions
|
||||
protocol version 70002: section protocol versions
|
||||
pubkey: public key
|
||||
pubkey hash:
|
||||
pubkey hashes: pubkey hash
|
||||
pubkey script:
|
||||
pubkey scripts: pubkey script
|
||||
pubkeys: public key
|
||||
public key:
|
||||
public keys: public key
|
||||
public key infrastructure: pki
|
||||
'`r`': r
|
||||
raw format:
|
||||
raw transaction: raw format
|
||||
raw transactions: raw format
|
||||
raw transaction format: raw format
|
||||
rawtransaction format: raw format
|
||||
receipt:
|
||||
recurrent rebilling:
|
||||
redeem script:
|
||||
refund:
|
||||
refunds: refund
|
||||
regression test mode:
|
||||
regtest: regression test mode
|
||||
'`reject` message': reject message
|
||||
'`reject` messages': reject message
|
||||
root certificate:
|
||||
root seed:
|
||||
RPC:
|
||||
RPCs: rpc
|
||||
RPC byte order:
|
||||
satoshi:
|
||||
satoshis: satoshi
|
||||
'`script`': pp script
|
||||
script hash:
|
||||
secp256k1:
|
||||
sequence number:
|
||||
sequence numbers: sequence number
|
||||
serialized block:
|
||||
serialized blocks: serialized block
|
||||
serialized transaction: raw format
|
||||
serialized transactions: raw format
|
||||
SIGHASH: signature hash
|
||||
'`SIGHASH_ANYONECANPAY`': shacp
|
||||
'`SIGHASH_ALL`': sighash_all
|
||||
'`SIGHASH_ALL|SIGHASH_ANYONECANPAY`': sha_shacp
|
||||
'`SIGHASH_NONE`': sighash_none
|
||||
'`SIGHASH_NONE|SIGHASH_ANYONECANPAY`': shn_shacp
|
||||
'`SIGHASH_SINGLE|SIGHASH_ANYONECANPAY`': shs_shacp
|
||||
signature:
|
||||
signature hash:
|
||||
signature script:
|
||||
signature scripts: signature script
|
||||
signatures: signature
|
||||
soft fork:
|
||||
soft forks: soft fork
|
||||
SPV:
|
||||
stack:
|
||||
stale block:
|
||||
stale blocks: stale block
|
||||
standard block relay:
|
||||
standard script:
|
||||
standard scripts: standard script
|
||||
standard transaction: standard script
|
||||
standard transactions: standard script
|
||||
start string:
|
||||
target:
|
||||
testnet:
|
||||
#transaction -- Recommend we don't autocrossref this; it occurs too often
|
||||
transaction fee:
|
||||
transaction fees: transaction fee
|
||||
transaction malleability:
|
||||
transaction object format:
|
||||
transaction version number:
|
||||
'`tx` message': tx message
|
||||
'`tx` messages': tx message
|
||||
txid:
|
||||
txids: txid
|
||||
unconfirmed:
|
||||
unconfirmed transactions:
|
||||
unencrypted wallet:
|
||||
unix epoch time:
|
||||
unix time: unix epoch time
|
||||
|
|
@ -150,13 +332,21 @@ unique address: unique addresses
|
|||
unique addresses:
|
||||
unlocked wallet:
|
||||
unsolicited block push:
|
||||
utxo:
|
||||
utxos: utxo
|
||||
'`verack` message': verack message
|
||||
'`verack` messages': verack message
|
||||
verified payments:
|
||||
version 2 blocks: v2 block
|
||||
'`version` message': version message
|
||||
'`version` messages': version message
|
||||
watch-only:
|
||||
watch-only address: watch-only
|
||||
watch-only addresses: watch-only
|
||||
waching-only: watch-only
|
||||
wallet:
|
||||
wallets: wallet
|
||||
wallet import format:
|
||||
wallet support:
|
||||
wallet support disabled: wallet support
|
||||
wallet support enabled: wallet support
|
||||
|
|
|
|||
279
_config.yml
279
_config.yml
|
|
@ -200,282 +200,3 @@ kramdown:
|
|||
coderay_tab_width: 4
|
||||
coderay_bold_every: 10
|
||||
coderay_css: style
|
||||
|
||||
|
||||
## Items in devsearches will appear in the search box in the order they
|
||||
## are listed below. For the top-level ("Glossary", "RPCs", etc...) this
|
||||
## is arbitrary based on whatever we think is most important. For the
|
||||
## second-level, this should be alphabetical order or another order that
|
||||
## will make intuitive sense to the user.
|
||||
devsearches:
|
||||
|
||||
## Initialize the glossary array here so it appears first in the
|
||||
## search box. _plugins/glossary.rb will provide alphabetical ordering
|
||||
"Glossary":
|
||||
|
||||
## RPCs currently documented on Bitcoin.org. CamelCase names (with
|
||||
## leading capital) for easier quick scanning
|
||||
"RPCs":
|
||||
- 'AddMultiSigAddress': "/en/developer-reference#addmultisigaddress"
|
||||
- 'AddNode': "/en/developer-reference#addnode"
|
||||
- 'BackupWallet': "/en/developer-reference#backupwallet"
|
||||
- 'CreateMultisig': "/en/developer-reference#createmultisig"
|
||||
- 'CreateRawTransaction': "/en/developer-reference#createrawtransaction"
|
||||
- 'DecodeRawTransaction': "/en/developer-reference#decoderawtransaction"
|
||||
- 'DecodeScript': "/en/developer-reference#decodescript"
|
||||
- 'DumpPrivKey': "/en/developer-reference#dumpprivkey"
|
||||
- 'DumpWallet': "/en/developer-reference#dumpwallet"
|
||||
- 'EncryptWallet': "/en/developer-reference#encryptwallet"
|
||||
- 'EstimateFee': "/en/developer-reference#estimatefee"
|
||||
- 'EstimatePriority': "/en/developer-reference#estimatepriority"
|
||||
- 'GetAccount': "/en/developer-reference#getaccount"
|
||||
- 'GetAccountAddress': "/en/developer-reference#getaccountaddress"
|
||||
- 'GetAddedNodeInfo': "/en/developer-reference#getaddednodeinfo"
|
||||
- 'GetAddressesByAccount': "/en/developer-reference#getaddressesbyaccount"
|
||||
- 'GetBalance': "/en/developer-reference#getbalance"
|
||||
- 'GetBestBlockHash': "/en/developer-reference#getbestblockhash"
|
||||
- 'GetBlock': "/en/developer-reference#getblock"
|
||||
- 'GetBlockChainInfo': "/en/developer-reference#getblockchaininfo"
|
||||
- 'GetBlockCount': "/en/developer-reference#getblockcount"
|
||||
- 'GetBlockHash': "/en/developer-reference#getblockhash"
|
||||
- 'GetBlockTemplate': "/en/developer-reference#getblocktemplate"
|
||||
- 'GetChainTips': "/en/developer-reference#getchaintips"
|
||||
- 'GetConnectionCount': "/en/developer-reference#getconnectioncount"
|
||||
- 'GetDifficulty': "/en/developer-reference#getdifficulty"
|
||||
- 'GetGenerate': "/en/developer-reference#getgenerate"
|
||||
- 'GetHashesPerSec': "/en/developer-reference#gethashespersec"
|
||||
- 'GetInfo': "/en/developer-reference#getinfo"
|
||||
- 'GetMempoolInfo': "/en/developer-reference#getmempoolinfo"
|
||||
- 'GetMiningInfo': "/en/developer-reference#getmininginfo"
|
||||
- 'GetNetTotals': "/en/developer-reference#getnettotals"
|
||||
- 'GetNetworkHashPS': "/en/developer-reference#getnetworkhashps"
|
||||
- 'GetNetworkInfo': "/en/developer-reference#getnetworkinfo"
|
||||
- 'GetNewAddress': "/en/developer-reference#getnewaddress"
|
||||
- 'GetPeerInfo': "/en/developer-reference#getpeerinfo"
|
||||
- 'GetRawChangeAddress': "/en/developer-reference#getrawchangeaddress"
|
||||
- 'GetRawMempool': "/en/developer-reference#getrawmempool"
|
||||
- 'GetRawTransaction': "/en/developer-reference#getrawtransaction"
|
||||
- 'GetReceivedByAccount': "/en/developer-reference#getreceivedbyaccount"
|
||||
- 'GetReceivedByAddress': "/en/developer-reference#getreceivedbyaddress"
|
||||
- 'GetTransaction': "/en/developer-reference#gettransaction"
|
||||
- 'GetTxout': "/en/developer-reference#gettxout"
|
||||
- 'GetTxoutSetInfo': "/en/developer-reference#gettxoutsetinfo"
|
||||
- 'GetUnconfirmedBalance': "/en/developer-reference#getunconfirmedbalance"
|
||||
- 'GetWalletInfo': "/en/developer-reference#getwalletinfo"
|
||||
- 'GetWork': "/en/developer-reference#getwork"
|
||||
- 'Help': "/en/developer-reference#help"
|
||||
- 'ImportAddress': "/en/developer-reference#importaddress"
|
||||
- 'ImportPrivkey': "/en/developer-reference#importprivkey"
|
||||
- 'ImportWallet': "/en/developer-reference#importwallet"
|
||||
- 'KeypoolRefill': "/en/developer-reference#keypoolrefill"
|
||||
- 'ListAccounts': "/en/developer-reference#listaccounts"
|
||||
- 'ListAddressGroupings': "/en/developer-reference#listaddressgroupings"
|
||||
- 'ListLockUnspent': "/en/developer-reference#listlockunspent"
|
||||
- 'ListReceivedByAccount': "/en/developer-reference#listreceivedbyaccount"
|
||||
- 'ListReceivedByAddress': "/en/developer-reference#listreceivedbyaddress"
|
||||
- 'ListSinceBlock': "/en/developer-reference#listsinceblock"
|
||||
- 'ListTransactions': "/en/developer-reference#listtransactions"
|
||||
- 'ListUnspent': "/en/developer-reference#listunspent"
|
||||
- 'LockUnspent': "/en/developer-reference#lockunspent"
|
||||
- 'Move': "/en/developer-reference#move"
|
||||
- 'Ping': "/en/developer-reference#ping-rpc"
|
||||
- 'SendFrom': "/en/developer-reference#sendfrom"
|
||||
- 'SendMany': "/en/developer-reference#sendmany"
|
||||
- 'SendRawTransaction': "/en/developer-reference#sendrawtransaction"
|
||||
- 'SendToAddress': "/en/developer-reference#sendtoaddress"
|
||||
- 'SetAccount': "/en/developer-reference#setaccount"
|
||||
- 'SetGenerate': "/en/developer-reference#setgenerate"
|
||||
- 'SetTxFee': "/en/developer-reference#settxfee"
|
||||
- 'SignMessage': "/en/developer-reference#signmessage"
|
||||
- 'SignRawTransaction': "/en/developer-reference#signrawtransaction"
|
||||
- 'Stop': "/en/developer-reference#stop"
|
||||
- 'SubmitBlock': "/en/developer-reference#submitblock"
|
||||
- 'ValidateAddress': "/en/developer-reference#validateaddress"
|
||||
- 'VerifyChain': "/en/developer-reference#verifychain"
|
||||
- 'VerifyMessage': "/en/developer-reference#verifymessage"
|
||||
- 'WalletLock': "/en/developer-reference#walletlock"
|
||||
- 'WalletPassphrase': "/en/developer-reference#walletpassphrase"
|
||||
- 'WalletPassphraseChange': "/en/developer-reference#walletpassphrasechange"
|
||||
|
||||
## Op codes currently implemented in Bitcoin Core master branch. After
|
||||
## we document them on Bitcoin.org, these links will be updated
|
||||
"Op codes":
|
||||
- "OP_0 (OP_FALSE)": "https://en.bitcoin.it/wiki/Script#Constants"
|
||||
- "OP_PUSHDATA1": "https://en.bitcoin.it/wiki/Script#Constants"
|
||||
- "OP_PUSHDATA2": "https://en.bitcoin.it/wiki/Script#Constants"
|
||||
- "OP_PUSHDATA4": "https://en.bitcoin.it/wiki/Script#Constants"
|
||||
- "OP_1NEGATE": "https://en.bitcoin.it/wiki/Script#Constants"
|
||||
- "OP_1 (OP_TRUE)": "https://en.bitcoin.it/wiki/Script#Constants"
|
||||
- "OP_2": "https://en.bitcoin.it/wiki/Script#Constants"
|
||||
- "OP_3": "https://en.bitcoin.it/wiki/Script#Constants"
|
||||
- "OP_4": "https://en.bitcoin.it/wiki/Script#Constants"
|
||||
- "OP_5": "https://en.bitcoin.it/wiki/Script#Constants"
|
||||
- "OP_6": "https://en.bitcoin.it/wiki/Script#Constants"
|
||||
- "OP_7": "https://en.bitcoin.it/wiki/Script#Constants"
|
||||
- "OP_8": "https://en.bitcoin.it/wiki/Script#Constants"
|
||||
- "OP_9": "https://en.bitcoin.it/wiki/Script#Constants"
|
||||
- "OP_10": "https://en.bitcoin.it/wiki/Script#Constants"
|
||||
- "OP_11": "https://en.bitcoin.it/wiki/Script#Constants"
|
||||
- "OP_12": "https://en.bitcoin.it/wiki/Script#Constants"
|
||||
- "OP_13": "https://en.bitcoin.it/wiki/Script#Constants"
|
||||
- "OP_14": "https://en.bitcoin.it/wiki/Script#Constants"
|
||||
- "OP_15": "https://en.bitcoin.it/wiki/Script#Constants"
|
||||
- "OP_16": "https://en.bitcoin.it/wiki/Script#Constants"
|
||||
|
||||
- "OP_NOP": "https://en.bitcoin.it/wiki/Script#Flow_control"
|
||||
- "OP_IF": "https://en.bitcoin.it/wiki/Script#Flow_control"
|
||||
- "OP_NOTIF": "https://en.bitcoin.it/wiki/Script#Flow_control"
|
||||
- "OP_ELSE": "https://en.bitcoin.it/wiki/Script#Flow_control"
|
||||
- "OP_ENDIF": "https://en.bitcoin.it/wiki/Script#Flow_control"
|
||||
- "OP_VERIFY": "https://en.bitcoin.it/wiki/Script#Flow_control"
|
||||
- "OP_RETURN": "https://en.bitcoin.it/wiki/Script#Flow_control"
|
||||
|
||||
- "OP_TOALTSTACK": "https://en.bitcoin.it/wiki/Script#Stack"
|
||||
- "OP_FROMALTSTACK": "https://en.bitcoin.it/wiki/Script#Stack"
|
||||
- "OP_IFDUP": "https://en.bitcoin.it/wiki/Script#Stack"
|
||||
- "OP_DEPTH": "https://en.bitcoin.it/wiki/Script#Stack"
|
||||
- "OP_DROP": "https://en.bitcoin.it/wiki/Script#Stack"
|
||||
- "OP_DUP": "https://en.bitcoin.it/wiki/Script#Stack"
|
||||
- "OP_NIP": "https://en.bitcoin.it/wiki/Script#Stack"
|
||||
- "OP_OVER": "https://en.bitcoin.it/wiki/Script#Stack"
|
||||
- "OP_PICK": "https://en.bitcoin.it/wiki/Script#Stack"
|
||||
- "OP_ROLL": "https://en.bitcoin.it/wiki/Script#Stack"
|
||||
- "OP_ROT": "https://en.bitcoin.it/wiki/Script#Stack"
|
||||
- "OP_SWAP": "https://en.bitcoin.it/wiki/Script#Stack"
|
||||
- "OP_TUCK": "https://en.bitcoin.it/wiki/Script#Stack"
|
||||
- "OP_2DROP": "https://en.bitcoin.it/wiki/Script#Stack"
|
||||
- "OP_2DUP": "https://en.bitcoin.it/wiki/Script#Stack"
|
||||
- "OP_3DUP": "https://en.bitcoin.it/wiki/Script#Stack"
|
||||
- "OP_2OVER": "https://en.bitcoin.it/wiki/Script#Stack"
|
||||
- "OP_2ROT": "https://en.bitcoin.it/wiki/Script#Stack"
|
||||
- "OP_2SWAP": "https://en.bitcoin.it/wiki/Script#Stack"
|
||||
|
||||
- "OP_CAT (disabled)": "https://en.bitcoin.it/wiki/Script#Splice"
|
||||
- "OP_SUBSTR (disabled)": "https://en.bitcoin.it/wiki/Script#Splice"
|
||||
- "OP_LEFT (disabled)": "https://en.bitcoin.it/wiki/Script#Splice"
|
||||
- "OP_RIGHT (disabled)": "https://en.bitcoin.it/wiki/Script#Splice"
|
||||
- "OP_SIZE": "https://en.bitcoin.it/wiki/Script#Splice"
|
||||
|
||||
- "OP_INVERT (disabled)": "https://en.bitcoin.it/wiki/Script#Bitwise_logic"
|
||||
- "OP_AND (disabled)": "https://en.bitcoin.it/wiki/Script#Bitwise_logic"
|
||||
- "OP_OR (disabled)": "https://en.bitcoin.it/wiki/Script#Bitwise_logic"
|
||||
- "OP_XOR (disabled)": "https://en.bitcoin.it/wiki/Script#Bitwise_logic"
|
||||
- "OP_EQUAL": "https://en.bitcoin.it/wiki/Script#Bitwise_logic"
|
||||
- "OP_EQUALVERIFY": "https://en.bitcoin.it/wiki/Script#Bitwise_logic"
|
||||
|
||||
- "OP_1ADD": "https://en.bitcoin.it/wiki/Script#Arithmetic"
|
||||
- "OP_1SUB": "https://en.bitcoin.it/wiki/Script#Arithmetic"
|
||||
- "OP_2MUL (disabled)": "https://en.bitcoin.it/wiki/Script#Arithmetic"
|
||||
- "OP_2DIV (disabled)": "https://en.bitcoin.it/wiki/Script#Arithmetic"
|
||||
- "OP_NEGATE": "https://en.bitcoin.it/wiki/Script#Arithmetic"
|
||||
- "OP_ABS": "https://en.bitcoin.it/wiki/Script#Arithmetic"
|
||||
- "OP_NOT": "https://en.bitcoin.it/wiki/Script#Arithmetic"
|
||||
- "OP_0NOTEQUAL": "https://en.bitcoin.it/wiki/Script#Arithmetic"
|
||||
- "OP_ADD": "https://en.bitcoin.it/wiki/Script#Arithmetic"
|
||||
- "OP_SUB": "https://en.bitcoin.it/wiki/Script#Arithmetic"
|
||||
- "OP_MUL (disabled)": "https://en.bitcoin.it/wiki/Script#Arithmetic"
|
||||
- "OP_DIV (disabled)": "https://en.bitcoin.it/wiki/Script#Arithmetic"
|
||||
- "OP_MOD (disabled)": "https://en.bitcoin.it/wiki/Script#Arithmetic"
|
||||
- "OP_LSHIFT (disabled)": "https://en.bitcoin.it/wiki/Script#Arithmetic"
|
||||
- "OP_RSHIFT (disabled)": "https://en.bitcoin.it/wiki/Script#Arithmetic"
|
||||
- "OP_BOOLAND": "https://en.bitcoin.it/wiki/Script#Arithmetic"
|
||||
- "OP_BOOLOR": "https://en.bitcoin.it/wiki/Script#Arithmetic"
|
||||
- "OP_NUMEQUAL": "https://en.bitcoin.it/wiki/Script#Arithmetic"
|
||||
- "OP_NUMEQUALVERIFY": "https://en.bitcoin.it/wiki/Script#Arithmetic"
|
||||
- "OP_NUMNOTEQUAL": "https://en.bitcoin.it/wiki/Script#Arithmetic"
|
||||
- "OP_LESSTHAN": "https://en.bitcoin.it/wiki/Script#Arithmetic"
|
||||
- "OP_GREATERTHAN": "https://en.bitcoin.it/wiki/Script#Arithmetic"
|
||||
- "OP_LESSTHANOREQUAL": "https://en.bitcoin.it/wiki/Script#Arithmetic"
|
||||
- "OP_GREATERTHANOREQUAL": "https://en.bitcoin.it/wiki/Script#Arithmetic"
|
||||
- "OP_MIN": "https://en.bitcoin.it/wiki/Script#Arithmetic"
|
||||
- "OP_MAX": "https://en.bitcoin.it/wiki/Script#Arithmetic"
|
||||
- "OP_WITHIN": "https://en.bitcoin.it/wiki/Script#Arithmetic"
|
||||
|
||||
- "OP_RIPEMD160": "https://en.bitcoin.it/wiki/Script#Crypto"
|
||||
- "OP_SHA1": "https://en.bitcoin.it/wiki/Script#Crypto"
|
||||
- "OP_SHA256": "https://en.bitcoin.it/wiki/Script#Crypto"
|
||||
- "OP_HASH160": "https://en.bitcoin.it/wiki/Script#Crypto"
|
||||
- "OP_HASH256": "https://en.bitcoin.it/wiki/Script#Crypto"
|
||||
- "OP_CODESEPARATOR": "https://en.bitcoin.it/wiki/Script#Crypto"
|
||||
- "OP_CHECKSIG": "https://en.bitcoin.it/wiki/Script#Crypto"
|
||||
- "OP_CHECKSIGVERIFY": "https://en.bitcoin.it/wiki/Script#Crypto"
|
||||
- "OP_CHECKMULTISIG": "https://en.bitcoin.it/wiki/Script#Crypto"
|
||||
- "OP_CHECKMULTISIGVERIFY": "https://en.bitcoin.it/wiki/Script#Crypto"
|
||||
|
||||
- "OP_PUBKEYHASH (invalid)": "https://en.bitcoin.it/wiki/Script#Pseudo-words"
|
||||
- "OP_PUBKEY (invalid)": "https://en.bitcoin.it/wiki/Script#Pseudo-words"
|
||||
- "OP_INVALIDOPCODE (invalid)": "https://en.bitcoin.it/wiki/Script#Pseudo-words"
|
||||
|
||||
- "OP_RESERVED (reserved)": "https://en.bitcoin.it/wiki/Script#Reserved_words"
|
||||
- "OP_VER (reserved)": "https://en.bitcoin.it/wiki/Script#Reserved_words"
|
||||
- "OP_VERIF (reserved)": "https://en.bitcoin.it/wiki/Script#Reserved_words"
|
||||
- "OP_VERNOTIF (reserved)": "https://en.bitcoin.it/wiki/Script#Reserved_words"
|
||||
- "OP_RESERVED1 (reserved)": "https://en.bitcoin.it/wiki/Script#Reserved_words"
|
||||
- "OP_RESERVED2 (reserved)": "https://en.bitcoin.it/wiki/Script#Reserved_words"
|
||||
- "OP_NOP1 (reserved)": "https://en.bitcoin.it/wiki/Script#Reserved_words"
|
||||
- "OP_NOP2 (reserved)": "https://en.bitcoin.it/wiki/Script#Reserved_words"
|
||||
- "OP_NOP3 (reserved)": "https://en.bitcoin.it/wiki/Script#Reserved_words"
|
||||
- "OP_NOP4 (reserved)": "https://en.bitcoin.it/wiki/Script#Reserved_words"
|
||||
- "OP_NOP5 (reserved)": "https://en.bitcoin.it/wiki/Script#Reserved_words"
|
||||
- "OP_NOP6 (reserved)": "https://en.bitcoin.it/wiki/Script#Reserved_words"
|
||||
- "OP_NOP7 (reserved)": "https://en.bitcoin.it/wiki/Script#Reserved_words"
|
||||
- "OP_NOP8 (reserved)": "https://en.bitcoin.it/wiki/Script#Reserved_words"
|
||||
- "OP_NOP9 (reserved)": "https://en.bitcoin.it/wiki/Script#Reserved_words"
|
||||
- "OP_NOP10 (reserved)": "https://en.bitcoin.it/wiki/Script#Reserved_words"
|
||||
|
||||
## Only notable and non-withdrawn BIPs. Try to keep descriptions short
|
||||
## and focused on likely keywords
|
||||
"BIPs":
|
||||
- "BIP1: BIP purpose and guidelines": "https://github.com/bitcoin/bips/blob/master/bip-0001.mediawiki"
|
||||
- "BIP11: m-of-n multisig transactions": "https://github.com/bitcoin/bips/blob/master/bip-0011.mediawiki"
|
||||
- "BIP13: P2SH address format": "https://github.com/bitcoin/bips/blob/master/bip-0013.mediawiki"
|
||||
- "BIP14: protocol version & user agent": "https://github.com/bitcoin/bips/blob/master/bip-0014.mediawiki"
|
||||
- "BIP16: pay to script hash (P2SH)": "https://github.com/bitcoin/bips/blob/master/bip-0016.mediawiki"
|
||||
- "BIP21: URI scheme": "https://github.com/bitcoin/bips/blob/master/bip-0021.mediawiki"
|
||||
- "BIP22: GetBlockTemplate fundamentals": "https://github.com/bitcoin/bips/blob/master/bip-0022.mediawiki"
|
||||
- "BIP23: GetBlockTemplate pooled mining": "https://github.com/bitcoin/bips/blob/master/bip-0023.mediawiki"
|
||||
- "BIP30: dealing with duplicate transactions": "https://github.com/bitcoin/bips/blob/master/bip-0030.mediawiki"
|
||||
- "BIP31: P2P pong message": "https://github.com/bitcoin/bips/blob/master/bip-0031.mediawiki"
|
||||
- "BIP32: HD wallets": "https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki"
|
||||
- "BIP34: block height in coinbase": "https://github.com/bitcoin/bips/blob/master/bip-0034.mediawiki"
|
||||
- "BIP35: P2P mempool message": "https://github.com/bitcoin/bips/blob/master/bip-0035.mediawiki"
|
||||
- "BIP37: bloom filtering": "https://github.com/bitcoin/bips/blob/master/bip-0037.mediawiki"
|
||||
- "BIP38: passphrase-protected private key": "https://github.com/bitcoin/bips/blob/master/bip-0038.mediawiki"
|
||||
- "BIP39: mnemonic code for HD wallets": "https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki"
|
||||
- "BIP42: finite monetary supply": "https://github.com/bitcoin/bips/blob/master/bip-0042.mediawiki"
|
||||
- "BIP44: HD wallet account hierarchy": "https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki"
|
||||
- "BIP50: March 2013 fork post-mortem": "https://github.com/bitcoin/bips/blob/master/bip-0050.mediawiki"
|
||||
- "BIP60: fixed-length version message": "https://github.com/bitcoin/bips/blob/master/bip-0060.mediawiki"
|
||||
- "BIP61: P2P reject message": "https://github.com/bitcoin/bips/blob/master/bip-0061.mediawiki"
|
||||
- "BIP62: dealing with malleability": "https://github.com/bitcoin/bips/blob/master/bip-0062.mediawiki"
|
||||
- "BIP64: P2P geutxos message": "https://github.com/bitcoin/bips/blob/master/bip-0064.mediawiki"
|
||||
- "BIP65: OP_CHECKLOCKTIMEVERIFY": "https://github.com/bitcoin/bips/blob/master/bip-0065.mediawiki"
|
||||
- "BIP66: strict DER signatures": "https://github.com/bitcoin/bips/blob/master/bip-0066.mediawiki"
|
||||
- "BIP70: payment protocol": "https://github.com/bitcoin/bips/blob/master/bip-0070.mediawiki"
|
||||
- "BIP71: payment protocol MIME types": "https://github.com/bitcoin/bips/blob/master/bip-0071.mediawiki"
|
||||
- "BIP72: payment protocol URIs": "https://github.com/bitcoin/bips/blob/master/bip-0072.mediawiki"
|
||||
- "BIP73: accept header with payment protocol": "https://github.com/bitcoin/bips/blob/master/bip-0073.mediawiki"
|
||||
|
||||
## Bitcoin P2P Protocol messages documented on Bitcoin.org
|
||||
"P2P Messages":
|
||||
- "addr": "/en/developer-reference#addr"
|
||||
- "alert": "/en/developer-reference#alert"
|
||||
- "block": "/en/developer-reference#block"
|
||||
- "filteradd": "/en/developer-reference#filteradd"
|
||||
- "filterclear": "/en/developer-reference#filterclear"
|
||||
- "filterload": "/en/developer-reference#filterload"
|
||||
- "getaddr": "/en/developer-reference#getaddr"
|
||||
- "getblocks": "/en/developer-reference#getblocks"
|
||||
- "getdata": "/en/developer-reference#getdata"
|
||||
- "getheaders": "/en/developer-reference#getheaders"
|
||||
- "headers": "/en/developer-reference#headers"
|
||||
- "inv": "/en/developer-reference#inv"
|
||||
- "mempool": "/en/developer-reference#mempool"
|
||||
- "merkleblock": "/en/developer-reference#merkleblock"
|
||||
- "notfound": "/en/developer-reference#notfound"
|
||||
- "ping": "/en/developer-reference#ping"
|
||||
- "pong": "/en/developer-reference#pong"
|
||||
- "reject": "/en/developer-reference#reject"
|
||||
- "tx": "/en/developer-reference#tx"
|
||||
- "verack": "/en/developer-reference#verack"
|
||||
- "version": "/en/developer-reference#version"
|
||||
|
|
|
|||
|
|
@ -1,37 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: 51% Attack, Majority Hash Rate Attack
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
The ability of someone controlling a majority of network
|
||||
hash rate to revise transaction history and prevent new
|
||||
transactions from confirming.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- 51 percent attack
|
||||
- Majority attack
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- 51 percent attacks
|
||||
|
||||
- majority attacks
|
||||
|
||||
- 51% attack
|
||||
- 51% attacks
|
||||
|
||||
- majority hash rate attack
|
||||
- majority hash rate attacks
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[51% attack](/en/developer-guide#term-51-attack) --- Bitcoin.org Developer Guide"
|
||||
- "[What can an attacker with 51% of hash power do?](http://bitcoin.stackexchange.com/q/658) --- Bitcoin StackExchange"
|
||||
- "[Bitcoin.pdf](/bitcoin.pdf) --- Satoshi Nakamoto (Bitcoin.org)"
|
||||
|
||||
---
|
||||
|
|
@ -1,29 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Payment Addresses
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
A 20-byte hash formatted using base58check to produce either a
|
||||
P2PKH or P2SH Bitcoin address. Currently the most common way
|
||||
users exchange payment information.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Address
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- addresses
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- IP address
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Address](/en/developer-guide#term-address) --- Bitcoin.org Developer Guide"
|
||||
- "[Address](https://en.bitcoin.it/wiki/Address) --- Bitcoin Wiki"
|
||||
|
||||
|
||||
---
|
||||
|
|
@ -1,32 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Base58check, Bitcoin Address Encoding
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
The method used in Bitcoin for converting 160-bit hashes into
|
||||
P2PKH and P2SH addresses. Also used in other parts of Bitcoin,
|
||||
such as encoding private keys for backup in WIP format. Not the
|
||||
same as other base58 implementations.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Base58check
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- base58
|
||||
- base-58
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- P2PKH address
|
||||
- P2SH address
|
||||
- IP address
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[base58check](/en/developer-reference#term-base58check) --- Bitcoin.org Developer Reference"
|
||||
- "[Base58Check encoding](https://en.bitcoin.it/wiki/Base58Check_encoding) --- Bitcoin Wiki"
|
||||
|
||||
---
|
||||
|
|
@ -1,36 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Block Chain
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
A chain of blocks with each block referencing the block
|
||||
that preceded it. The most-difficult-to-recreate chain is
|
||||
the best block chain.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Block chain
|
||||
- Best block chain ## this could be moved into its own entry
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- block chains
|
||||
- blocks chain
|
||||
- block-chain
|
||||
- block-chains
|
||||
- blockchain
|
||||
- blockchains
|
||||
- best block chain
|
||||
- best blockchain
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Header chain
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Block chain](/en/developer-guide#block-chain) --- Bitcoin.org Developer Guide"
|
||||
- "[Block chain](https://en.bitcoin.it/wiki/Block_chain) --- Bitcoin Wiki"
|
||||
|
||||
---
|
||||
|
|
@ -1,29 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Block Header
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
An 80-byte header belonging to a single block which is hashed
|
||||
repeatedly to create proof of work.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Block header
|
||||
- Header
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- headers
|
||||
- block headers
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Block header](/en/developer-reference#block-headers) --- Bitcoin.org Developer Reference"
|
||||
- "[Block hashing algorithm](https://en.bitcoin.it/wiki/Block_hashing_algorithm) --- Bitcoin Wiki"
|
||||
- "[What are Bitcoin miners really solving?](http://bitcoin.stackexchange.com/q/8031) --- Bitcoin StackExchange"
|
||||
|
||||
---
|
||||
|
|
@ -1,33 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Block Chain Height, Block Height
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
The number of blocks preceding a particular block on a block
|
||||
chain. For example, the genesis block has a height of zero
|
||||
because zero block preceded it.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Height
|
||||
- Block height
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- heights
|
||||
- block heights
|
||||
- block chain height
|
||||
- block chain heights
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Block height](/en/developer-guide#term-block-height) --- Bitcoin.org Developer Guide"
|
||||
- "[Definition of block height](http://bitcoin.stackexchange.com/q/18561) --- Bitcoin StackExchange"
|
||||
- "[Why is block height required in the coinbase?](http://bitcoin.stackexchange.com/q/30764) --- Bitcoin StackExchange"
|
||||
- "[Is block height always sequencial?](http://bitcoin.stackexchange.com/q/24309) --- Bitcoin StackExchange"
|
||||
|
||||
---
|
||||
|
|
@ -1,30 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Block Reward, Block Miner Reward
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
The amount that miners may claim as a reward for creating a
|
||||
block. Equal to the sum of the block subsidy (newly available
|
||||
satoshis) plus the transactions fees paid by transactions
|
||||
included in the block.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Block reward
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- block rewards
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Block subsidy
|
||||
- Transaction fees
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Block reward](/en/developer-reference#term-block-reward) --- Bitcoin.org Developer Reference"
|
||||
|
||||
|
||||
---
|
||||
|
|
@ -1,27 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Block, Block Of Transactions
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
One or more transactions prefaced by a block header and
|
||||
protected by proof of work. Blocks are the data stored on the
|
||||
block chain.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Block
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- Blocks
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Block](/en/developer-guide#term-block) --- Bitcoin.org Developer Guide"
|
||||
- "[Block](https://en.bitcoin.it/wiki/Block) --- Bitcoin Wiki"
|
||||
|
||||
---
|
||||
|
|
@ -1,28 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Blocks-First, Blocks-First Sync
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
Synchronizing the block chain by downloading each block from a
|
||||
peer and then validating it.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Blocks-first sync
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- Blocks-first
|
||||
- Blocks-first initial block download
|
||||
- Blocks-first IBD
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Headers-first sync
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Blocks-first sync](/en/developer-guide#blocks-first) --- Bitcoin.org Developer Guide"
|
||||
|
||||
---
|
||||
|
|
@ -1,29 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Bloom Filter
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
A filter used primarily by SPV clients to request only matching
|
||||
transactions and merkle blocks from full nodes.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Bloom filter
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- Bloom filters
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Bloom filter (general computer science term, of which Bitcoin's bloom filters are a specific implementation)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Bloom filter](/en/developer-guide#bloom-filters) --- Bitcoin.org Developer Guide"
|
||||
- "[BIP37: Connection Bloom Filtering](https://github.com/bitcoin/bips/blob/master/bip-0037.mediawiki)--- Bitcoin Improvement Proposals"
|
||||
- "[Pull request that implemented bloom filters in Bitcoin Core](https://github.com/bitcoin/bitcoin/pull/1795) --- GitHub"
|
||||
- "[Discussion about bloom filtering and SPV clients](https://bitcointalk.org/index.php?topic=252937.0) --- BitcoinTalk"
|
||||
|
||||
---
|
||||
|
|
@ -1,35 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Chain Code, HD Wallet Chain Code
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
In HD wallets, 256 bits of entropy added to the public and
|
||||
private keys to help them generate secure child keys; the master
|
||||
chain code is usually derived from a seed along with the master
|
||||
private key
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Chain code
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- Chain codes
|
||||
- HD wallet chain code
|
||||
- HD wallet chain codes
|
||||
- parent chain code
|
||||
- parent chain codes
|
||||
- child chain code
|
||||
- child chain codes
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Chain code](/en/developer-guide#term-chain-code) --- Bitcoin.org Developer Guide"
|
||||
- "[BIP32: Hierarchical Deterministic Wallets](https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki) --- Bitcoin Improvement Proposals"
|
||||
- "[Deterministic wallet](https://en.bitcoin.it/wiki/Deterministic_Wallet) --- Bitcoin wiki"
|
||||
|
||||
---
|
||||
|
|
@ -1,33 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Change, Change Address, Change Output
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
An output in a transaction which returns satoshis to the
|
||||
spender, thus preventing too much of the input value from going
|
||||
to transaction fees.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Change address
|
||||
- Change output
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- change addresses
|
||||
- change outputs
|
||||
## don't add "change" or it'll get autocrossreferenced every
|
||||
## time we use it with its usual verb/noun meanings
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Address reuse
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Change address](/en/developer-guide#term-change-output) --- Bitcoin.org Developer Guide"
|
||||
- "[Change](https://en.bitcoin.it/wiki/Change) --- Bitcoin Wiki"
|
||||
- "[Why does Bitcoin Core use separate change addresses?](http://bitcoin.stackexchange.com/q/35412) --- Bitcoin StackExchange"
|
||||
|
||||
---
|
||||
|
|
@ -1,38 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Child Key, HD Wallet Child Key
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
In HD wallets, a key derived from a parent key. The key can be
|
||||
either a private key or a public key, and the key derivation may
|
||||
also require a chain code.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Child key
|
||||
- Child public key
|
||||
- Child private key
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- Child keys
|
||||
- child public keys
|
||||
- child private keys
|
||||
|
||||
- HD wallet child key
|
||||
- HD wallet child keys
|
||||
|
||||
- child private and public keys
|
||||
- child public and private keys
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Public key (derived from a private key, not a parent key)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Child key](/en/developer-guide#term-child-public-key) --- Bitcoin.org Developer Guide"
|
||||
- "[BIP32: Hierarchical Deterministic Wallets](https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki) --- Bitcoin Improvement Proposals"
|
||||
|
||||
---
|
||||
|
|
@ -1,31 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Coinbase / Generation Transaction
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
The first transaction in a block. Always created by a miner, it
|
||||
includes a single coinbase.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Coinbase transaction
|
||||
- Generation transaction
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- Coinbase transactions
|
||||
- generation transactions
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Coinbase (the unique part of a coinbase transaction)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Coinbase transaction](/en/developer-reference#term-coinbase-tx) --- Bitcoin.org Developer Reference"
|
||||
- "[Generation transaction](https://en.bitcoin.it/wiki/Transaction#Generation) --- Bitcoin Wiki"
|
||||
- "[Who generates the coinbase transaction?](http://bitcoin.stackexchange.com/q/32091) --- Bitcoin StackExchange"
|
||||
- "[Must a block contain a coinbase transaction?](http://bitcoin.stackexchange.com/q/30349) --- Bitcoin StackExchange"
|
||||
|
||||
---
|
||||
|
|
@ -1,32 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Coinbase, Coinbase Field
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
A special field used as the sole input for coinbase
|
||||
transactions. The coinbase allows claiming the block reward and
|
||||
provides up to 100 bytes for arbitrary data.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Coinbase
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- Coinbases
|
||||
|
||||
- coinbase field
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Coinbase transaction
|
||||
- Coinbase.com
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Coinbase](/en/developer-reference#term-coinbase-field) --- Bitcoin.org Developer Reference"
|
||||
- "[Coinbase](https://en.bitcoin.it/wiki/Coinbase) --- Bitcoin Wiki"
|
||||
- "[What is the coinbase?](http://bitcoin.stackexchange.com/q/4571) --- Bitcoin StackExchange"
|
||||
|
||||
---
|
||||
|
|
@ -1,31 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: CompactSize Unsigned Integer
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
A type of variable-length integer commonly used in the Bitcoin
|
||||
P2P protocol and Bitcoin serialized data structures.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- CompactSize
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- compactsize unsigned integer
|
||||
- compactsize unsigned integers
|
||||
- compactsize uint
|
||||
- compactsize uints
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- VarInt (a data type Bitcoin Core uses for local data storage)
|
||||
- Compact (the data type used for nBits in the block header)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[CompactSize Unsigned Integers](/en/developer-reference#compactsize-unsigned-integers) --- Bitcoin.org Developer Reference"
|
||||
- "[Variable length integers (compactSize)](https://en.bitcoin.it/wiki/Protocol_documentation#Variable_length_integer) --- Bitcoin Wiki"
|
||||
|
||||
---
|
||||
|
|
@ -1,28 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Compressed Public Key
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
An ECDSA public key that is 33 bytes long rather than the 65
|
||||
bytes of an uncompressed public key.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Compressed public key
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- compressed public keys
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Public key formats](/en/developer-guide#public-key-formats) --- Bitcoin.org Developer Guide"
|
||||
- "[What is a compressed public key?](http://bitcoin.stackexchange.com/q/3059) --- Bitcoin StackExchange"
|
||||
- "[Why does Bitcoin Core support both compressed and uncompressed keys?](http://bitcoin.stackexchange.com/q/5952) --- Bitcoin StackExchange"
|
||||
|
||||
|
||||
---
|
||||
|
|
@ -1,39 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Confirmation Score, Confirmed Transaction
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
A score indicating the number of blocks on the best block chain
|
||||
that would need to be modified to remove or modify a particular
|
||||
transaction. A confirmed transaction has a confirmation score of
|
||||
one or higher.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Confirmation score
|
||||
- Confirmations
|
||||
- Confirmed transaction
|
||||
- Unconfirmed transaction
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- Confirmed
|
||||
- unconfirmed
|
||||
- confirmation
|
||||
- confirmation scores
|
||||
|
||||
- confirmed transactions
|
||||
- unconfirmed transactions
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Confirmations](/en/developer-guide#term-confirmation) --- Bitcoin.org Developer Guide"
|
||||
- "[Confirmation](https://en.bitcoin.it/wiki/Confirmation) --- Bitcoin Wiki"
|
||||
- "[What are confirmations?](http://bitcoin.stackexchange.com/a/160) --- Bitcoin StackExchange"
|
||||
- "[When should I worry about 1-confirmation payments?](http://bitcoin.stackexchange.com/q/32562) --- Bitcoin StackExchange"
|
||||
|
||||
---
|
||||
|
|
@ -1,30 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Consensus Rules, Validation Rules
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
The block validation rules that full nodes follow to stay in
|
||||
consensus with other nodes.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Consensus rules
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- consensus rule
|
||||
- block chain validation rule
|
||||
- Block chain validation rules
|
||||
- validation rule
|
||||
- validation rules
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Consensus (what happens when nodes follow the same consensus rules)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Consensus rules](/en/developer-guide#term-consensus-rules) --- Bitcoin.org Developer Guide"
|
||||
|
||||
---
|
||||
|
|
@ -1,27 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Consensus
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
When several nodes (usually most nodes on the network) all have
|
||||
the same blocks in their locally-validated best block chain.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Consensus
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- block chain consensus
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Social consensus (often used in discussion among developers to indicate that most people agree with a particular plan)
|
||||
- Consensus rules (the rules that allow nodes to maintain consensus)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Consensus](/en/developer-guide#term-consensus) --- Bitcoin.org Developer Guide"
|
||||
|
||||
---
|
||||
|
|
@ -1,30 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Difficulty, Network Difficulty
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
How difficult it is to find a block relative to the difficulty
|
||||
of finding the easiest possible block. The easiest possible
|
||||
block has a proof-of-work difficulty of 1.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Difficulty
|
||||
- Network difficulty
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- hash difficulty
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Target threshold (the value from which difficulty is calculated)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Difficulty](/en/developer-guide#term-difficulty) --- Bitcoin.org Developer Guide"
|
||||
- "[Difficulty](https://en.bitcoin.it/wiki/Difficulty) --- Bitcoin Wiki"
|
||||
- "[How is difficulty calculated?](http://bitcoin.stackexchange.com/q/5838) --- Bitcoin StackExchange"
|
||||
|
||||
---
|
||||
|
|
@ -1,28 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: DNS Seed
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
A DNS server which returns IP addresses of full nodes on the
|
||||
Bitcoin network to assist in peer discovery.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- DNS seed
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- DNS seeds
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- HD wallet seeds
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[DNS seed](/en/developer-guide#term-dns-seed) --- Bitcoin.org Developer Guide"
|
||||
- "[DNS seeds](https://en.bitcoin.it/wiki/Satoshi_Client_Node_Discovery#DNS_Addresses) --- Bitcoin Wiki"
|
||||
- "[What is a DNS seed versus a seed node?](http://bitcoin.stackexchange.com/q/14371) --- Bitcoin StackExchange"
|
||||
|
||||
---
|
||||
|
|
@ -1,34 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Double Spend
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
A transaction that spends the same input as spent in another
|
||||
transaction.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Double spend
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- double spends
|
||||
- double spent
|
||||
- double-spend
|
||||
- double-spends
|
||||
- double-spent
|
||||
- dobule spending
|
||||
- double-spending
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Double spend](/en/developer-guide#term-double-spend) --- Bitcoin.org Developer Guide"
|
||||
- "[Double spending](https://en.bitcoin.it/wiki/Double-spending) --- Bitcoin Wiki"
|
||||
- "[What is a double spend?](http://bitcoin.stackexchange.com/q/4974) --- Bitcoin StackExchange"
|
||||
- "[How do I detect a double spend?](http://bitcoin.stackexchange.com/q/13370) --- Bitcoin StackExchange"
|
||||
|
||||
---
|
||||
|
|
@ -1,29 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Escrow Contract
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
A transaction in which a spender and receiver place funds in a
|
||||
2-of-2 (or other m-of-n) multisig output so that neither can
|
||||
spend the funds until they're both satisfied with some
|
||||
external outcome.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Escrow contract
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- Escrow contracts
|
||||
- escrow
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Escrow contract](/en/developer-guide#term-escrow-contract) --- Bitcoin.org Developer Guide"
|
||||
- "[Escrow and dispute mediation](https://en.bitcoin.it/wiki/Contracts#Example_2:_Escrow_and_dispute_mediation) --- Bitcoin Wiki"
|
||||
|
||||
---
|
||||
|
|
@ -1,34 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Extended Key, HD Wallet Extended Key
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
In the context of HD wallets, a public key or private key
|
||||
extended with the chain code to allow them to derive child keys.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Extended key
|
||||
- Public extended key
|
||||
- Private extended key
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- extended keys
|
||||
- public extended keys
|
||||
- private extended keys
|
||||
- public and private extended key
|
||||
- public and private extended keys
|
||||
- private and public extended key
|
||||
- private and public extended keys
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Extended key](/en/developer-guide#term-extended-key) --- Bitcoin.org Developer Guide"
|
||||
- "[BIP32: hierarchical deterministic wallets](https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki) --- Bitcoin Improvement Proposals"
|
||||
|
||||
---
|
||||
|
|
@ -1,33 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Fork, Accidental Fork
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
When two or more blocks have the same block height, forking the
|
||||
block chain. Typically occurs when two or more miners find
|
||||
blocks at nearly the same time. Can also happen as part of an
|
||||
attack.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Fork
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- Forks
|
||||
- accidental forks
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Hard fork (a change in consensus rules that breaks security for nodes that don't upgrade)
|
||||
- Soft fork (a change in consensus rules that weakens security for nodes that don't upgrade)
|
||||
- Software fork (when one or more developers permanently develops a codebase separately from other developers)
|
||||
- Git fork (when one or more developers temporarily develops a codebase separately from other developers)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Fork](/en/developer-guide#term-fork) --- Bitcoin.org Developer Guide"
|
||||
- "[What is the longest block chain fork that has been made stale so far?](http://bitcoin.stackexchange.com/q/3343) --- Bitcoin StackExchange"
|
||||
|
||||
---
|
||||
|
|
@ -1,29 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Genesis Block, Block 0
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
The first block in the Bitcoin block chain.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Genesis block
|
||||
- Block 0
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- Genesis blocks
|
||||
- block zero
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Generation transaction (the first transaction in a block)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Genesis block](/en/developer-guide#term-genesis-block) --- Bitcoin.org Developer Guide"
|
||||
- "[Genesis block](https://en.bitcoin.it/wiki/Genesis_block) --- Bitcoin Wiki"
|
||||
- "[Why can't the genesis block coinbase transaction be spent?](http://bitcoin.stackexchange.com/q/10009) --- Bitcoin StackExchange"
|
||||
|
||||
---
|
||||
|
|
@ -1,34 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Hard Fork, Hard-Forking Change
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
A permanent divergence in the the block chain, commonly occurs
|
||||
when non-upgraded nodes can't validate blocks created by
|
||||
upgraded nodes that follow newer consensus rules.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Hard fork
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- hard forks
|
||||
- hard-forking change
|
||||
- hard-forking
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Fork (a regular fork where all nodes follow the same consensus rules, so the fork is resolved once one chain has more proof of work than another)
|
||||
- Soft fork (a temporary divergence in the block chain caused by non-upgraded nodes not following new consensus rules)
|
||||
- Software fork (when one or more developers permanently develops a codebase separately from other developers)
|
||||
- Git fork (when one or more developers temporarily develops a codebase separately from other developers
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Hard fork](/en/developer-guide#term-hard-fork) --- Bitcoin.org Developer Guide"
|
||||
- "[Hard fork](https://en.bitcoin.it/wiki/Hardfork) --- Bitcoin Wiki"
|
||||
- "[Has a hard fork ever occurred?](http://bitcoin.stackexchange.com/q/36090) --- Bitcoin StackExchange"
|
||||
|
||||
---
|
||||
|
|
@ -1,30 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Hardened Extended Key (HD Wallets)
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
A variation on HD wallet extended keys where only the hardened
|
||||
extended private key can derive child keys. This prevents
|
||||
compromise of the chain code plus any private key from putting
|
||||
the whole wallet at risk.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Hardened extended key
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- hardened extended keys
|
||||
- hardened extended private key
|
||||
- hardened extended private keys
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Hardened extended private keys](/en/developer-guide#term-hardened-extended-private-key) --- Bitcoin.org Developer Guide"
|
||||
- "[BIP32: hierarchical deterministic wallets](https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki) --- Bitcoin Improvement Proposals"
|
||||
|
||||
---
|
||||
|
|
@ -1,34 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: HD Protocol, HD Wallet, BIP32
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
The Hierarchical Deterministic (HD) key creation and transfer
|
||||
protocol (BIP32), which allows creating child keys from parent
|
||||
keys in a hierarchy. Wallets using the HD protocol are called
|
||||
HD wallets.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- HD protocol
|
||||
- HD wallet
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- HD protocols
|
||||
- HD wallets
|
||||
- hierarchical deterministic
|
||||
- hierarchical deterministic protocol
|
||||
- hierarchical deterministic wallets
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[HD Protocol](/en/developer-guide#term-hd-protocol) --- Bitcoin.org Developer Guide"
|
||||
- "[BIP32: hierarchical deterministic wallets](https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki) --- Bitcoin Improvement Proposals"
|
||||
- "[Deterministic wallet](https://en.bitcoin.it/wiki/Deterministic_Wallet) --- Bitcoin Wiki"
|
||||
|
||||
---
|
||||
|
|
@ -1,32 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: HD Wallet Seed, Root Seed
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
A potentially-short value used as a seed to generate the master
|
||||
private key and master chain code for an HD wallet.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- HD wallet seed
|
||||
- Root seed
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- hd wallet seeds
|
||||
- root seeds
|
||||
- hd seed
|
||||
- hd seeds
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Mnemonic code / mnemonic seed (a binary root seed formatted as words to make it easier for humans to transcribe and possibly remember)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Root seed](/en/developer-guide#term-root-seed) --- Bitcoin.org Developer Guide"
|
||||
- "[BIP32: hierarchical deterministic wallets](https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki) --- Bitcoin Improvement Proposals"
|
||||
- "[BIP39: mnemonic code for generating deterministic keys](https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki) --- Bitcoin Improvement Proposals"
|
||||
|
||||
---
|
||||
|
|
@ -1,36 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Header Chain, Best Header Chain
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
A chain of block headers with each header linking to the header
|
||||
that preceded it; the most-difficult-to-recreate chain is the
|
||||
best header chain
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Header chain
|
||||
- Best header chain
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- header chains
|
||||
- headers chain
|
||||
- header-chain
|
||||
- header-chains
|
||||
- headerchain
|
||||
- headerchains
|
||||
- best header chain
|
||||
- best headerchain
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Block chain
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Header chain](/en/developer-guide#term-header-chain) --- Bitcoin.org Developer Guide"
|
||||
- "[Is it a chain of headers rather than a chain of blocks?](http://bitcoin.stackexchange.com/q/35448) --- Bitcoin StackExchange"
|
||||
|
||||
---
|
||||
|
|
@ -1,29 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Headers-First, Headers-First Sync
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
Synchronizing the block chain by downloading block headers
|
||||
before downloading the full blocks.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Headers-first sync
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- Headers-first
|
||||
- Headers-first initial block download
|
||||
- Headers-first IBD
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Blocks-first sync (Downloading entire blocks immediately without first getting their headers)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Headers-first sync](/en/developer-guide#headers-first) --- Bitcoin.org Developer Guide"
|
||||
- "[Pull request adding headers-first sync to Bitcoin Core](https://github.com/bitcoin/bitcoin/pull/4468) --- GitHub"
|
||||
|
||||
---
|
||||
|
|
@ -1,30 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: High-Priority Transaction, Free Tx
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
Transactions that don't have to pay a transaction fee because
|
||||
their inputs have been idle long enough to accumulated large
|
||||
amounts of priority. Note: miners choose whether to accept free
|
||||
transactions.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- High-priority transaction
|
||||
- Free transaction
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- high-priority transactions
|
||||
- free transactions
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[High-priority transactions](/en/developer-guide#term-high-priority-transactions) --- Bitcoin.org Developer Guide"
|
||||
- "[Free transaction relay policy](https://en.bitcoin.it/wiki/Free_transaction_relay_policy) --- Bitcoin Wiki"
|
||||
|
||||
---
|
||||
|
|
@ -1,27 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Initial Block Download, IBD
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
The process used by a new node (or long-offline node) to
|
||||
download a large number of blocks to catch up to the tip of the
|
||||
best block chain.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Initial block download
|
||||
- IBD
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Blocks-first sync (syncing includes getting any amount of blocks; IBD is only used for large numbers of blocks)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Initial block download](/en/developer-guide#initial-block-download) --- Bitcoin.org Developer Guide"
|
||||
|
||||
---
|
||||
|
|
@ -1,31 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Input, Transaction Input, TxIn
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
An input in a transaction which contains four fields: an
|
||||
outpoint, a signature script, and a sequence number. The
|
||||
outpoint references a previous output and the signature script
|
||||
allows spending it.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Input
|
||||
- TxIn
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- inputs
|
||||
- txins
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Input](/en/developer-guide#term-input) --- Bitcoin.org Developer Guide"
|
||||
- "[TxIn](/en/developer-reference#txin) --- Bitcoin.org Developer Reference"
|
||||
- "[Inputs](https://en.bitcoin.it/wiki/Transaction#Input) --- Bitcoin Wiki"
|
||||
|
||||
---
|
||||
|
|
@ -1,28 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Internal Byte Order
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
The standard order in which hash digests are displayed as
|
||||
strings---the same format used in serialized blocks and
|
||||
transactions.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Internal byte order
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- Internal hash byte order
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- RPC byte order (where the byte order is reversed)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Internal byte order](/en/developer-reference#hash-byte-order) --- Bitcoin.org Developer Reference"
|
||||
- "[Block hashing algorithm ('endian conversion')](https://en.bitcoin.it/wiki/Block_hashing_algorithm) --- Bitcoin Wiki"
|
||||
|
||||
---
|
||||
|
|
@ -1,27 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Inventory, Block Or Transaction Inventory
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
A data type identifier and a hash; used to identify transactions
|
||||
and blocks available for download through the Bitcoin P2P network.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Inventory
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- inventories
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Inv message (one of the P2P messages that transmits inventories)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Inventory](/en/developer-reference#term-inventory) --- Bitcoin.org Developer Reference"
|
||||
- "[Inventory vectors](https://en.bitcoin.it/wiki/Protocol_documentation#Inventory_Vectors) --- Bitcoin Wiki"
|
||||
|
||||
---
|
||||
|
|
@ -1,28 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Locktime, nLockTime
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
Part of a transaction which indicates the earliest time or
|
||||
earliest block when that transaction may be added to the
|
||||
block chain.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Locktime
|
||||
- nLockTime
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Locktime](/en/developer-guide#term-locktime) --- Bitcoin.org Developer Guide"
|
||||
- "[nLockTime](https://en.bitcoin.it/wiki/NLockTime) --- Bitcoin Wiki"
|
||||
- "[How is locktime enforced in Bitcoin Core?](http://bitcoin.stackexchange.com/q/5914) --- Bitcoin StackExchange"
|
||||
|
||||
---
|
||||
|
|
@ -1,26 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Mainnet, Bitcoin Main Network
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
The original and main network for Bitcoin transactions, where
|
||||
satoshis have real economic value.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Mainnet
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Testnet (an open network very similar to mainnet where satoshis have no value)
|
||||
- Regtest (a private testing node similar to testnet)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Mainnet](/en/developer-examples#term-mainnet) --- Bitcoin.org Developer Examples"
|
||||
|
||||
---
|
||||
|
|
@ -1,32 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Transaction Malleability, Mutability
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
The ability of someone to change (mutate) unconfirmed
|
||||
transactions without making them invalid, which changes the
|
||||
transaction's txid, making child transactions invalid.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Transaction malleability
|
||||
- Transaction mutability
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- malleability
|
||||
- mutability
|
||||
- mutate
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- BIP62 (a proposal for an optional new transaction version that reduces the set of known mutations for common transactions)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Transaction malleability](/en/developer-guide#transaction-malleability) --- Bitcoin.org Developer Guide"
|
||||
- "[Transaction malleability](https://en.bitcoin.it/wiki/Transaction_Malleability) --- Bitcoin Wiki"
|
||||
- "[BIP62: dealing with malleability](https://github.com/bitcoin/bips/blob/master/bip-0062.mediawiki) --- Bitcoin Improvement Proposals"
|
||||
|
||||
---
|
||||
|
|
@ -1,29 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Master Chain Code And Private Key
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
In HD wallets, the master chain code and master private key are
|
||||
the two pieces of data derived from the root seed.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Master chain code
|
||||
- Master private key
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- master chain codes
|
||||
- master private keys
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Master chain code](/en/developer-guide#term-master-chain-code) --- Bitcoin.org Developer Guide"
|
||||
- "[Master private key](/en/developer-guide#term-master-private-key) --- Bitcoin.org Developer Guide"
|
||||
- "[BIP32: hierarchical deterministic wallets](https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki) --- Bitcoin Improvement Proposals"
|
||||
|
||||
---
|
||||
|
|
@ -1,27 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Merkle Block
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
A partial merkle tree connecting transactions matching a bloom
|
||||
filter to the merkle root of a block.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Merkle block
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- merkle blocks
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- MerkleBlock message (a P2P protocol message that transmits a merkle block)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Merkle block](/en/developer-reference#merkleblock) --- Bitcoin.org Developer Reference"
|
||||
- "[MerkleBlock P2P protocol message](https://en.bitcoin.it/wiki/Protocol_documentation#filterload.2C_filteradd.2C_filterclear.2C_merkleblock) --- Bitcoin Wiki"
|
||||
|
||||
---
|
||||
|
|
@ -1,31 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Merkle Root
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
The root node of a merkle tree, a descendant of all the hashed
|
||||
pairs in the tree. Block headers must include a valid merkle
|
||||
root descended from all transactions in that block.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Merkle root
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- merkle roots
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Merkle tree (the tree of which the merkle root is the root node)
|
||||
- Merkle block (a partial merkle branch connecting the root to one or more leaves [transactions])
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Merkle root](/en/developer-guide#term-merkle-root) --- Bitcoin.org Developer Guide"
|
||||
- "[Merkle trees](https://en.bitcoin.it/wiki/Protocol_documentation#Merkle_Trees) --- Bitcoin Wiki"
|
||||
- "[What is the merkle root?](http://bitcoin.stackexchange.com/q/10479) --- Bitcoin StackExchange"
|
||||
- "[Merkle tree](https://en.wikipedia.org/wiki/Merkle_tree) --- Wikipedia"
|
||||
|
||||
---
|
||||
|
|
@ -1,32 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Merkle Tree
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
A tree constructed by hashing paired data (the leaves), then
|
||||
pairing and hashing the results until a single hash remains, the
|
||||
merkle root. In Bitcoin, the leaves are almost always
|
||||
transactions from a single block.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Merkle tree
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- merkle trees
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Partial merkle branch (a branch connecting one or more leaves to the root)
|
||||
- Merkle block (a partial merkle branch connecting one or more transactions from a single block to the block merkle root)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Merkle tree](/en/developer-guide#term-merkle-tree) --- Bitcoin.org Developer Guide"
|
||||
- "[Merkle trees](https://en.bitcoin.it/wiki/Protocol_documentation#Merkle_Trees) --- Bitcoin Wiki"
|
||||
- "[How do I implement a merkle tree?](http://bitcoin.stackexchange.com/q/1110) --- Bitcoin StackExchange"
|
||||
- "[Merkle tree](https://en.wikipedia.org/wiki/Merkle_tree) --- Wikipedia"
|
||||
|
||||
---
|
||||
|
|
@ -1,27 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Message Header
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
The four header fields prefixed to all messages on the Bitcoin
|
||||
P2P network.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Message header
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- message headers
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Message headers](/en/developer-reference#message-headers) --- Bitcoin.org Developer Reference"
|
||||
- "[Message structure](https://en.bitcoin.it/wiki/Protocol_documentation#Message_structure) --- Bitcoin Wiki"
|
||||
- "[What is the function of the payload checksum in message headers?](http://bitcoin.stackexchange.com/q/22882) --- Bitcoin StackExchange"
|
||||
|
||||
---
|
||||
|
|
@ -1,32 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Minimum Relay Fee
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
The minimum transaction fee a transaction must pay (if it isn't
|
||||
a high-priority transaction) for a full node to relay that
|
||||
transaction to other nodes. There is no one minimum relay
|
||||
fee---each node chooses its own policy.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Minimum relay fee
|
||||
- Relay fee
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- minimum relay fees
|
||||
- relay fees
|
||||
- minimum fee
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Transaction fee (the minimum relay fee is a policy setting that filters out transactions with too-low transaction fees)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Minimum relay fee](/en/developer-guide#term-minimum-fee) --- Bitcoin.org Developer Guide"
|
||||
- "[Transaction fees](https://en.bitcoin.it/wiki/Transaction_fees) --- Bitcoin Wiki"
|
||||
|
||||
---
|
||||
|
|
@ -1,32 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Mining, Miner
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
Mining is the act of creating valid Bitcoin blocks, which
|
||||
requires demonstrating proof of work, and miners are devices
|
||||
that mine or people who own those devices.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Mining
|
||||
- Miner
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- mine
|
||||
- miners
|
||||
- mining
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Mining](/en/developer-guide#term-miner) --- Bitcoin.org Developer Guide"
|
||||
- "[Mining](https://en.bitcoin.it/wiki/Mining) --- Bitcoin Wiki"
|
||||
- "[What exactly is mining?](http://bitcoin.stackexchange.com/q/148) --- Bitcoin StackExchange"
|
||||
|
||||
|
||||
---
|
||||
|
|
@ -1,37 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: M-of-N Multisig, Multisig Output
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
A pubkey script that provides *n* number of pubkeys and requires
|
||||
the corresponding signature script provide *m* minimum number
|
||||
signatures corresponding to the provided pubkeys.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Multisig
|
||||
- Bare multisig
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- m-of-n
|
||||
- m-of-n multisig
|
||||
- multisig output
|
||||
- multisignature
|
||||
- multisignatures
|
||||
- multisigs
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- P2SH multisig (a multisig script contained inside P2SH)
|
||||
- Advanced scripts that require multiple signatures without using OP_CHECKMULTISIG or OP_CHECKMULTISIGVERIFY
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Multisig](/en/developer-guide#term-multisig) --- Bitcoin.org Developer Guide"
|
||||
- "[BIP11: m-of-n standard transactions](https://github.com/bitcoin/bips/blob/master/bip-0011.mediawiki) --- Bitcoin Improvement Proposals"
|
||||
- "[What are multi-signature transactions?](http://bitcoin.stackexchange.com/q/3718) --- Bitcoin StackExchange"
|
||||
|
||||
|
||||
---
|
||||
|
|
@ -1,33 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: nBits, Target Threshold
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
The target is the threshold below which a block header hash must
|
||||
be in order for the block to valid, and nBits is the encoded
|
||||
form of the target threshold as it appears in the block header.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- nBits
|
||||
- Target
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- targets
|
||||
- target threshold
|
||||
- target thresholds
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Difficulty (a number measuring the difficulty of finding a header hash relative to the difficulty of finding a header hash with the easiest target)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Target](/en/developer-guide#term-target) --- Bitcoin.org Developer Guide"
|
||||
- "[nBits](/en/developer-reference#target-nbits) --- Bitcoin.org Developer Reference"
|
||||
- "[Target](https://en.bitcoin.it/wiki/Target) --- Bitcoin Wiki"
|
||||
- "[How is the target section of the block header calculated?](http://bitcoin.stackexchange.com/q/23912) --- Bitcoin StackExchange"
|
||||
|
||||
---
|
||||
|
|
@ -1,31 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Null Data (OP_RETURN) Transaction
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
A standard transaction type which allows adding 40 bytes of
|
||||
arbitrary data to the block chain up to once per transaction.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Null data transaction
|
||||
- OP_RETURN transaction
|
||||
- Data carrier transaction
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- null data transactions
|
||||
- op_return transactions
|
||||
- data carrier transactions
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- OP_RETURN (an op code used in one of the outputs in an OP_RETURN transaction)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Null data transaction](/en/developer-guide#term-null-data) --- Bitcoin.org Developer Guide"
|
||||
- "[Pull request implement null data transactions](https://github.com/bitcoin/bitcoin/pull/2738) --- GitHub"
|
||||
|
||||
---
|
||||
|
|
@ -1,34 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Op Code
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
Operation codes from the Bitcoin Script language which push data
|
||||
or perform functions within a pubkey script or signature script.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Op code
|
||||
- Data-pushing op code
|
||||
- Non-data-pushing op code
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- op codes
|
||||
- opcode
|
||||
- opcodes
|
||||
- data-pushing op codes
|
||||
- data-pushing opcodes
|
||||
- non-data-pushing op codes
|
||||
- non-data-pushing opcodes
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Op codes](/en/developer-reference#op-codes) --- Bitcoin.org Developer Reference"
|
||||
- "[List of op codes](https://en.bitcoin.it/wiki/Script) --- Bitcoin Wiki"
|
||||
|
||||
---
|
||||
|
|
@ -1,27 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Orphan Block
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
Blocks whose parent block has not been processed by the local node,
|
||||
so they can't be fully validated yet.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Orphan block
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- orphan blocks
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Stale block
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Orphan blocks](/en/developer-guide#orphan-blocks) --- Bitcoin.org Developer Guide"
|
||||
- "[What are orphaned and stale blocks?](http://bitcoin.stackexchange.com/q/5859) --- Bitcoin StackExchange"
|
||||
|
||||
---
|
||||
|
|
@ -1,29 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Outpoint
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
The data structure used to refer to a particular transaction
|
||||
output, consisting of a 32-byte TXID and a 4-byte output index
|
||||
number (vout).
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Outpoint
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- outpoints
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Output (an entire output from a transaction)
|
||||
- TxOut (same as output)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Outpoint](/en/developer-reference#outpoint) --- Bitcoin.org Developer Reference"
|
||||
- "[Tx message (includes outpoint description)](https://en.bitcoin.it/wiki/Protocol_documentation#tx) --- Bitcoin Wiki"
|
||||
|
||||
---
|
||||
|
|
@ -1,32 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Output, Transaction Output, TxOut
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
An output in a transaction which contains two fields: a value
|
||||
field for transferring zero or more satoshis and a pubkey script
|
||||
for indicating what conditions must be fulfilled for those
|
||||
satoshis to be further spent.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Output
|
||||
- TxOut
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- outputs
|
||||
- txouts
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Outpoint (a reference to a particular output)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Output](/en/developer-guide#term-output) --- Bitcoin.org Developer Guide"
|
||||
- "[TxOut](/en/developer-reference#txout) --- Bitcoin.org Developer Reference"
|
||||
- "[Output](https://en.bitcoin.it/wiki/Transaction#Output) --- Bitcoin Wiki"
|
||||
|
||||
---
|
||||
|
|
@ -1,35 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: P2PKH Address, Pay To PubKey Hash
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
A Bitcoin payment address comprising a hashed public key,
|
||||
allowing the spender to create a standard pubkey script that
|
||||
Pays To PubKey Hash (P2PKH).
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- P2PKH address
|
||||
- P2PKH output
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- P2PKH addresses
|
||||
- P2PKH outputs
|
||||
- P2PKH pubkey script
|
||||
- P2PKH pubkey scripts
|
||||
- pubkey hash
|
||||
- pubkey hashes
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- P2PK output (an output paying a public key directly)
|
||||
- P2SH address, P2SH output (an address comprising a hashed script, and its corresponding output)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[P2PKH](/en/developer-guide#term-p2pkh) --- Bitcoin.org Developer Guide"
|
||||
- "[P2PKH versus P2PK](http://bitcoin.stackexchange.com/a/32642) --- Bitcoin StackExchange"
|
||||
|
||||
---
|
||||
|
|
@ -1,36 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: P2SH Address, Pay To Script Hash
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
A Bitcoin payment address comprising a hashed script,
|
||||
allowing the spender to create a standard pubkey script that
|
||||
Pays To Script Hash (P2SH). The script can be almost any
|
||||
valid pubkey script.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- P2SH address
|
||||
- P2SH output
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- P2SH addresses
|
||||
- P2SH outputs
|
||||
- P2SH pubkey script
|
||||
- P2SH pubkey scripts
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- P2PK output (an output paying a public key directly)
|
||||
- P2PKH address, P2PKH output (an address comprising a hashed pubkey, and its corresponding output)
|
||||
- P2SH multisig (a particular instance of P2SH where the script uses a multisig op code)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[P2SH](/en/developer-guide#term-p2sh) --- Bitcoin.org Developer Guide"
|
||||
- "[BIP16: pay to script hash](https://github.com/bitcoin/bips/blob/master/bip-0016.mediawiki) --- Bitcoin Improvement Proposals"
|
||||
- "[P2SH](https://en.bitcoin.it/wiki/P2SH) --- Bitcoin Wiki"
|
||||
|
||||
---
|
||||
|
|
@ -1,36 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: P2SH Multisig, P2SH Multisig Output
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
A P2SH output where the redeem script uses one of the multisig
|
||||
op codes. Up until Bitcoin Core 0.10.0, P2SH multisig scripts
|
||||
were standard transactions, but most other P2SH scripts were
|
||||
not.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- P2SH multisig
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- P2SH multisig script
|
||||
- P2SH multisig output
|
||||
- P2Sh multisig scripts
|
||||
- P2SH multisig outputs
|
||||
- P2SH multisig redeem script
|
||||
- P2SH multisig redeem scripts
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Multisig pubkey scripts (also called "bare multisig", these multisig scripts don't use P2SH encapsulation)
|
||||
- P2SH (general P2SH, of which P2SH multisig is a specific instance that was special cased up until Bitcoin Core 0.10.0)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[P2SH multisig](/en/developer-guide#term-p2sh-multisig) --- Bitcoin.org Developer Guide"
|
||||
- "[BIP16: pay to script hash](https://github.com/bitcoin/bips/blob/master/bip-0016.mediawiki) --- Bitcoin Improvement Proposals"
|
||||
- "[What are the limits of bare multisig and P2SH multisig?](http://bitcoin.stackexchange.com/q/23893) --- Bitcoin StackExchange"
|
||||
|
||||
---
|
||||
|
|
@ -1,38 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Parent Key, HD Wallet Parent Key
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
In HD wallets, a key used to derive child keys. The key can be
|
||||
either a private key or a public key, and the key derivation may
|
||||
also require a chain code.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Parent key
|
||||
- Parent public key
|
||||
- Parent private key
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- Parent keys
|
||||
- Parent public keys
|
||||
- Parent private keys
|
||||
|
||||
- HD wallet Parent key
|
||||
- HD wallet Parent keys
|
||||
|
||||
- Parent private and public keys
|
||||
- Parent public and private keys
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Public key (derived from a private key, not a parent key)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Parent key](/en/developer-guide#term-parent-key) --- Bitcoin.org Developer Guide"
|
||||
- "[BIP32: hierarchical deterministic wallets](https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki) --- Bitcoin Improvement Proposals"
|
||||
|
||||
---
|
||||
|
|
@ -1,29 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Payment Protocol, Payment Request, BIP70
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
The protocol defined in BIP70 (and other BIPs) which lets
|
||||
spenders get signed payment details from receivers.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Payment protocol
|
||||
- Payment request
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- payment protocols
|
||||
- payment requests
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- IP-to-IP payment protocol (an insecure, discontinued protocol included in early versions of Bitcoin)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Payment Protocol](/en/developer-guide#term-payment-protocol) --- Bitcoin.org Developer Guide"
|
||||
- "[BIP70: payment protocol](https://github.com/bitcoin/bips/blob/master/bip-0070.mediawiki) --- Bitcoin Improvement Proposals"
|
||||
|
||||
---
|
||||
|
|
@ -1,31 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Private Key, ECDSA Private Key
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
The private portion of a keypair which can create signatures
|
||||
that other people can verify using the public key.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Private key
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- private keys
|
||||
- ecdsa private key
|
||||
- secp256k1 private key
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Public key (data derived from the private key)
|
||||
- Parent key (a key used to create child keys, not necessarily a private key)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Private key](/en/developer-guide#term-private-key) --- Bitcoin.org Developer Guide"
|
||||
- "[Private key](https://en.bitcoin.it/wiki/Private_key) --- Bitcoin Wiki"
|
||||
- "[What is a private key?](http://bitcoin.stackexchange.com/q/4675) --- Bitcoin StackExchange"
|
||||
|
||||
---
|
||||
|
|
@ -1,27 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Proof Of Work
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
A hash below a target value which can only be obtained, on
|
||||
average, by performing a certain amount of brute force
|
||||
work---therefore demonstrating proof of work.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Proof of work
|
||||
- POW
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Proof of work](/en/developer-guide#term-proof-of-work) --- Bitcoin.org Developer Guide"
|
||||
- "[Proof of work](https://en.bitcoin.it/wiki/Proof_of_work) --- Bitcoin Wiki"
|
||||
|
||||
---
|
||||
|
|
@ -1,31 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Pubkey Script, ScriptPubKey
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
A script included in outputs which sets the conditions that must
|
||||
be fulfilled for those satoshis to be spent. Data for
|
||||
fulfilling the conditions can be provided in a signature script.
|
||||
Called a scriptPubKey in code.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Pubkey script
|
||||
- ScriptPubKey
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- pubkey scripts
|
||||
- scriptpubkeys
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Pubkey (a public key, which can be used as part of a pubkey script but don't provide a programmable authentication mechanism)
|
||||
- Signature script (a script that provides data to the pubkey script)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Pubkey script](/en/developer-guide#term-pubkey-script) --- Bitcoin.org Developer Guide"
|
||||
|
||||
---
|
||||
|
|
@ -1,33 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Public Key, ECDSA Public Key
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
The public portion of a keypair which can be used to verify
|
||||
signatures made with the private portion of the keypair.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Public key
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- public keys
|
||||
- ecdsa public key
|
||||
- ecdsa public keys
|
||||
- secp256k1 public key
|
||||
- pubkey
|
||||
- pubkeys
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Private key (data from which the public key is derived)
|
||||
- Parent key (a key used to create child keys, not necessarily a public key)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Public key](/en/developer-guide#term-public-key) --- Bitcoin.org Developer Guide"
|
||||
- "[What is a public key?](http://bitcoin.stackexchange.com/q/4675) --- Bitcoin StackExchange"
|
||||
|
||||
---
|
||||
|
|
@ -1,33 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Redeem Script, RedeemScript
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
A script similar in function to a pubkey script. One copy of it
|
||||
is hashed to create a P2SH address (used in an actual pubkey
|
||||
script) and another copy is placed in the spending signature
|
||||
script to enforce its conditions.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Redeem script
|
||||
- RedeemScript
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- redeem scripts
|
||||
- redeemscripts
|
||||
- script hash
|
||||
- script hashes
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Signature script (a script that provides data to the pubkey script, which includes the redeem script in a P2SH input)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Redeem script](/en/developer-guide#term-redeem-script) --- Bitcoin.org Developer Guide"
|
||||
- "[BIP16: pay to script hash](https://github.com/bitcoin/bips/blob/master/bip-0016.mediawiki) --- Bitcoin Improvement Proposals"
|
||||
|
||||
---
|
||||
|
|
@ -1,31 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Regtest, Regression Test Mode
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
A local testing environment in which developers can almost
|
||||
instantly generate blocks on demand for testing events, and can
|
||||
create private satoshis with no real-world value.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Regtest
|
||||
- Regression test mode
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- regtests
|
||||
- regression test modes
|
||||
- regtest mode
|
||||
- regtest modes
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Testnet (a global testing environment which mostly mimics mainnet)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Regtest mode](/en/developer-examples#regtest-mode) --- Bitcoin.org Developer Examples"
|
||||
|
||||
---
|
||||
|
|
@ -1,27 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: RPC Byte Order
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
A hash digest displayed with the byte order reversed; used in
|
||||
Bitcoin Core RPCs, many block explorers, and other software.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- RPC byte order
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- RPC byte orders
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Internal byte order (hash digests displayed in their typical order; used in serialized blocks and serialized transactions)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[RPC byte order](/en/developer-reference#hash-byte-order) --- Bitcoin.org Developer Reference"
|
||||
- "[Block hashing algorithm ('endian conversion')](https://en.bitcoin.it/wiki/Block_hashing_algorithm) --- Bitcoin Wiki"
|
||||
|
||||
---
|
||||
|
|
@ -1,31 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Sequence Number (Transactions)
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
Part of all transactions. A number intended to allow unconfirmed
|
||||
time-locked transactions to be updated before being finalized;
|
||||
not currently used except to disable locktime in a transaction
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Sequence number
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- sequence numbers
|
||||
- transaction sequence number
|
||||
- transaction sequence numbers
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Output index number / vout (this is the 0-indexed number of an output within a transaction used by a later transaction to refer to that specific output)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Sequence number](/en/developer-guide#term-sequence-number) --- Bitcoin.org Developer Guide"
|
||||
- "[Tx message (describes sequence number)](https://en.bitcoin.it/wiki/Protocol_documentation#tx) --- Bitcoin Wiki"
|
||||
- "[What is the sequence number?](http://bitcoin.stackexchange.com/q/2025) --- Bitcoin StackExchange"
|
||||
|
||||
---
|
||||
|
|
@ -1,30 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Serialized Block, Raw Block
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
A complete block in its binary format---the same format used to
|
||||
calculate total block byte size; often represented using
|
||||
hexadecimal.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Serialized block
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- serialized blocks
|
||||
- raw blocks
|
||||
- raw format block
|
||||
- raw format blocks
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Serialized blocks](/en/developer-reference#serialized-blocks) --- Bitcoin.org Developer Reference"
|
||||
- "[Block message (serialized block)](https://en.bitcoin.it/wiki/Protocol_documentation#block) --- Bitcoin Wiki"
|
||||
|
||||
---
|
||||
|
|
@ -1,32 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Serialized Transaction, Raw Transaction
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
Complete transactions in their binary format; often represented
|
||||
using hexadecimal. Sometimes called raw format because of the
|
||||
various Bitcoin Core commands with "raw" in their names.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Serialized transaction
|
||||
- Raw transaction
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- serialized transactions
|
||||
- raw transactions
|
||||
- raw format transaction
|
||||
- raw format transactions
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Serialized transactions](/en/developer-reference#term-raw-format) --- Bitcoin.org Developer Guide"
|
||||
- "[Tx message (serialized transaction)](https://en.bitcoin.it/wiki/Protocol_documentation#tx) --- Bitcoin Wiki"
|
||||
- "[Transaction](https://en.bitcoin.it/wiki/Transaction) --- Bitconi Wiki"
|
||||
|
||||
---
|
||||
|
|
@ -1,28 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: SIGHASH_ALL
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
Default signature hash type which signs the entire transaction
|
||||
except any signature scripts, preventing modification of the
|
||||
signed parts.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- SIGHASH_ALL
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- "`SIGHASH_ALL`"
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[`SIGHASH_ALL`](/en/developer-guide#term-sighash-all) --- Bitcoin.org Developer Guide"
|
||||
- "[OP_CHECKSIG](https://en.bitcoin.it/wiki/OP_CHECKSIG) --- Bitcoin Wiki"
|
||||
- "[Contracts](https://en.bitcoin.it/wiki/Contracts#Theory) --- Bitcoin Wiki"
|
||||
|
||||
---
|
||||
|
|
@ -1,47 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: SIGHASH_ANYONECANPAY
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
A signature hash type which modifies the behavior of other signature hash types
|
||||
to allow signing only the current input.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- SIGHASH_ANYONECANPAY
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- anyonecanpay
|
||||
- "`SIGHASH_ANYONECANPAY`"
|
||||
|
||||
- "sighash_all|anyonecanpay"
|
||||
- "`sighash_all|anyonecanpay`"
|
||||
|
||||
- "sighash_all|sighash_anyonecanpay"
|
||||
- "`sighash_all|sighash_anyonecanpay`"
|
||||
|
||||
- "sighash_none|anyonecanpay"
|
||||
- "`sighash_none|anyonecanpay`"
|
||||
|
||||
- "sighash_none|sighash_anyonecanpay"
|
||||
- "`sighash_none|sighash_anyonecanpay`"
|
||||
|
||||
- "sighash_single|anyonecanpay"
|
||||
- "`sighash_single|anyonecanpay`"
|
||||
|
||||
- "sighash_single|sighash_anyonecanpay"
|
||||
- "`sighash_single|sighash_anyonecanpay`"
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- SIGHASH_SINGLE (which signs only a single input, like SIGHASH_ANYONECANPAY, but also signs a single output)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[SIGHASH_ANYONECANPAY](/en/developer-guide#term-sighash-anyonecanpay) --- Bitcoin.org Developer Guide"
|
||||
- "[OP_CHECKSIG](https://en.bitcoin.it/wiki/OP_CHECKSIG) --- Bitcoin Wiki"
|
||||
- "[Contracts](https://en.bitcoin.it/wiki/Contracts#Theory) --- Bitcoin Wiki"
|
||||
|
||||
---
|
||||
|
|
@ -1,27 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: SIGHASH_NONE
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
Signature hash type which only signs the inputs, allowing anyone
|
||||
to change the outputs however they'd like.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- SIGHASH_NONE
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- "`SIGHASH_NONE`"
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[`SIGHASH_NONE`](/en/developer-guide#term-sighash-none) --- Bitcoin.org Developer Guide"
|
||||
- "[OP_CHECKSIG](https://en.bitcoin.it/wiki/OP_CHECKSIG) --- Bitcoin Wiki"
|
||||
- "[Contracts](https://en.bitcoin.it/wiki/Contracts#Theory) --- Bitcoin Wiki"
|
||||
|
||||
---
|
||||
|
|
@ -1,29 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: SIGHASH_SINGLE
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
Signature hash type which only signs its input and the output
|
||||
with the same index value, allowing modification of other inputs
|
||||
and outputs.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- SIGHASH_SINGLE
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- "`SIGHASH_SINGLE`"
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- SIGHASH_ANYONECANPAY (a flag to signature hash types that only signs a single input, like SIGHASH_SINGLE, but which doesn't sign any outputs.)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[`SIGHASH_SINGLE`](/en/developer-guide#term-sighash-single) --- Bitcoin.org Developer Guide"
|
||||
- "[OP_CHECKSIG](https://en.bitcoin.it/wiki/OP_CHECKSIG) --- Bitcoin Wiki"
|
||||
- "[Contracts](https://en.bitcoin.it/wiki/Contracts#Theory) --- Bitcoin Wiki"
|
||||
|
||||
---
|
||||
|
|
@ -1,34 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Signature Hash
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
A flag to Bitcoin signatures that indicates what parts of the
|
||||
transaction the signature signs. (The default is SIGHASH_ALL.)
|
||||
The unsigned parts of the transaction may be modified.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Signature hash
|
||||
- Sighash
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- sighash flag
|
||||
- signature hashes
|
||||
- sighashes
|
||||
- sighash flags
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Signed hash (a hash of the data to be signed)
|
||||
- Transaction malleability / transaction mutability (although non-default sighash flags do allow optional malleability, malleability comprises any way a transaction may be mutated)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Signature hash](/en/developer-guide#term-signature-hash) --- Bitcoin.org Developer Guide"
|
||||
- "[OP_CHECKSIG](https://en.bitcoin.it/wiki/OP_CHECKSIG) --- Bitcoin Wiki"
|
||||
- "[Contracts](https://en.bitcoin.it/wiki/Contracts#Theory) --- Bitcoin Wiki"
|
||||
|
||||
---
|
||||
|
|
@ -1,29 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Signature Script, ScriptSig
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
Data generated by a spender which is almost always used as
|
||||
variables to satisfy a pubkey script. Called a scriptSig in
|
||||
code.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Signature script
|
||||
- ScriptSig
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- signature scripts
|
||||
- scriptSigs
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- ECDSA signature (a signature, which can be used as part of a pubkey script in addition to other data)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Signature script](/en/developer-guide#term-signature-script) --- Bitcoin.org Developer Guide"
|
||||
|
||||
---
|
||||
|
|
@ -1,32 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Signature, ECDSA Signature
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
A value related to a public key which could only have reasonably
|
||||
been created by someone who has the private key that created
|
||||
that public key. Used in Bitcoin to authorize spending satoshis
|
||||
previously sent to a public key.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Signature
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- signatures
|
||||
- ecdsa signature
|
||||
- ecdsa signatures
|
||||
- secp256k1 signature
|
||||
- secp256k1 signatures
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Signature](/en/developer-guide#term-signature) --- Bitcoin.org Developer Guide"
|
||||
- "[ECDSA](https://en.bitcoin.it/wiki/Elliptic_Curve_Digital_Signature_Algorithm) --- Bitcoin Wiki"
|
||||
- "[ECDSA](https://en.wikipedia.org/wiki/Elliptic_Curve_DSA) --- Wikipedia"
|
||||
---
|
||||
|
|
@ -1,36 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: SPV, Simplified Payment Verification
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
A method for verifying particular transactions were included
|
||||
in a block without downloading the entire block. The method is
|
||||
used by some lightweight Bitcoin clients.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- SPV
|
||||
- Simplified Payment Verification
|
||||
- Lightweight client
|
||||
- Thin client
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- lightweight clients
|
||||
- thin clients
|
||||
- spv client
|
||||
- spv clients
|
||||
- spv node
|
||||
- spv nodes
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[SPV](/en/developer-guide#simplified-payment-verification-spv) --- Bitcoin.org Developer Guide"
|
||||
- "[Thin client security](https://en.bitcoin.it/wiki/Thin_Client_Security) --- Bitcoin Wiki"
|
||||
- "[What is a thin client?](http://bitcoin.stackexchange.com/questions/32529) --- Bitcoin StackExchange"
|
||||
|
||||
---
|
||||
|
|
@ -1,34 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Soft Fork, Soft-Forking Change
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
A temporary fork in the block chain which commonly occurs when
|
||||
miners using non-upgraded nodes violate a new consensus rule
|
||||
their nodes don't know about.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Soft fork
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- soft forks
|
||||
- soft-forking change
|
||||
- soft-forking
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Fork (a regular fork where all nodes follow the same consensus rules, so the fork is resolved once one chain has more proof of work than another)
|
||||
- Hard fork (a permanent divergence in the block chain caused by non-upgraded nodes not following new consensus rules)
|
||||
- Software fork (when one or more developers permanently develops a codebase separately from other developers)
|
||||
- Git fork (when one or more developers temporarily develops a codebase separately from other developers
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Soft fork](/en/developer-guide#term-soft-fork) --- Bitcoin.org Developer Guide"
|
||||
- "[Soft fork](https://en.bitcoin.it/wiki/Softfork) --- Bitcoin Wiki"
|
||||
- "[What is a soft fork?](http://bitcoin.stackexchange.com/questions/30817) --- Bitcoin StackExchange"
|
||||
|
||||
---
|
||||
|
|
@ -1,28 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Stale Block
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
Blocks which were successfully mined but which aren't included
|
||||
on the current best block chain, likely because some other block
|
||||
at the same height had its chain extended first.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Stale block
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- stale blocks
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Orphan block (a block whose previous (parent) hash field points to an unknown block, meaning the orphan can't be validated)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Stale blocks](/en/developer-guide#term-stale-block) --- Bitcoin.org Developer Guide"
|
||||
- "[What are orphaned and stale blocks?](http://bitcoin.stackexchange.com/q/5859) --- Bitcoin StackExchange"
|
||||
|
||||
---
|
||||
|
|
@ -1,27 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Standard Transaction
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
A transaction that passes Bitcoin Core's IsStandard() and
|
||||
IsStandardTx() tests. Only standard transactions are mined or
|
||||
broadcast by peers running the default Bitcoin Core software.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Standard Transaction
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- standard transactions
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Standard transactions](/en/developer-guide#standard-transactions) --- Bitcoin.org Developer Guide"
|
||||
- "[Will general non-standard transactions ever be allowed?](http://bitcoin.stackexchange.com/q/5664) --- Bitcoin StackExchange"
|
||||
|
||||
---
|
||||
|
|
@ -1,28 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Start String, Network Magic
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
Four defined bytes which start every message in the Bitcoin P2P
|
||||
protocol to allow seeking to the next message.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Start string
|
||||
- Network magic
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- start strings
|
||||
- magic
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Start string](/en/developer-reference#term-start-string) --- Bitcoin.org Developer Reference"
|
||||
- "[How was the start string chosen?](http://bitcoin.stackexchange.com/q/2337) --- Bitcoin StackExchange"
|
||||
|
||||
---
|
||||
|
|
@ -1,32 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Testnet, Testing Network
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
A global testing environment in which developers can obtain and
|
||||
spend satoshis that have no real-world value on a network that
|
||||
is very similar to the Bitcoin mainnet.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Testnet
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- testnets
|
||||
- testnet mode
|
||||
- testnet modes
|
||||
- testing network
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Regtest (a local testing environment where developers can control block generation)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Testnet mode](/en/developer-examples#testnet) --- Bitcoin.org Developer Examples"
|
||||
- "[Testnet](https://en.bitcoin.it/wiki/Testnet) --- Bitcoin Wiki"
|
||||
- "[Get testnet bitcoins][Piotr Piasecki's testnet faucet] --- Testnet Faucet"
|
||||
|
||||
---
|
||||
|
|
@ -1,34 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Transaction Fee, Miner Fee
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
The amount remaining when the value of all outputs in a
|
||||
transaction are subtracted from all inputs in a transaction;
|
||||
the fee is paid to the miner who includes that transaction
|
||||
in a block.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Transaction fee
|
||||
- Miners fee
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- transaction fees
|
||||
- miners fees
|
||||
- tx fee
|
||||
- tx fees
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Minimum relay fee (the lowest fee a transaction must pay to be accepted into the memory pool and relayed by Bitcoin Core nodes)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Transaction fee](/en/developer-guide#term-transaction-fee) --- Bitcoin.org Developer Guide"
|
||||
- "[Transaction fees](https://en.bitcoin.it/wiki/Transaction_fees) --- Bitcoin Wiki"
|
||||
- "[How to calculate transaction fees before sending?](http://bitcoin.stackexchange.com/q/1195) --- Bitcoin StackExchange"
|
||||
|
||||
---
|
||||
|
|
@ -1,29 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Txid, Transaction Identifier
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
An identifier used to uniquely identify a particular
|
||||
transaction; specifically, the sha256d hash of the transaction.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Txid
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- txids
|
||||
- transaction identifier
|
||||
- transaction identifiers
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Outpoint (the combination of a txid with a vout used to identify a specific output)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Txid](/en/developer-guide#term-txid) --- Bitcoin.org Developer Guide"
|
||||
- "[How do I calculate the txid of this raw transaction?](http://bitcoin.stackexchange.com/q/32765) --- Bitcoin StackExchange"
|
||||
|
||||
---
|
||||
|
|
@ -1,27 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Unspent Transaction Output, UTXO
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
An Unspent Transaction Output (UTXO) that can be spent as an
|
||||
input in a new transaction.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- UTXO
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- utxos
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Output (any output, whether spent or not. Outputs are a superset of UTXOs)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[UTXO](/en/developer-guide#term-utxo) --- Bitcoin.org Developer Guide"
|
||||
- "[How big is the UTXO database?](http://bitcoin.stackexchange.com/q/35980) --- Bitcoin StackExchange"
|
||||
|
||||
---
|
||||
|
|
@ -1,29 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Wallet Import Format
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
A data interchange format designed to allow exporting and
|
||||
importing a single private key with a flag indicating whether or
|
||||
not it uses a compressed public key.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- WIF
|
||||
- Wallet Import Format
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- Extended private keys (which allow importing a hierarchy of private keys)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Wallet import format](/en/developer-guide#term-wallet-import-format) --- Bitcoin.org Developer Guide"
|
||||
- "[Wallet import format](https://en.bitcoin.it/wiki/Wallet_import_format) --- Bitcoin Wiki"
|
||||
- "[What is the role of wallet import format?](http://bitcoin.stackexchange.com/q/35723) --- Bitcoin StackExchange"
|
||||
|
||||
---
|
||||
|
|
@ -1,31 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Wallet
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
Software that stores private keys and monitors the block chain
|
||||
(sometimes as a client of a server that does the processing) to
|
||||
allow users to spend and receive satoshis.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Wallet
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- wallets
|
||||
- web wallet
|
||||
- web wallets
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
- HD wallet (a protocol that allows all of a wallet's keys to be created from a single seed)
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Wallets](/en/developer-guide#wallets) --- Bitcoin.org Developer Guide"
|
||||
- "[Wallet](https://en.bitcoin.it/wiki/Wallet) --- Bitcoin Wiki"
|
||||
- "[Where are the user's bitcoins actually stored?](http://bitcoin.stackexchange.com/q/1600) --- Bitcoin StackExchange"
|
||||
|
||||
---
|
||||
|
|
@ -1,28 +0,0 @@
|
|||
---
|
||||
# This file is licensed under the MIT License (MIT) available on
|
||||
# http://opensource.org/licenses/MIT.
|
||||
|
||||
required:
|
||||
#-------------40 characters-------------#
|
||||
title_max_40_characters_no_formatting: Watch-Only Address
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
An address or pubkey script stored in the wallet without the
|
||||
corresponding private key, allowing the wallet to watch for
|
||||
outputs but not spend them.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Watch-only address
|
||||
|
||||
optional:
|
||||
synonyms_and_pluralizations_not_shown_in_glossary:
|
||||
- watch-only addresses
|
||||
- watch-only
|
||||
|
||||
not_to_be_confused_with_capitalize_first_letter:
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[`importaddress` RPC](/en/developer-reference#importaddress) --- Bitcoin.org Developer Reference"
|
||||
- "[Pull request adding watch-only support to Bitcoin Core](https://github.com/bitcoin/bitcoin/pull/4045) --- GitHub"
|
||||
|
||||
---
|
||||
|
|
@ -20,7 +20,7 @@ test their applications with reduced risks and limitations.
|
|||
{% autocrossref %}
|
||||
|
||||
When run with no arguments, all Bitcoin Core programs default to Bitcoin's main
|
||||
network ([mainnet][/en/glossary/mainnet]{:#term-mainnet}{:.term}). However, for development,
|
||||
network ([mainnet][mainnet]{:#term-mainnet}{:.term}). However, for development,
|
||||
it's safer and cheaper to use Bitcoin's test network (testnet)
|
||||
where the satoshis spent have no real-world value. Testnet also relaxes some
|
||||
restrictions (such as standard transaction checks) so you can test functions
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ of data to create transactions with the same attributes as those
|
|||
described below.
|
||||
|
||||
In order to use this tutorial, you will need to setup [Bitcoin Core][core executable]
|
||||
and create a regression test mode environment with 50 BTC in your test
|
||||
and create a [regression test mode][] environment with 50 BTC in your test
|
||||
wallet.
|
||||
|
||||
{% endautocrossref %}
|
||||
|
|
@ -915,7 +915,7 @@ way to reference the underlying full (unhashed) public keys it knows
|
|||
about, so we get the three new addresses above in order to use their
|
||||
public keys.
|
||||
|
||||
Recall from the Guide that the hashed public keys used in addresses
|
||||
[Recall from the Guide][address] that the hashed public keys used in addresses
|
||||
obfuscate the full public key, so you cannot give an address to another
|
||||
person or device as part of creating a typical multisig output or P2SH multisig
|
||||
redeem script. You must give them a full public key.
|
||||
|
|
|
|||
|
|
@ -16,9 +16,9 @@ and modification of previous transaction records.
|
|||
Each full node in the Bitcoin network independently stores a block chain
|
||||
containing only blocks validated by that node. When several nodes all
|
||||
have the same blocks in their block chain, they are considered to be in
|
||||
[consensus][/en/glossary/consensus]{:#term-consensus}{:.term}. The validation rules these
|
||||
[consensus][]{:#term-consensus}{:.term}. The validation rules these
|
||||
nodes follow to maintain consensus are called [consensus
|
||||
rules][/en/glossary/consensus-rules]{:#term-consensus-rules}{:.term}. This section describes many of
|
||||
rules][]{:#term-consensus-rules}{:.term}. This section describes many of
|
||||
the consensus rules used by Bitcoin Core.
|
||||
|
||||
{% endautocrossref %}
|
||||
|
|
@ -31,11 +31,11 @@ the consensus rules used by Bitcoin Core.
|
|||
|
||||
|
||||
The illustration above shows a simplified version of a block chain.
|
||||
A [block][/en/glossary/block]{:#term-block}{:.term} of one or more new transactions
|
||||
A [block][]{:#term-block}{:.term} of one or more new transactions
|
||||
is collected into the transaction data part of a block.
|
||||
Copies of each transaction are hashed, and the hashes are then paired,
|
||||
hashed, paired again, and hashed again until a single hash remains, the
|
||||
[merkle root][/en/glossary/merkle-root]{:#term-merkle-root}{:.term} of a merkle tree.
|
||||
[merkle root][]{:#term-merkle-root}{:.term} of a merkle tree.
|
||||
|
||||
The merkle root is stored in the block header. Each block also
|
||||
stores the hash of the previous block's header, chaining the blocks
|
||||
|
|
@ -57,20 +57,20 @@ a particular transaction can only be used as an input once in the
|
|||
block chain. Any subsequent reference is a forbidden double
|
||||
spend---an attempt to spend the same satoshis twice.
|
||||
|
||||
Outputs are tied to [transaction identifiers (TXIDs)][/en/glossary/txid]{:#term-txid}{:.term}, which are the hashes
|
||||
Outputs are tied to [transaction identifiers (TXIDs)][txid]{:#term-txid}{:.term}, which are the hashes
|
||||
of signed transactions.
|
||||
|
||||
Because each output of a particular transaction can only be spent once,
|
||||
the outputs of all transactions included in the block chain can be categorized as either
|
||||
[Unspent Transaction Outputs (UTXOs)][/en/glossary/unspent-transaction-output]{:#term-utxo}{:.term} or spent transaction outputs. For a
|
||||
[Unspent Transaction Outputs (UTXOs)][utxo]{:#term-utxo}{:.term} or spent transaction outputs. For a
|
||||
payment to be valid, it must only use UTXOs as inputs.
|
||||
|
||||
Ignoring coinbase transactions (described later), if the value of a
|
||||
transaction's outputs exceed its inputs, the transaction will be
|
||||
rejected---but if the inputs exceed the value of the outputs, any
|
||||
difference in value may be claimed as a [transaction
|
||||
fee][/en/glossary/transaction-fee]{:#term-transaction-fee}{:.term} by the Bitcoin
|
||||
[miner][/en/glossary/mining]{:#term-miner}{:.term} who creates the block containing that
|
||||
fee][]{:#term-transaction-fee}{:.term} by the Bitcoin
|
||||
[miner][]{:#term-miner}{:.term} who creates the block containing that
|
||||
transaction.
|
||||
For example, in the illustration above, each transaction spends 10,000 satoshis
|
||||
fewer than it receives from its combined inputs, effectively paying a 10,000
|
||||
|
|
@ -94,7 +94,7 @@ in any block without modifying all following blocks. As a
|
|||
result, the cost to modify a particular block increases with every new block
|
||||
added to the block chain, magnifying the effect of the proof of work.
|
||||
|
||||
The [proof of work][/en/glossary/proof-of-work]{:#term-proof-of-work}{:.term} used in Bitcoin
|
||||
The [proof of work][]{:#term-proof-of-work}{:.term} used in Bitcoin
|
||||
takes advantage of the apparently random nature of cryptographic hashes.
|
||||
A good cryptographic hash algorithm converts arbitrary data into a
|
||||
seemingly-random number. If the data is modified in any way and
|
||||
|
|
@ -110,12 +110,12 @@ class="math">2<sup>255</sup></span>.
|
|||
|
||||
In the example given above, you will produce a successful hash on average every other try.
|
||||
You can even estimate the probability
|
||||
that a given hash attempt will generate a number below the [target][/en/glossary/nbits]{:#term-target}{:.term}
|
||||
that a given hash attempt will generate a number below the [target][]{:#term-target}{:.term}
|
||||
threshold.
|
||||
Bitcoin assumes a linear probability that the lower it makes the target threshold, the more hash attempts (on average) will need to be tried.
|
||||
|
||||
New blocks will only be added to the block chain if their hash is at
|
||||
least as challenging as a [difficulty][/en/glossary/difficulty]{:#term-difficulty}{:.term} value expected by the consensus protocol.
|
||||
least as challenging as a [difficulty][]{:#term-difficulty}{:.term} value expected by the consensus protocol.
|
||||
Every 2,016 blocks, the network uses timestamps stored in each
|
||||
block header to calculate the number of seconds elapsed between generation
|
||||
of the first and last of those last 2,016 blocks. The ideal value is
|
||||
|
|
@ -140,7 +140,7 @@ preceded it, it requires (on average) as much hashing power to
|
|||
propagate a modified block as the entire Bitcoin network expended
|
||||
between the time the original block was created and the present time.
|
||||
Only if you acquired a majority of the network's hashing power
|
||||
could you reliably execute such a [51 percent attack][/en/glossary/51-percent-attack]{:#term-51-attack}{:.term} against
|
||||
could you reliably execute such a [51 percent attack][]{:#term-51-attack}{:.term} against
|
||||
transaction history (although, it should be noted, that even less than 50% of the hashing power still has a good chance of performing such attacks).
|
||||
|
||||
The block header provides several easy-to-modify fields, such as a
|
||||
|
|
@ -162,15 +162,15 @@ Any Bitcoin miner who successfully hashes a block header to a value
|
|||
below the target threshold can add the entire block to the block chain
|
||||
(assuming the block is otherwise valid).
|
||||
These blocks are commonly addressed
|
||||
by their [block height][/en/glossary/block-height]{:#term-block-height}{:.term}---the number of blocks between them and the first Bitcoin
|
||||
block (block 0, most commonly known as the [genesis block][/en/glossary/genesis-block]{:#term-genesis-block}{:.term}). For example,
|
||||
by their [block height][]{:#term-block-height}{:.term}---the number of blocks between them and the first Bitcoin
|
||||
block (block 0, most commonly known as the [genesis block]{:#term-genesis-block}{:.term}). For example,
|
||||
block 2016 is where difficulty could have first been adjusted.
|
||||
|
||||
|
||||
|
||||
Multiple blocks can all have the same block height, as is common when
|
||||
two or more miners each produce a block at roughly the same time. This
|
||||
creates an apparent [fork][/en/glossary/fork]{:#term-fork}{:.term} in the block chain, as shown in the
|
||||
creates an apparent [fork][]{:#term-fork}{:.term} in the block chain, as shown in the
|
||||
illustration above.
|
||||
|
||||
When miners produce simultaneous blocks at the end of the block chain, each
|
||||
|
|
@ -183,11 +183,11 @@ the competing simultaneously-mined blocks. This makes that side of
|
|||
the fork stronger than the other side.
|
||||
Assuming a fork only contains valid
|
||||
blocks, normal peers always follow the the most difficult chain
|
||||
to recreate and throw away [stale blocks][/en/glossary/stale-block]{:#term-stale-block}{:.term} belonging to shorter forks.
|
||||
to recreate and throw away [stale blocks][stale block]{:#term-stale-block}{:.term} belonging to shorter forks.
|
||||
(Stale blocks are also sometimes called orphans or orphan blocks<!--noref-->, but
|
||||
those terms are also used for true orphan blocks without a known parent block.)
|
||||
|
||||
Long-term forks are possible if different miners work at cross-purposes,
|
||||
[Long-term forks][long-term fork]{:#term-long-term-fork}{:.term} are possible if different miners work at cross-purposes,
|
||||
such as some miners diligently working to extend the block chain at the
|
||||
same time other miners are attempting a 51 percent attack to revise
|
||||
transaction history.
|
||||
|
|
@ -220,7 +220,7 @@ All transactions, including the coinbase transaction, are encoded into
|
|||
blocks in binary rawtransaction format.
|
||||
|
||||
The rawtransaction format is hashed to create the transaction
|
||||
identifier (txid). From these txids, the [merkle tree][/en/glossary/merkle-tree]{:#term-merkle-tree}{:.term} is constructed by pairing each
|
||||
identifier (txid). From these txids, the [merkle tree][]{:#term-merkle-tree}{:.term} is constructed by pairing each
|
||||
txid with one other txid and then hashing them together. If there are
|
||||
an odd number of txids, the txid without a partner is hashed with a
|
||||
copy of itself.
|
||||
|
|
@ -297,7 +297,7 @@ which gets block chain data from those non-upgraded nodes refuses to
|
|||
build on the same chain as mining software getting data from upgraded
|
||||
nodes. This creates permanently divergent chains---one for non-upgraded
|
||||
nodes and one for upgraded nodes---called a [hard
|
||||
fork][/en/glossary/hard-fork]{:#term-hard-fork}{:.term}.
|
||||
fork][]{:#term-hard-fork}{:.term}.
|
||||
|
||||
|
||||
|
||||
|
|
@ -307,7 +307,7 @@ majority of the hash rate. That's because, in this case, non-upgraded
|
|||
nodes will accept as valid all the same blocks as upgraded nodes, so the
|
||||
upgraded nodes can build a stronger chain that the non-upgraded nodes
|
||||
will accept as the best valid block chain. This is called a [soft
|
||||
fork][/en/glossary/soft-fork]{:#term-soft-fork}{:.term}.
|
||||
fork][]{:#term-soft-fork}{:.term}.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -42,15 +42,15 @@ merchandise, but Charlie can't get the merchandise and keep his payment.
|
|||
|
||||
This simple contract isn't much help if there's a dispute, so Bob and
|
||||
Charlie enlist the help of Alice-the-arbitrator to create an [escrow
|
||||
contract][/en/glossary/escrow-contract]{:#term-escrow-contract}{:.term}. Charlie spends his satoshis
|
||||
contract][]{:#term-escrow-contract}{:.term}. Charlie spends his satoshis
|
||||
to an output which can only be spent if two of the three people sign the
|
||||
input. Now Charlie can pay Bob if everything is ok, Bob can refund
|
||||
Charlie's money if there's a problem, or Alice can arbitrate and decide
|
||||
who should get the satoshis if there's a dispute.
|
||||
|
||||
To create a multiple-signature ([multisig][/en/glossary/multisig]{:#term-multisig}{:.term})
|
||||
To create a multiple-signature ([multisig][]{:#term-multisig}{:.term})
|
||||
output, they each give the others a public key. Then Bob creates the
|
||||
following [P2SH multisig][/en/glossary/p2sh-multisig]{:#term-p2sh-multisig}{:.term} redeem script:
|
||||
following [P2SH multisig][]{:#term-p2sh-multisig}{:.term} redeem script:
|
||||
|
||||
{% endautocrossref %}
|
||||
|
||||
|
|
|
|||
|
|
@ -37,8 +37,8 @@ IP addresses.
|
|||
|
||||
When started for the first time, programs don't know the IP
|
||||
addresses of any active full nodes. In order to discover some IP
|
||||
addresses, they query one or more DNS names (called [DNS seeds][/en/glossary/dns-seed]{:#term-dns-seed}{:.term})
|
||||
hardcoded into Bitcoin Core and
|
||||
addresses, they query one or more DNS names (called [DNS seeds][dns
|
||||
seed]{:#term-dns-seed}{:.term}) hardcoded into Bitcoin Core and
|
||||
BitcoinJ. The response to the lookup should include one or more [DNS
|
||||
A records][] with the IP addresses of full nodes that may accept new
|
||||
incoming connections. For example, using the [Unix `dig`
|
||||
|
|
@ -317,7 +317,7 @@ to the reference page for that message.
|
|||
|
||||
Bitcoin Core 0.10.0 uses an initial block download (IBD) method called
|
||||
*headers-first*. The goal is to download the headers for the best [header
|
||||
chain][/en/glossary/header-chain]{:#term-header-chain}{:.term}, partially validate them as best
|
||||
chain][]{:#term-header-chain}{:.term}, partially validate them as best
|
||||
as possible, and then download the corresponding blocks in parallel. This
|
||||
solves several problems with the older blocks-first IBD method.
|
||||
|
||||
|
|
@ -469,7 +469,7 @@ block retrieval method.)
|
|||
| **Payload** | The inventory of the new block | The inventory of the new block | One or more header hashes on the HF node's best header chain (BHC) | Up to 2,000 headers connecting HF node's BHC to relay node's BHC
|
||||
| **Message** | [`block`][block message] | [`merkleblock`][merkleblock message] | [`tx`][tx message] |
|
||||
| **From→To** | Relay→BF/HF | Relay→SPV | Relay→SPV |
|
||||
| **Payload** | The new block in [serialized format][section serialized blocks] | The new block filtered into a merkle block | Serialized transactions from the new block that match the bloom filter |
|
||||
| **Payload** | The new block in [serialized format][serialized block] | The new block filtered into a merkle block | Serialized transactions from the new block that match the bloom filter |
|
||||
|
||||
{% endautocrossref %}
|
||||
|
||||
|
|
|
|||
|
|
@ -257,7 +257,7 @@ displayed on high-resolution screens.
|
|||
|
||||
{% autocrossref %}
|
||||
|
||||
Bitcoin Core 0.9 supports the new [payment protocol][/en/glossary/payment-protocol]{:#term-payment-protocol}{:.term}. The payment protocol
|
||||
Bitcoin Core 0.9 supports the new [payment protocol][]{:#term-payment-protocol}{:.term}. The payment protocol
|
||||
adds many important features to payment requests:
|
||||
|
||||
- Supports X.509 certificates and SSL encryption to verify receivers' identity
|
||||
|
|
@ -423,7 +423,7 @@ for more details.
|
|||
|
||||
{% autocrossref %}
|
||||
|
||||
As explained in the [Transactions][] and [Block Chain][section block chain] sections, broadcasting
|
||||
As explained in the [Transactions][] and [Block Chain][] sections, broadcasting
|
||||
a transaction to the network doesn't ensure that the receiver gets
|
||||
paid. A malicious spender can create one transaction that pays the
|
||||
receiver and a second one that pays the same input back to himself. Only
|
||||
|
|
@ -431,20 +431,20 @@ one of these transactions will be added to the block chain, and nobody
|
|||
can say for sure which one it will be.
|
||||
|
||||
Two or more transactions spending the same input are commonly referred
|
||||
to as a [double spend][/en/glossary/double-spend]{:#term-double-spend}{:.term}.
|
||||
to as a [double spend][]{:#term-double-spend}{:.term}.
|
||||
|
||||
Once the transaction is included in a block, double spends are
|
||||
impossible without modifying block chain history to replace the
|
||||
transaction, which is quite difficult. Using this system,
|
||||
the Bitcoin protocol can give each of your transactions an updating confidence
|
||||
score based on the number of blocks which would need to be modified to replace
|
||||
a transaction. For each block, the transaction gains one [confirmation][/en/glossary/confirmation-score]{:#term-confirmation}{:.term}. Since
|
||||
a transaction. For each block, the transaction gains one [confirmation][]{:#term-confirmation}{:.term}. Since
|
||||
modifying blocks is quite difficult, higher confirmation scores indicate
|
||||
greater protection.
|
||||
|
||||
**0 confirmations**: The transaction has been broadcast but is still not
|
||||
included in any block. Zero confirmation transactions (unconfirmed
|
||||
transactions) should generally not be
|
||||
included in any block. Zero confirmation transactions ([unconfirmed
|
||||
transactions][]{:#term-unconfirmed-transactions}{:.term}) should generally not be
|
||||
trusted without risk analysis. Although miners usually confirm the first
|
||||
transaction they receive, fraudsters may be able to manipulate the
|
||||
network into including their version of a transaction.
|
||||
|
|
|
|||
|
|
@ -33,8 +33,8 @@ about coinbase transactions in the block chain section of this guide.
|
|||
|
||||
|
||||
The figure above shows the main parts of a Bitcoin transaction. Each
|
||||
transaction has at least one input and one output. Each [input][/en/glossary/input]{:#term-input}{:.term} spends the
|
||||
satoshis paid to a previous output. Each [output][/en/glossary/output]{:#term-output}{:.term} then waits as an Unspent
|
||||
transaction has at least one input and one output. Each [input][]{:#term-input}{:.term} spends the
|
||||
satoshis paid to a previous output. Each [output][]{:#term-output}{:.term} then waits as an Unspent
|
||||
Transaction Output (UTXO) until a later input spends it. When your
|
||||
Bitcoin wallet tells you that you have a 10,000 satoshi balance, it really
|
||||
means that you have 10,000 satoshis waiting in one or more UTXOs.
|
||||
|
|
@ -63,7 +63,7 @@ The figures below help illustrate how these features are used by
|
|||
showing the workflow Alice uses to send Bob a transaction and which Bob
|
||||
later uses to spend that transaction. Both Alice and Bob will use the
|
||||
most common form of the standard Pay-To-Public-Key-Hash (P2PKH) transaction
|
||||
type. [P2PKH][/en/glossary/p2pkh-address]{:#term-p2pkh}{:.term} lets Alice spend satoshis to a typical Bitcoin address,
|
||||
type. [P2PKH][]{:#term-p2pkh}{:.term} lets Alice spend satoshis to a typical Bitcoin address,
|
||||
and then lets Bob further spend those satoshis using a simple
|
||||
cryptographic key pair.
|
||||
|
||||
|
|
@ -71,9 +71,10 @@ cryptographic key pair.
|
|||
|
||||
Bob must first generate a private/public [key pair][]{:#term-key-pair}{:.term} before Alice can create the
|
||||
first transaction. Bitcoin uses the Elliptic Curve Digital Signature Algorithm (ECDSA) with
|
||||
the secp256k1 curve; secp256k1 [private keys][/en/glossary/private-key]{:#term-private-key}{:.term} are 256 bits of random
|
||||
the secp256k1 curve; secp256k1 [private keys][private
|
||||
key]{:#term-private-key}{:.term} are 256 bits of random
|
||||
data. A copy of that data is deterministically transformed into an secp256k1 [public
|
||||
key][/en/glossary/public-key]{:#term-public-key}{:.term}. Because the transformation can be reliably repeated later, the
|
||||
key][]{:#term-public-key}{:.term}. Because the transformation can be reliably repeated later, the
|
||||
public key does not need to be stored.
|
||||
|
||||
The public key (pubkey) is then cryptographically hashed. This pubkey hash can
|
||||
|
|
@ -88,8 +89,8 @@ and "full public key" to provide quick differentiation between the
|
|||
different states of a public key and to help the text better match the
|
||||
space-constrained diagrams where "public-key hash" wouldn't fit. -harding -->
|
||||
|
||||
Bob provides the pubkey hash to Alice. Pubkey hashes are almost always
|
||||
sent encoded as Bitcoin [addresses][/en/glossary/address]{:#term-address}{:.term}, which are base58-encoded strings
|
||||
Bob provides the [pubkey hash][]{:#term-pubkey-hash}{:.term} to Alice. Pubkey hashes are almost always
|
||||
sent encoded as Bitcoin [addresses][]{:#term-address}{:.term}, which are base58-encoded strings
|
||||
containing an address version number, the hash, and an error-detection
|
||||
checksum to catch typos. The address can be transmitted
|
||||
through any medium, including one-way mediums which prevent the spender
|
||||
|
|
@ -101,7 +102,7 @@ Once Alice has the address and decodes it back into a standard hash, she
|
|||
can create the first transaction. She creates a standard P2PKH
|
||||
transaction output containing instructions which allow anyone to spend that
|
||||
output if they can prove they control the private key corresponding to
|
||||
Bob's hashed public key. These instructions are called the [pubkey script][/en/glossary/pubkey-script]{:#term-pubkey-script}{:.term}
|
||||
Bob's hashed public key. These instructions are called the [pubkey script][]{:#term-pubkey-script}{:.term}
|
||||
or scriptPubKey.
|
||||
|
||||
Alice broadcasts the transaction and it is added to the block chain.
|
||||
|
|
@ -112,7 +113,7 @@ When, some time later, Bob decides to spend the UTXO, he must create an
|
|||
input which references the transaction Alice created by its hash, called
|
||||
a Transaction Identifier (txid), and the specific output she used by its
|
||||
index number ([output index][]{:#term-output-index}{:.term}). He must then create a [signature
|
||||
script][/en/glossary/signature-script]{:#term-signature-script}{:.term}---a
|
||||
script][]{:#term-signature-script}{:.term}---a
|
||||
collection of data parameters which satisfy the conditions Alice placed
|
||||
in the previous output's pubkey script. Signature scripts are also
|
||||
called scriptSigs.
|
||||
|
|
@ -129,7 +130,7 @@ pieces of data:
|
|||
1. His full (unhashed) public key, so the pubkey script can check that it
|
||||
hashes to the same value as the pubkey hash provided by Alice.
|
||||
|
||||
2. An secp256k1 [signature][/en/glossary/signature]{:#term-signature}{:.term} made by using the ECDSA cryptographic formula to combine
|
||||
2. An secp256k1 [signature][]{:#term-signature}{:.term} made by using the ECDSA cryptographic formula to combine
|
||||
certain transaction data (described below) with Bob's private key.
|
||||
This lets the pubkey script verify that Bob owns the private key which
|
||||
created the public key.
|
||||
|
|
@ -186,7 +187,7 @@ and full public key (pubkey), creating the following concatenation:
|
|||
|
||||
The script language is a
|
||||
[Forth-like](https://en.wikipedia.org/wiki/Forth_%28programming_language%29)
|
||||
stack-based language deliberately designed to be stateless and not
|
||||
[stack][]{:#term-stack}{:.term}-based language deliberately designed to be stateless and not
|
||||
Turing complete. Statelessness ensures that once a transaction is added
|
||||
to the block chain, there is no condition which renders it permanently
|
||||
unspendable. Turing-incompleteness (specifically, a lack of loops or
|
||||
|
|
@ -262,10 +263,10 @@ between programs prior to widespread implementation of the BIP70 Payment
|
|||
Protocol discussed later.
|
||||
|
||||
To solve these problems, pay-to-script-hash
|
||||
([P2SH][/en/glossary/p2sh-address]{:#term-p2sh}{:.term}) transactions were created in 2012 to let
|
||||
a spender create a pubkey script containing a hash of a second
|
||||
script, the
|
||||
[redeem script][/en/glossary/redeem-script]{:#term-redeem-script}{:.term}.
|
||||
([P2SH][]{:#term-p2sh}{:.term}) transactions were created in 2012 to let
|
||||
a spender create a pubkey script containing a [hash of a second
|
||||
script][script hash]{:#term-script-hash}{:.term}, the
|
||||
[redeem script][]{:#term-redeem-script}{:.term}.
|
||||
|
||||
The basic P2SH workflow, illustrated below, looks almost identical to
|
||||
the P2PKH workflow. Bob creates a redeem script with whatever script he
|
||||
|
|
@ -408,7 +409,7 @@ Signature script: OP_0 <A sig> <C sig> <redeemScript>
|
|||
|
||||
{% autocrossref %}
|
||||
|
||||
Pubkey outputs are a simplified form of the P2PKH pubkey script,
|
||||
[Pubkey][]{:#term-pubkey}{:.term} scripts are a simplified form of the P2PKH pubkey script,
|
||||
but they aren’t as
|
||||
secure as P2PKH, so they generally
|
||||
aren’t used in new transactions anymore.
|
||||
|
|
@ -426,7 +427,7 @@ Signature script: <sig>
|
|||
|
||||
{% autocrossref %}
|
||||
|
||||
[Null data][/en/glossary/null-data-transaction]{:#term-null-data}{:.term} pubkey scripts let you add a small amount of arbitrary data to the block
|
||||
[Null data][]{:#term-null-data}{:.term} pubkey scripts let you add a small amount of arbitrary data to the block
|
||||
chain in exchange for paying a transaction fee, but doing so is discouraged.
|
||||
(Null data is a standard pubkey script type only because some people were adding data
|
||||
to the block chain in more harmful ways.)
|
||||
|
|
@ -507,36 +508,36 @@ from modification, this lets signers selectively choose to let other
|
|||
people modify their transactions.
|
||||
|
||||
The various options for what to sign are
|
||||
called [signature hash][/en/glossary/signature-hash]{:#term-signature-hash}{:.term} types. There are three base SIGHASH types
|
||||
called [signature hash][]{:#term-signature-hash}{:.term} types. There are three base SIGHASH types
|
||||
currently available:
|
||||
|
||||
* [`SIGHASH_ALL`][/en/glossary/sighash-all]{:#term-sighash-all}{:.term}, the default, signs all the inputs and outputs,
|
||||
* [`SIGHASH_ALL`][sighash_all]{:#term-sighash-all}{:.term}, the default, signs all the inputs and outputs,
|
||||
protecting everything except the signature scripts against modification.
|
||||
|
||||
* [`SIGHASH_NONE`][/en/glossary/sighash-none]{:#term-sighash-none}{:.term} signs all of the inputs but none of the outputs,
|
||||
* [`SIGHASH_NONE`][sighash_none]{:#term-sighash-none}{:.term} signs all of the inputs but none of the outputs,
|
||||
allowing anyone to change where the satoshis are going unless other
|
||||
signatures using other signature hash flags protect the outputs.
|
||||
|
||||
* [`SIGHASH_SINGLE`][/en/glossary/sighash-none]{:#term-sighash-single}{:.term} signs only this input and only one corresponding
|
||||
* [`SIGHASH_SINGLE`][sighash_single]{:#term-sighash-single}{:.term} signs only this input and only one corresponding
|
||||
output (the output with the same output index number as the input), ensuring
|
||||
nobody can change your part of the transaction but allowing other
|
||||
signers to change their part of the transaction. The corresponding
|
||||
output must exist or the value "1" will be signed, breaking the security
|
||||
scheme.
|
||||
|
||||
The base types can be modified with the [`SIGHASH_ANYONECANPAY`][/en/glossary/sighash-anyonecanpay]{:#term-sighash-anyonecanpay}{:.term} (anyone can
|
||||
The base types can be modified with the [`SIGHASH_ANYONECANPAY`][shacp]{:#term-sighash-anyonecanpay}{:.term} (anyone can
|
||||
pay) flag, creating three new combined types:
|
||||
|
||||
* `SIGHASH_ALL|SIGHASH_ANYONECANPAY` signs all of the outputs but only
|
||||
* [`SIGHASH_ALL|SIGHASH_ANYONECANPAY`][sha_shacp]{:#term-sighash-all-sighash-anyonecanpay}{:.term} signs all of the outputs but only
|
||||
this one input, and it also allows anyone to add or remove other
|
||||
inputs, so anyone can contribute additional satoshis but they cannot
|
||||
change how many satoshis are sent nor where they go.
|
||||
|
||||
* `SIGHASH_NONE|SIGHASH_ANYONECANPAY` signs only this one input and
|
||||
* [`SIGHASH_NONE|SIGHASH_ANYONECANPAY`][shn_shacp]{:#term-sighash-none-sighash-anyonecanpay}{:.term} signs only this one input and
|
||||
allows anyone to add or remove other inputs or outputs, so anyone who
|
||||
gets a copy of this input can spend it however they'd like.
|
||||
|
||||
* `SIGHASH_SINGLE|SIGHASH_ANYONECANPAY` signs only this input and only
|
||||
* [`SIGHASH_SINGLE|SIGHASH_ANYONECANPAY`][shs_shacp]{:#term-sighash-single-sighash-anyonecanpay}{:.term} signs only this input and only
|
||||
one corresponding output, but it also allows anyone to add or remove
|
||||
other inputs.
|
||||
|
||||
|
|
@ -563,7 +564,7 @@ hash types sign, including the procedure for inserting the subscript -->
|
|||
|
||||
{% autocrossref %}
|
||||
|
||||
One thing all signature hash types sign is the transaction's [locktime][/en/glossary/locktime]{:#term-locktime}{:.term}.
|
||||
One thing all signature hash types sign is the transaction's [locktime][]{:#term-locktime}{:.term}.
|
||||
(Called nLockTime in the Bitcoin Core source code.)
|
||||
The locktime indicates the earliest time a transaction can be added to
|
||||
the block chain.
|
||||
|
|
@ -590,7 +591,7 @@ Previous versions of Bitcoin Core provided a feature which prevented
|
|||
transaction signers from using the method described above to cancel a
|
||||
time-locked transaction, but a necessary part of this feature was
|
||||
disabled to prevent denial of service attacks. A legacy of this system are four-byte
|
||||
[sequence numbers][/en/glossary/sequence-number]{:#term-sequence-number}{:.term} in every input. Sequence numbers were meant to allow
|
||||
[sequence numbers][sequence number]{:#term-sequence-number}{:.term} in every input. Sequence numbers were meant to allow
|
||||
multiple signers to agree to update a transaction; when they finished
|
||||
updating the transaction, they could agree to set every input's
|
||||
sequence number to the four-byte unsigned maximum (0xffffffff),
|
||||
|
|
@ -624,20 +625,20 @@ enable locktime.
|
|||
|
||||
Transactions typically pay transaction fees based on the total byte size
|
||||
of the signed transaction. The transaction fee is given to the
|
||||
Bitcoin miner, as explained in the [block chain section][section block chain], and so it is
|
||||
Bitcoin miner, as explained in the [block chain section][block chain], and so it is
|
||||
ultimately up to each miner to choose the minimum transaction fee they
|
||||
will accept.
|
||||
|
||||
<!-- TODO: check: 50 KB or 50 KiB? Not that transactors care... -->
|
||||
|
||||
By default, miners reserve 50 KB of each block for [high-priority
|
||||
transactions][/en/glossary/high-priority-transaction]{:#term-high-priority-transactions}{:.term} which spend satoshis that haven't been spent for a long
|
||||
transactions][]{:#term-high-priority-transactions}{:.term} which spend satoshis that haven't been spent for a long
|
||||
time. The remaining space in each block is typically allocated to transactions
|
||||
based on their fee per byte, with higher-paying transactions being added
|
||||
in sequence until all of the available space is filled.
|
||||
|
||||
As of Bitcoin Core 0.9, transactions which do not count as high-priority transactions
|
||||
need to pay a [minimum fee][/en/glossary/minimum-relay-fee]{:#term-minimum-fee}{:.term} (currently 1,000 satoshis) to be
|
||||
need to pay a [minimum fee][]{:#term-minimum-fee}{:.term} (currently 1,000 satoshis) to be
|
||||
broadcast across the network. Any transaction paying only the minimum fee
|
||||
should be prepared to wait a long time before there's enough spare space
|
||||
in a block to include it. Please see the [verifying payment section][section verifying payment]
|
||||
|
|
@ -649,7 +650,7 @@ UTXOs must be spent or given to a miner as a transaction fee. Few
|
|||
people will have UTXOs that exactly match the amount they want to pay,
|
||||
so most transactions include a change output.
|
||||
|
||||
[Change outputs][/en/glossary/change-address]{:#term-change-output}{:.term} are regular outputs which spend the surplus satoshis
|
||||
[Change outputs][change output]{:#term-change-output}{:.term} are regular outputs which spend the surplus satoshis
|
||||
from the UTXOs back to the spender. They can reuse the same P2PKH pubkey hash
|
||||
or P2SH script hash as was used in the UTXO, but for the reasons
|
||||
described in the [next subsection](#avoiding-key-reuse), it is highly recommended that change
|
||||
|
|
@ -718,7 +719,7 @@ fixed URI to which payments should be sent, please see the
|
|||
|
||||
None of Bitcoin's signature hash types protect the signature script, leaving
|
||||
the door open for a limited denial of service attack called [transaction
|
||||
malleability][/en/glossary/malleability]{:.term}{:#term-transaction-malleability}. The signature script
|
||||
malleability][]{:.term}{:#term-transaction-malleability}. The signature script
|
||||
contains the secp256k1 signature, which can't sign itself, allowing attackers to
|
||||
make non-functional modifications to a transaction without rendering it
|
||||
invalid. For example, an attacker can add some data to the signature script
|
||||
|
|
|
|||
|
|
@ -284,7 +284,7 @@ Private keys are what are used to unlock satoshis from a particular address. In
|
|||
|
||||
{% autocrossref %}
|
||||
|
||||
In order to make copying of private keys less prone to error, [Wallet Import Format][/en/glossary/wallet-import-format]{:#term-wallet-import-format}{:.term} may be utilized. WIF uses base58Check encoding on an private key, greatly decreasing the chance of copying error, much like standard Bitcoin addresses.
|
||||
In order to make copying of private keys less prone to error, [Wallet Import Format][]{:#term-wallet-import-format}{:.term} may be utilized. WIF uses base58Check encoding on an private key, greatly decreasing the chance of copying error, much like standard Bitcoin addresses.
|
||||
|
||||
1. Take a private key.
|
||||
|
||||
|
|
@ -403,7 +403,7 @@ For consistent word ordering:
|
|||
{% autocrossref %}
|
||||
|
||||
The hierarchical deterministic key creation and transfer protocol ([HD
|
||||
protocol][/en/glossary/hd-protocol]{:#term-hd-protocol}{:.term}) greatly simplifies wallet
|
||||
protocol][]{:#term-hd-protocol}{:.term}) greatly simplifies wallet
|
||||
backups, eliminates the need for repeated communication between multiple
|
||||
programs using the same wallet, permits creation of child accounts which
|
||||
can operate independently, gives each parent account the ability to
|
||||
|
|
@ -424,8 +424,9 @@ point (the public key):
|
|||
{% autocrossref %}
|
||||
|
||||
Because of the way `point()` functions, it's possible to create a [child
|
||||
public key][/en/glossary/child-key]{:#term-child-public-key}{:.term} by combining an
|
||||
existing [(parent) public key][/en/glossary/parent-key]{:#term-parent-public-key}{:.term} with another public key created from any
|
||||
public key][]{:#term-child-public-key}{:.term} by combining an
|
||||
existing [(parent) public key][parent public
|
||||
key]{:#term-parent-public-key}{:.term} with another public key created from any
|
||||
integer (*i*) value. This child public key is the same public key which
|
||||
would be created by the `point()` function if you added the *i* value to
|
||||
the original (parent) private key and then found the remainder of that
|
||||
|
|
@ -438,8 +439,8 @@ sum divided by a global constant used by all Bitcoin software (*G*):
|
|||
{% autocrossref %}
|
||||
|
||||
This means that two or more independent programs which agree on a
|
||||
sequence of integers can create a series of unique [child key][/en/glossary/child-key]{:#term-child-key}{:.term} pairs from
|
||||
a single [parent key][/en/glossary/parent-key]{:#term-parent-key}{:.term} pair without any further communication.
|
||||
sequence of integers can create a series of unique [child key][]{:#term-child-key}{:.term} pairs from
|
||||
a single [parent key][]{:#term-parent-key}{:.term} pair without any further communication.
|
||||
Moreover, the program which distributes new public keys for receiving
|
||||
payment can do so without any access to the private keys, allowing the
|
||||
public key distribution program to run on a possibly-insecure platform such as
|
||||
|
|
@ -468,10 +469,10 @@ The HD protocol uses a single root seed to create a hierarchy of
|
|||
child, grandchild, and other descended keys with unlinkable
|
||||
deterministically-generated integer values. Each child key also gets
|
||||
a deterministically-generated seed from its parent, called a [chain
|
||||
code][/en/glossary/chain-code]{:#term-chain-code}{:.term}, so the compromising of one chain
|
||||
code][]{:#term-chain-code}{:.term}, so the compromising of one chain
|
||||
code doesn't necessary compromise the integer sequence for the whole
|
||||
hierarchy, allowing the [master chain
|
||||
code][/en/glossary/master-chain-code-and-private-key]{:#term-master-chain-code}{:.term} to continue being useful
|
||||
code][]{:#term-master-chain-code}{:.term} to continue being useful
|
||||
even if, for example, a web-based public key distribution program
|
||||
gets hacked.
|
||||
|
||||
|
|
@ -479,10 +480,10 @@ gets hacked.
|
|||
|
||||
As illustrated above, HD key derivation takes four inputs<!--noref-->:
|
||||
|
||||
* The *[parent private key][/en/glossary/parent-key]{:#term-parent-private-key}{:.term}* and
|
||||
* The *[parent private key][]{:#term-parent-private-key}{:.term}* and
|
||||
*parent public key* are regular uncompressed 256-bit ECDSA keys.
|
||||
|
||||
* The [parent chain code][/en/glossary/chain-code]{:#term-parent-chain-code}{:.term} is 256
|
||||
* The [parent chain code][]{:#term-parent-chain-code}{:.term} is 256
|
||||
bits of seemingly-random data.
|
||||
|
||||
* The [index][key index]{:#term-key-index}{:.term} number is a 32-bit integer specified by the program.
|
||||
|
|
@ -510,17 +511,17 @@ child keys using the child chain code will create unlinkable grandchild keys.
|
|||
|
||||
Because creating child keys requires both a key and a chain code, the
|
||||
key and chain code together are called the [extended
|
||||
key][/en/glossary/extended-key]{:#term-extended-key}{:.term}. An [extended private
|
||||
key][/en/glossary/extended-key]{:#term-extended-private-key}{:.term} and its corresponding
|
||||
[extended public key][/en/glossary/extended-key]{:#term-extended-public-key}{:.term} have the
|
||||
key][]{:#term-extended-key}{:.term}. An [extended private
|
||||
key][]{:#term-extended-private-key}{:.term} and its corresponding
|
||||
[extended public key][]{:#term-extended-public-key}{:.term} have the
|
||||
same chain code. The (top-level parent) [master private
|
||||
key][/en/glossary/master-chain-code-and-private-key]{:#term-master-private-key}{:.term} and master chain
|
||||
key][]{:#term-master-private-key}{:.term} and master chain
|
||||
code are derived from random data,
|
||||
as illustrated below.
|
||||
|
||||
|
||||
|
||||
A [root seed][/en/glossary/hd-wallet-seed]{:#term-root-seed}{:.term} is created from either 128
|
||||
A [root seed][]{:#term-root-seed}{:.term} is created from either 128
|
||||
bits, 256 bits, or 512 bits of random data. This root seed of as little
|
||||
as 128 bits is the the only data the user needs to backup in order to
|
||||
derive every key created by a particular wallet program using
|
||||
|
|
@ -588,7 +589,7 @@ knowing the parent private key. In other words, parent extended public
|
|||
keys can't create hardened child public keys.
|
||||
|
||||
Because of that, a [hardened extended private
|
||||
key][/en/glossary/hardened-extended-key]{:#term-hardened-extended-private-key}{:.term} is much less
|
||||
key][]{:#term-hardened-extended-private-key}{:.term} is much less
|
||||
useful than a normal extended private key---however,
|
||||
hardened extended private keys create a firewall through which
|
||||
multi-level key derivation compromises cannot happen. Because hardened
|
||||
|
|
|
|||
Some files were not shown because too many files have changed in this diff Show more
Loading…
Add table
Add a link
Reference in a new issue