The last gain from 2025: On Tue, the team detected and applied a config change that reduced the L1 finality time by 20 minutes. This change was not in S-Two itself, but rather in SHARP - the infrastructure that wraps S-Two for aggregation and submission proofs. Two days ago, I said that "now, when we have an active ecosystem of apps, we can focus our work on the ecosystem demands". This is exactly what happened here - we got feedback that L1 latency times are a pain point. We initiated a review process to determine how we can cut it and discovered several low-hanging fruits, as S-Two is far from being the bottleneck. And changes that are much more meaningful than 20 minutes (though a bit more complicated) are coming soon.