Comment
Author: Admin | 2025-04-28
Whether or not it uses a compressed public key.Not to be confused with: Extended private keys (which allow importing a hierarchy of private keys)Watch-only addressAn address or pubkey script stored in the wallet without the corresponding private key, allowing the wallet to watch for outputs but not spend them.Bitcoin URIA URI which allows receivers to encode payment details so spenders don’t have to manually enter addresses and other details.Certificate chainA chain of certificates connecting a individual’s leaf certificate to the certificate authority’s root certificate.Coinbase block heightThe current block’s height encoded into the first bytes of the coinbase field.FiatNational currencies such as the dollar or euro.Intermediate certificateA intermediate certificate authority certificate which helps connect a leaf (receiver) certificate to a root certificate authority.Key indexAn index number used in the HD wallet formula to generate child keys from a parent key.Key pairA private key and its derived public key.LabelThe label parameter of a bitcoin: URI which provides the spender with the receiver’s name (unauthenticated).Leaf certificateThe end-node in a certificate chain; in the payment protocol, it is the certificate belonging to the receiver of satoshis.MergeSpending, in the same transaction, multiple outputs which can be traced back to different previous spenders, leaking information about how many satoshis you control.Merge avoidanceA strategy for selecting which outputs to spend that avoids merging outputs with different histories that could leak private information.MessageA parameter of bitcoin: URIs which allows the receiver to optionally specify a message to the spender.Micropayment channelterm-micropayment-channel (contracts-guide) (original target)OP CHECKMULTISIGOpcode 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).Output indexThe sequentially-numbered index of outputs in a single transaction starting from 0.PKIPublic Key Infrastructure; usually meant to indicate the X.509 certificate system used for HTTP Secure (https).Point functionThe ECDSA function used to create a public key from a private key.PP amountPart 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.PP expiresThe expires field of a PaymentDetails where the receiver tells the spender when the PaymentDetails expires.PP memoThe memo fields of PaymentDetails, Payment, and PaymentACK which allow spenders and receivers to send each other memos.PP merchant dataThe 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.PP pki dataThe pki_data field of a PaymentRequest which provides details such as certificates necessary to validate the request.PP pki typeThe PKI field of a PaymentRequest which tells spenders how to validate this request as being from a specific recipient.PP scriptThe script field of a PaymentDetails where the receiver tells the spender what pubkey scripts to pay.A field in the block header which contains the SHA256(SHA256()) hash of the previous block’s header.R parameterThe payment request parameter in a bitcoin: URI.ReceiptA cryptographically-verifiable receipt created using parts of a payment request and a confirmed transaction.Root certificateA certificate belonging to a certificate
Add Comment