Solana News

Solana mainnet slot time set to 350ms at epoch 1020, Brennan Watt says

Solana’s mainnet is moving to a 350-millisecond slot time, with Anza CEO Brennan Watt saying the change becomes effective starting at epoch 1020. In posts on X, Watt described the update as the first slot time reduction on mainnet and warned developers that some SDK constants have not yet been updated to reflect the new timing.

Watt said applications that depend on constants such as DEFAULT_MS_PER_SLOT should be checked against epoch boundaries during the transition. He also noted that the feature follows a delayed activation pattern, with a pending state in epoch E, activation in E+1 and full effect in E+2.

Developer checks may matter during the transition

The practical issue, according to Watt, is that software may temporarily rely on timing assumptions that no longer match mainnet behavior once the change is live. He said the team plans to update the relevant SDK values in a later release, while longer-term plans call for these parameters to be placed on-chain so clients can query them directly.

The posts did not describe a broader user-facing rollout beyond the timing change itself. Based on Watt’s comments, the immediate focus is on avoiding mismatches for applications that read slot timing from SDK constants rather than from the network state.

Other coverage echoed Watt’s timeline for epoch 1020 and the warning that developers may need to adapt their integrations during the transition period. No separate official mainnet activation notice was included in the material reviewed for the update.