From 42f4f0b530eec81b6747e85f23329bdefb5e128f Mon Sep 17 00:00:00 2001 From: Richard Date: Tue, 23 Mar 2021 17:13:56 +0100 Subject: [PATCH] Update 01_introduction.asciidoc (#651) Typo MB -> GB --- 01_introduction.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/01_introduction.asciidoc b/01_introduction.asciidoc index 1901f38..06ac5cb 100644 --- a/01_introduction.asciidoc +++ b/01_introduction.asciidoc @@ -158,7 +158,7 @@ This does not include the traffic overhead of forwarding the transaction informa While 10 MB/s does not seem extreme in the context of high-speed fiber optic and 5G mobile speeds, it would effectively exclude anyone who cannot meet this requirement from running a node, especially in countries where high-performance internet is not affordable or widely available. Users also have many other demands on their bandwidth and cannot be expected to expend this much only to receive transactions. -Furthermore storing this information locally would result in 864GB Megabytes per day. This is roughly one Terabyte of data or the size of a hard drive. +Furthermore storing this information locally would result in 864 Gigabytes per day. This is roughly one Terabyte of data or the size of a hard drive. Verifying 40,000 ECDSA signatures per second is also barely feasible (c.f.: https://bitcoin.stackexchange.com/questions/95339/how-many-bitcoin-transactions-can-be-verified-per-second) making the _Initial Blockchain Download (IBD)_ of the Bitcoin blockchain (synchronizing and verifying everything starting from the genesis block) almost impossible without very expensive hardware.