Roman Shanin
Roman Shanin
> yes, but you can also define max_instructions or fuel limits to reject those i see, we just need to make sure that consensus `commit_time_limit` is large enough to produce...
> A final important note is that blocks themselves are bounded in size. Each block has a target size of 15 million gas but the size of blocks will increase...
> I believe we should just introduce TooComplex transaction reject reason for cases where it takes more time to produce a block (with even such the only one included) than...
> In that case the complexity is to become tied to fuel and not the time limit/max instructions then Tying to `fuel` might be tricky because for transactions/triggers we have...
Might be also relevant for `Burn` and other operations.
Find older issue with opposite proposal #3924
Should be noticed as well that degradation happens in case of single peer in the network as well.
Hmm, we use `ArrayQueue` which is already [follows](https://docs.rs/crossbeam/latest/crossbeam/queue/struct.ArrayQueue.html#examples) FIFO.
And you want to be able to push transactions back at the beginning of the queue so that they are removed from the queue earlier?
Your idea got me thinking that we can pull something similar without changing type of the queue. Gist is the following: 1) Leader pop transactions from the queue and they...