Skip to content

Latest commit

 

History

History
216 lines (109 loc) · 13 KB

terms.rst

File metadata and controls

216 lines (109 loc) · 13 KB
orphan:

Terms

Note

This is a temporary page with references used as targets for links in the documentation. They should be replaced by adding proper labels inline in the respective pages. This is more easily be done manually so this page acts as a temporary placeholder for that until the automatic import and conversion to RST is completed.

signature_script_modification_warning (developer-reference) (original target)

term-bitcoin-uri (payment-processing-guide) (original target): A URI which allows receivers to encode payment details so spenders don't have to manually enter addresses and other details.

term-certificate-chain (developer-examples) (original target): A chain of certificates connecting a individual's leaf certificate to the certificate authority's root certificate.

term-coinbase-block-height (developer-reference) (original target): The current block's height encoded into the first bytes of the coinbase field.

term-fiat (payment-processing-guide) (original target): National currencies such as the dollar or euro.

term-intermediate-certificate (developer-examples) (original target): A intermediate certificate authority certificate which helps connect a leaf (receiver) certificate to a root certificate authority.

term-key-index (wallets-guide) (original target): An index number used in the HD wallet formula to generate child keys from a parent key.

term-key-pair (transactions-guide) (original target): A private key and its derived public key.

term-label (payment-processing-guide) (original target): The label parameter of a bitcoin: URI which provides the spender with the receiver's name (unauthenticated).

term-leaf-certificate (developer-examples) (original target): The end-node in a certificate chain; in the payment protocol, it is the certificate belonging to the receiver of satoshis.

term-merge (payment-processing-guide) (original target): Spending, in the same transaction, multiple outputs which can be traced back to different previous spenders, leaking information about how many satoshis you control.

term-merge-avoidance (payment-processing-guide) (original target): A strategy for selecting which outputs to spend that avoids merging outputs with different histories that could leak private information.

term-message (payment-processing-guide) (original target): A parameter of bitcoin: URIs which allows the receiver to optionally specify a message to the spender.

term-micropayment-channel (contracts-guide) (original target)

term-msg_block (developer-reference) (original target): The block header hash data type identifier of an inventory on the P2P network.

term-msg_cmpct_block (developer-reference) (original target): An alternative to the block header hash data type identifier of an inventory on the P2P network used to request a compact block.

term-msg_filtered_witness_block (developer-reference) (original target): An alternative to the block header hash data type identifier of an inventory on the P2P network that is reserved for future use and unused.

term-msg_tx (developer-reference) (original target): The TXID data type identifier of an inventory on the P2P network.

term-msg_witness_block (developer-reference) (original target): An alternative to the block header hash data type identifier of an inventory on the P2P network used to request a block with witness serialization for SegWit.

term-msg_witness_tx (developer-reference) (original target): An alternative of the transaction data type identifier of an inventory on the P2P network used to request a transaction with witness serialization for SegWit.

term-op-checkmultisig (developer-reference) (original target): Opcode which returns true if one or more provided signatures (m) sign the correct parts of a transaction and match one or more provided public keys (n).

term-op-checksig (developer-reference) (original target): Opcode which returns true if a signature signs the correct parts of a transaction and matches a provided public key.

term-op-dup (developer-reference) (original target): Operation which duplicates the entry below it on the stack.

term-op-equal (developer-reference) (original target): Operation which returns true if the two entries below it on the stack are equivalent.

term-op-equalverify (developer-reference) (original target): Operation which terminates the script in failure unless the two entries below it on the stack are equivalent.

term-op-hash160 (developer-reference) (original target): Operation which converts the entry below it on the stack into a RIPEMD(SHA256()) hashed version of itself.

term-op-return (developer-reference) (original target): Operation which terminates the script in failure.

term-op-verify (developer-reference) (original target): Operation which terminates the script if the entry below it on the stack is non-true (zero).

term-output-index (transactions-guide) (original target): The sequentially-numbered index of outputs in a single transaction starting from 0.

term-paymentdetails (developer-examples) (original target): The PaymentDetails of the payment protocol which allows the receiver to specify the payment details to the spender.

term-paymentrequest (developer-examples) (original target): The PaymentRequest of the payment protocol which contains and allows signing of the PaymentDetails.

term-pki (developer-examples) (original target): Public Key Infrastructure; usually meant to indicate the X.509 certificate system used for HTTP Secure (https).

term-point-function (wallets-guide) (original target): The ECDSA function used to create a public key from a private key.

term-pp-amount (developer-examples) (original target): Part of the Output part of the PaymentDetails part of a payment protocol where receivers can specify the amount of satoshis they want paid to a particular pubkey script.

term-pp-expires (developer-examples) (original target): The expires field of a PaymentDetails where the receiver tells the spender when the PaymentDetails expires.

term-pp-memo (developer-examples) (original target): The memo fields of PaymentDetails, Payment, and PaymentACK which allow spenders and receivers to send each other memos.

term-pp-merchant-data (developer-examples) (original target): The merchant_data part of PaymentDetails and Payment which allows the receiver to send arbitrary data to the spender in PaymentDetails and receive it back in Payments.

term-pp-pki-data (developer-examples) (original target): The pki_data field of a PaymentRequest which provides details such as certificates necessary to validate the request.

term-pp-pki-type (developer-examples) (original target): The PKI field of a PaymentRequest which tells spenders how to validate this request as being from a specific recipient.

term-pp-script (developer-examples) (original target): The script field of a PaymentDetails where the receiver tells the spender what pubkey scripts to pay.

term-previous-block-header-hash (developer-reference) (original target): A field in the block header which contains the SHA256(SHA256()) hash of the previous block's header.

term-r-parameter (payment-processing-guide) (original target): The payment request parameter in a bitcoin: URI.

term-receipt (payment-processing-guide) (original target): A cryptographically-verifiable receipt created using parts of a payment request and a confirmed transaction.

term-root-certificate (developer-examples) (original target): A certificate belonging to a certificate authority (CA).

term-ssl-signature (developer-examples) (original target): Signatures created and recognized by major SSL implementations such as OpenSSL.

term-standard-block-relay (p2p-network-guide) (original target): The regular block relay method: announcing a block with an inv message and waiting for a response.

term-transaction-version-number (transactions-guide) (original target): A version number prefixed to transactions to allow upgrading.

term-unique-address (transactions-guide) (original target): Address which are only used once to protect privacy and increase security.

term-unsolicited-block-push (p2p-network-guide) (original target): When a miner sends a block message without sending an inv message first.

term-uri-qr-code (payment-processing-guide) (original target): A QR code containing a bitcoin: URI.

term-v2-block (developer-reference) (original target): The current version of Bitcoin blocks.

term-x509certificates (developer-examples) (original target)