How is the network going to deal with transaction flooding?
I know that when there is value put in network, then making thousands of transactions means money, but let's assume that there is a triggering event, that causes hundreds or even thousands of users to, simultaneously, create a transaction of any kind.
Now there are max 30tx/blk, but there might be a peak demand of network for 500 or 15k transactions per minute - then all those transactions are pending, effectively blocking new transactions from entering into blockchain.
On the other hand all delegates know what those pending transactions are, and how many are there.
What if delegates could control block production rate and/or block capacity in order to deal with pending transactions faster.
Something like delegate A sees that there are over 500 pending transactions, so he issues a block with indicator that block creation rate should be increased.
Now the whole network can agree or disagree - they all have necessary data to verify.
Next in queue, delegate B validates this aswell and if he agrees, he confirms A's suggestion, and delegate C will produce next block faster.
Then, if pending operation decreases to 100, delegate D can suggest decreasing rate to normal, delegate E can confirm, and delegate F can produce a block at normal rate.
There could be more than one thresholds for pending operations amount so that rate and/or capacity of a block could have many shifting gears.
I don't know if it's worth something, or am I just making a fool of myself