O3.1.1 - Milestone 2a: Limit Increase Readiness

[anupsdf]

Outcome

All required changes identified by the 200 SAC TPS readiness evaluation are implemented, released, and validated. Core, Platform, and Wallets either:

• complete the changes needed to support the proposed network-limit increase;
• confirm no changes are required because the system already passes evaluation;
• or, document that only a partial limit increase is currently supportable.

By the end of this milestone, the network-limit proposal is ready for execution, including technical validation, SLP acceptance, SDF infrastructure readiness, and external communication.

Exit criteria

• Required changes for Core, Platform, and Wallets are implemented and released in stable versions.
• SDF infrastructure is updated to support the stable versions and proposed limits.
• Teams that require no changes explicitly document a no-op/pass result.
• Milestone 1.b evaluation is re-run using stable versions, not prototypes. Re-run confirms that required SLAs are met for the proposed network limits.
• If full 200 SAC TPS support is not possible, the supported partial limit is documented with data. If no safe partial limit is feasible, blocking bottlenecks and required follow-up work are documented.
• SLP is proposed, presented to the community, and accepted.
• External communication is complete, including notifying Tier1 operators of the upcoming upgrade.
• Rollout plan, monitoring plan, and rollback/kill-switch plan are reviewed and ready for Milestone 2.b.