From 1da0c59c28e40cfb8d7654eeb03e897a0bc39b7e Mon Sep 17 00:00:00 2001 From: clenser Date: Fri, 13 Oct 2023 11:16:20 +0000 Subject: [PATCH] Edited ch01_intro.adoc with Atlas code editor --- ch01_intro.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ch01_intro.adoc b/ch01_intro.adoc index fd2833e7..7fb8fa5c 100644 --- a/ch01_intro.adoc +++ b/ch01_intro.adoc @@ -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