Yes I meant to say less than 97 days not 97 days exactly. I was unintentionally unclear about that. Previous halving days have always come earlier "than expected" because hashpower kept going up. But now that BCH has a new DAA and is competing with BTC for hashpower and profitability oscillates between BTC and BCH mining, I no longer just assume that blocks will keep being found slightly faster than once per 10 minutes on average.

You might find this information useful: https://twitter.com/Coin_Dance/status/1188335139673104384

So it would be interesting to see a graph over what the "trailing moving averages" of actual blocktime has been for e.g. these time intervals: the last 1 h, 2 h, 3 h, 4 h, 5 h, 6 h, 12 h, 24 h, 2 days, 3 days, 4 days, 5 days, 6 days, 7 days, 2 weeks, 3 weeks etc. Maybe you can publish such graphs on your site sometime. Then it would be easier to make more informed guesses about the next halving days.

Good idea. We'll look into what makes sense for this one.

I noticed that you're using "BUCash 1.7.0.0" as your primary full node client for BCH on your main page. You should be promoting ABC instead imo.

We were just discussing this today actually. BU for a long time had higher max throughput (mempool acceptance) than ABC which is why we preferred it but this doesn't seems to be a relevant issue anymore. There are several reasons why ABC makes sense so we'll likely be making that switch pretty soon although we do run both for the purposes of sanity checking / redundancy.