1
0
mirror of https://github.com/bitcoinbook/bitcoinbook synced 2025-07-31 19:08:05 +00:00

Edited ch02_overview.adoc with Atlas code editor

This commit is contained in:
clenser 2023-10-13 18:14:04 +00:00
parent 8c32017549
commit 2628b27c54

View File

@ -424,7 +424,7 @@ the software logic and the data necessary for them to fully verify the
correctness of a new transaction. The connections between peers are correctness of a new transaction. The connections between peers are
often visualized as edges (lines) in a graph, with the peers themselves often visualized as edges (lines) in a graph, with the peers themselves
being the nodes (dots). For that reason, Bitcoin peers are commonly being the nodes (dots). For that reason, Bitcoin peers are commonly
called "full verification nodes," or _full nodes_ for short. called "full verification nodes," ((("full nodes")))or _full nodes_ for short.
Alice's wallet application can send the new Alice's wallet application can send the new
transaction to any Bitcoin node over any type of transaction to any Bitcoin node over any type of
@ -436,7 +436,7 @@ to use the internet connection offered by Bob, though both those
options are possible too. Any Bitcoin node that receives a options are possible too. Any Bitcoin node that receives a
valid transaction it has not seen before will forward it to valid transaction it has not seen before will forward it to
all other nodes to which it is connected, a propagation technique known all other nodes to which it is connected, a propagation technique known
as _gossiping_. Thus, the transaction rapidly propagates out across the ((("gossiping")))as _gossiping_. Thus, the transaction rapidly propagates out across the
peer-to-peer network, reaching a large percentage of the nodes within a peer-to-peer network, reaching a large percentage of the nodes within a
few seconds. few seconds.