You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: glossary.rst
+154Lines changed: 154 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -492,4 +492,158 @@ Glossary
492
492
493
493
Watch-only address
494
494
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.
495
+
496
+
Bitcoin URI
497
+
A URI which allows receivers to encode payment details so spenders don't have to manually enter addresses and other details.
498
+
499
+
Certificate chain
500
+
A chain of certificates connecting a individual's leaf certificate to the certificate authority's root certificate.
501
+
502
+
Coinbase block height
503
+
The current block's height encoded into the first bytes of the coinbase field.
504
+
505
+
Fiat
506
+
National currencies such as the dollar or euro.
507
+
508
+
Intermediate certificate
509
+
A intermediate certificate authority certificate which helps connect a leaf (receiver) certificate to a root certificate authority.
510
+
511
+
Key index
512
+
An index number used in the HD wallet formula to generate child keys from a parent key.
513
+
514
+
Key pair
515
+
A private key and its derived public key.
516
+
517
+
Label
518
+
The label parameter of a bitcoin: URI which provides the spender with the receiver's name (unauthenticated).
519
+
520
+
Leaf certificate
521
+
The end-node in a certificate chain; in the payment protocol, it is the certificate belonging to the receiver of satoshis.
522
+
523
+
Merge
524
+
Spending, in the same transaction, multiple outputs which can be traced back to different previous spenders, leaking information about how many satoshis you control.
525
+
526
+
Merge avoidance
527
+
A strategy for selecting which outputs to spend that avoids merging outputs with different histories that could leak private information.
528
+
529
+
Message
530
+
A parameter of bitcoin: URIs which allows the receiver to optionally specify a message to the spender.
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).
Public Key Infrastructure; usually meant to indicate the X.509 certificate system used for HTTP Secure (https).
588
+
589
+
Point function
590
+
The ECDSA function used to create a public key from a private key.
591
+
592
+
PP amount
593
+
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.
594
+
595
+
PP expires
596
+
The expires field of a PaymentDetails where the receiver tells the spender when the PaymentDetails expires.
597
+
598
+
PP memo
599
+
The memo fields of PaymentDetails, Payment, and PaymentACK which allow spenders and receivers to send each other memos.
600
+
601
+
PP merchant data
602
+
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.
603
+
604
+
PP pki data
605
+
The pki_data field of a PaymentRequest which provides details such as certificates necessary to validate the request.
606
+
607
+
PP pki type
608
+
The PKI field of a PaymentRequest which tells spenders how to validate this request as being from a specific recipient.
609
+
610
+
PP script
611
+
The script field of a PaymentDetails where the receiver tells the spender what pubkey scripts to pay.
612
+
613
+
Previous block header hash
614
+
A field in the block header which contains the SHA256(SHA256()) hash of the previous block's header.
615
+
616
+
R parameter
617
+
The payment request parameter in a bitcoin: URI.
618
+
619
+
Receipt
620
+
A cryptographically-verifiable receipt created using parts of a payment request and a confirmed transaction.
621
+
622
+
Root certificate
623
+
A certificate belonging to a certificate authority (CA).
624
+
625
+
SSL signature
626
+
Signatures created and recognized by major SSL implementations such as OpenSSL.
627
+
628
+
Stanndard block relay
629
+
The regular block relay method: announcing a block with an inv message and waiting for a response.
630
+
631
+
Transaction version number
632
+
A version number prefixed to transactions to allow upgrading.
633
+
634
+
Unique Address
635
+
Address which are only used once to protect privacy and increase security.
636
+
637
+
Unsolicited block push
638
+
When a miner sends a block message without sending an inv message first.
0 commit comments