Meet E-Minimmit (Increasing Minimmit's Coding Rate) @AndrewLewisPye found a way to reduce Minimmit's data-expansion rate from 5 to 2.5 (-18% view and -15% transaction latency in bandwidth-limited environments). Check it out now on arXiv (Appendix D):

Because Minimmit advances views after only 2f+1 support (M-notarization), a naïve erasure coding scheme (like the one described in the original paper) would require an expansion rate of 5 (any f+1 participants must be able to recover the block).

When bandwidth is constrained, this expansion rate "overhang" dominates Minimmit's view change win and actually leads to slower transaction latency than two-phase consensus protocols with a higher quorum requirement for view change (but lower expansion rate).

This new work (includes liveness/safety proofs) provides a technique to reduce the required data-expansion rate of Minimmit from 5 to 2.5. All else equal, this leads to a significant boost in performance if you're willing to accept a slightly larger timeout (2Δ -> 3Δ).