arno/bitcoinbook
1
0
Fork 0
mirror of https://github.com/bitcoinbook/bitcoinbook synced 2025-06-25 09:22:38 +00:00
Code Issues Releases Wiki Activity

Edited ch01_intro.adoc with Atlas code editor

Browse Source
This commit is contained in:
clenser 2023-10-13 11:16:20 +00:00
parent a00403189d
commit 1da0c59c28
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
ch01_intro.adoc
View File

@ -195,7 +195,7 @@ hardware signing device.
===== Full node versus Lightweight ===== Full node versus Lightweight
Another way to categorize Bitcoin wallets is by their degree of autonomy and how they interact with the Bitcoin network: 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 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 transactions and serve data to other Bitcoin programs, either on the
same computer or over the internet. A full node uses substantial 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. complete autonomy to its users.
Lightweight client:: 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 connects to a full node or other remote server for receiving and sending
Bitcoin transaction information, but stores the user wallet locally, Bitcoin transaction information, but stores the user wallet locally,
partially validates the transactions it receives, and independently partially validates the transactions it receives, and independently