Aug 18, 2026

I've verified that the 8GB min scenarios remain operational and performant despite the address index, as long as we crank up the load factor to keep table heads resident with some headspace for bodies. A high LF would doom validation, but the address index is only used by wallets and remains very fast for that scenario even at LF50. So basically we can default address index to on, and autotune table creation to make it work/optimal.