We are indeed evaluating some issues that will arise far into the future and we are already working to mitigate them. We are not going to give a hard launch date as it fuels pump and dumps. When we are 100% ready we will release.
We just completed a successful 12,000 Block test run with DigiSpeed modifications (8mb blocks, 15 second transactions, difficulty calculation modifications, transaction propagation changes.)
The test resulted in even distribution between the five algos and our actual test data showed and average block time of 14.68 seconds (slightly speedier than planned).
Average transaction size: 250 bytes
Maximum block size: 8mb (8,388,608bytes)
Average block-time: 14.68
Maximum BTC TPS = 7 transactions per second.
BTC block size = 1mb
7 x 8mb blocks = 56 TPS
BTC Block Time= 10 min
DGB block time= 14.68 sec
600 min / 14.68 sec = 40.87 multiplier
56 TPS x 40.87 =
2,228 DigiByte Transactions per second Visa averages 2,000 TPS
Following the DigiSpeed v4.0 release we will release a version v5.0 in mid 2016 with enhanced block pruning, headers first sync and additional "incentives" for people like gamers to run a "full node" and keep the network decentralized as blockchain size increases
It's all well and good to say "we tested it and had no problem" but that would never fly in a corporate environment. You'd have to show data/proof.
I'd personally like to see the test blockchain data. Put up your test blockchain explorer somewhere so we can examine how many transactions you were sending per block.
In the data you provided, you say that the average transaction size is 250 bytes. But, how is that number used to calculate the 2228 DGB trans/second? If you divide 8mb/250 you come up with a theoretical maximum of 33554 transactions per block. Divide that by 14.68 you come up with 2286 trans/sec.
250 bytes is about right for a block with 1 input per transaction (block reward only).
I did a quick check of the last 1695 blocks (1336523 through 1338189) and came up with an average transaction size of 392 bytes (block size divided by transactions). This would lower the theoretical transactions/second to 1457.
As more and more transactions happen, there are going to be more inputs per transactions and that's going to inflate the size of each transaction, this is why I'm curious to see how many transactions you had per block and how many inputs you had per transactions.
