mirror of
https://github.com/bitcoinbook/bitcoinbook
synced 2025-02-22 20:42:09 +00:00
Edited ch01_intro.adoc with Atlas code editor
This commit is contained in:
parent
a00403189d
commit
1da0c59c28
@ -195,7 +195,7 @@ hardware signing device.
|
||||
===== Full node versus Lightweight
|
||||
Another way to categorize Bitcoin wallets is by their degree of autonomy and how they interact with the Bitcoin network:
|
||||
|
||||
Full node:: A full node is a program that validates the
|
||||
Full node:: A full node ((("full nodes")))is a program that validates the
|
||||
entire history of Bitcoin transactions (every transaction by every user, ever). Optionally, full nodes can also store previously validated
|
||||
transactions and serve data to other Bitcoin programs, either on the
|
||||
same computer or over the internet. A full node uses substantial
|
||||
@ -204,7 +204,7 @@ video for each day of Bitcoin transactions--but the full node offers
|
||||
complete autonomy to its users.
|
||||
|
||||
Lightweight client::
|
||||
A lightweight client, also known as a simplified-payment-verification (SPV) client,
|
||||
A lightweight client,((("lightweight clients")))((("simplified-payment-verification (SPV) clients")))((("SPV (simplified-payment-verification) clients"))) also known as a simplified-payment-verification (SPV) client,
|
||||
connects to a full node or other remote server for receiving and sending
|
||||
Bitcoin transaction information, but stores the user wallet locally,
|
||||
partially validates the transactions it receives, and independently
|
||||
|
Loading…
Reference in New Issue
Block a user