From d17df44749a537df5cae47150fbc9e54f8f2bbde Mon Sep 17 00:00:00 2001 From: Hugo Doyon Date: Sat, 25 Apr 2020 10:35:21 -0400 Subject: [PATCH] feasable? feasible (typo) --- 01_introduction.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/01_introduction.asciidoc b/01_introduction.asciidoc index 107acd1..7500568 100644 --- a/01_introduction.asciidoc +++ b/01_introduction.asciidoc @@ -24,7 +24,7 @@ Assuming 250 Bytes on average per transaction this would result in a data stream This is does not include the traffic overhead of forwarding the transaction information to other peers. While single hosts on the internet could handle such a load of traffic our current internet would not be able to support this traffic for a large fraction of hosts. Also storing this information locally would result in 864000 Megabyte per day. This is roughly 1 Terabyte of data or the size of a hard drive. -While verifying 40.000 ECDSA signatures per second seems barely feasable (c.f.: https://bitcoin.stackexchange.com/questions/95339/how-many-bitcoin-transactions-can-be-verified-per-second) nodes could hardly catch up initial sync of the blockchain. +While verifying 40.000 ECDSA signatures per second seems barely feasible (c.f.: https://bitcoin.stackexchange.com/questions/95339/how-many-bitcoin-transactions-can-be-verified-per-second) nodes could hardly catch up initial sync of the blockchain. ==== But what if each node wasn't required to know and validate every single transaction? What if there was a way to have scalable off-chain transactions, without losing the security of the Bitcoin network?