We’re working on blocksync (which is a peering issue under the hood) before increasing block size further, so its a very high priority. We have a good plan to fix this soon Fix getting to the tip of large chains quickly · Issue #1727 · celestiaorg/celestia-core · GitHub
It does feel unfair to get jailed when you responded in time. I don’t think it’s fair to expect insane multi node setups to avoid downtime either.
I still feel like the point of Jailing isn’t clear, or like I’m going crazy and explaining it wrong. It’s to keep the network healthy and reward validators who can keep their node up. Jailing isn’t bad. Being jailed for less than 24 hours should have essentially 0 consequences.
I will find whoever is in charge of the delegation program and ask them to fix it, but increasing the parameter is not addressing the root of the problem. Picking parameters to address symptoms is a terrible practice. We do our best to avoid that for as long as we can.
Increasing this parameter is bad for rollups by directly increases the number of missed slots, decreasing throughput and increasing finality. If it’s bad for rollups, it’s bad for the network.
Please wait to vote on this parameter until the peering (and therefore blocksync and statesync) are fixed.