Archives/lnbook
2
0
Fork 0
mirror of https://github.com/lnbook/lnbook synced 2024-11-04 18:00:26 +00:00
Code Issues Projects Releases Wiki Activity

feasable?

Browse Source 
feasible (typo)
This commit is contained in:
Hugo Doyon 2020-04-25 10:35:21 -04:00 committed by GitHub
parent 5bb60a65c6
commit d17df44749
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
01_introduction.asciidoc
View File

@ -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?