Tomorrow, SIMD-0286 activates at Epoch 1009. Here is how this would impact validators and applications. Validators: - Heavier maximum work done per block. If you are running on lower-end hardware, you could likely see increased execution times as well as replay degradation. - Ledger growth rises only to the extent blocks actually fill, so day-one impact is limited. But provision against the higher ceiling rather than current averages is recommended. The same goes for RPC providers, indexers, and archival nodes. Applications: - More transactions land per block. High-intensity programs like order-book DEXs get more room to operate before blocks fill, though the per-transaction cap of 1.4M CUs is unchanged. - Apps with distributed activities across accounts benefit the most. - Apps on one hot writable account are still bottlenecked as that account still caps out at 12M CUs. if SIMD-0306 passes, the per-account cap would move from a static 12M to 40% of the block limit (40M at 100M), which would actually relieve hot-account congestion. - More block space means less fee competition during congestion, so lower priority fees and fewer retries. If your app hardcodes fees or estimates from 50M/60M data, revisit it, otherwise you'll systematically overpay. - Scheduled/automated execution such as agentic txns are going to be more reliable during congestion. For app developers: nothing breaks, no migration needed, existing transactions and blocks stay valid, and it is important to highlight that the throughput gain from this is contingent on validators keeping up.