Defichain is standing for 10 minutes or more very often.

[wmbst]

What happened:

since the last hardfork we see defichain standing for 10 minutes or longer quite often. Since the speedy miner we have to live with jumping block times, but since the last hard fork, this is extreme. for example now last block 2229281 is about 24 minutes with no new block found. Then we have new block 2229282 which states it was within one minute, but in reality it was 24 minutes later. (it also explained the huge numbers of transactions) I see this behaviour every day now. Previous it was just once every couple of month.

What you expected to happen:

Blocks variance should not be that extreme. And it definitely was way better before.

Edit: Changed from 20 minutes to 10 minutes, as this is more accurate.

[defichain-bot]

@wmbst: Thanks for opening an issue, it is currently awaiting triage.

The triage/accepted label can be added by foundation members by writing /triage accepted in a comment.

Details

I am a bot created to help the DeFiCh developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the DeFiCh/oss-governance-bot repository.

[Stonygan]

I've made a little evaluation, from my point of view there are no major changes since the hardfork in blocktimes.

Longest Blocktimes before GW:

Longest Blocktimes after GW:

Maybe some blocks need much more time, but minimum one time every day a block needs more then 20 minutes, after Hardfork and before, too. I think the problem has nothing to do with the last Hardfork.

For own Statistics you can download the Logs:

https://mydeficha.in/stats/blocktime_after_gw.log

https://mydeficha.in/stats/blocktime_before_gw.log

[wmbst]

Thanks a lot for your work and the data. This is very very helpful as I am not a technican, but for me it definitely feels much slower than before and I don't think I just got very unlucky and always hit the slow blocks.

I made a diagram with your data, and for me it shows, that since the hard fork we have about 3 times more slow blocks than before.

You can see it quite good if you just look at the blocks slower than 10 minutes. about the same number of blocks in 1/3 rd of the time.

But you could be absolutely right, that it did not start with the hard fork, but about 1 week before. And it is not the hard fork itself, but the higher number of vaults? (Just guessing)

[wmbst]

Just saw it in your table. It shows the same. Number of blocks slower than 10 minutes: before hard fork: 0,031% after hard fork: 0,10%

So the number of very slow blocks is now 3 times more than before.

And this fits very good to my experience with the LW right now. Perhaps full node users don't see it, as most transactions go immediately to the mempool. The LW gives an "error" message after an timeout (sent but not confirmed)

[RoMi1981]

Is there a plan to improve that issue somehow? LW and EVM Wallet users will face this issue direct when they have to wait until their tx finishes. Sometimes this takes longer than 10 minutes until the next block arrives and then there are a lot of blocks in a row... (with short block time)

This issue happens often, here a recent Testnet3 example: