What broke the Lisk 0.1.4 network was 600 transactions in a minute or 10 transactions per second (10 tps).
For years, Bitcoin has been limited to 7 tps until changes made to cope with its DDoS attack last year.
https://blog.blockcypher.com/a-bitcoin-spam-attack-post-mortem-s-la-ying-alive-654e914edcf4#.mypx90hpi
http://fc16.ifca.ai/bitcoin/papers/BHMW16.pdf
@liskhq : What tps figure is the new and improved Lisk 0.1.5 network designed to support? What tps figure has been demonstrated in testing?
A major change made by BTC has been modifications in their transaction queueing system that stores excessive incoming transactions for processing during later blocktimes. Basically they store on the machines of individual miners those transactions that cannot be processed immediately. The miners then resubmit those transactions for processing at a later time.
What is the buffer size in Lisk 0.1.5 among the 101 Active Delegates (both in bytes and in transactions) that stores "excessive" transactions for later processing during future blocktimes?
For years, Bitcoin has been limited to 7 tps until changes made to cope with its DDoS attack last year.
https://blog.blockcypher.com/a-bitcoin-spam-attack-post-mortem-s-la-ying-alive-654e914edcf4#.mypx90hpi
http://fc16.ifca.ai/bitcoin/papers/BHMW16.pdf
@liskhq : What tps figure is the new and improved Lisk 0.1.5 network designed to support? What tps figure has been demonstrated in testing?
A major change made by BTC has been modifications in their transaction queueing system that stores excessive incoming transactions for processing during later blocktimes. Basically they store on the machines of individual miners those transactions that cannot be processed immediately. The miners then resubmit those transactions for processing at a later time.
What is the buffer size in Lisk 0.1.5 among the 101 Active Delegates (both in bytes and in transactions) that stores "excessive" transactions for later processing during future blocktimes?