Solana is transitioning to an era of producing five blocks per second, reducing the target block time on the network to 200 milliseconds; however, this speed increase will also raise the workload for validators.
The Solana network has reached the final stage of a seven-week update process aimed at improving network performance. The update, codenamed SIMD-0525, aims to reduce the target block time from 250 milliseconds to 200 milliseconds.
In Solana, the target block time was 400 milliseconds until August. The network switched to 350 milliseconds on August 21st, 300 milliseconds on August 28th, and 250 milliseconds on September 18th. With the final phase, the initial target time will be halved.
Know when your
coins moveAlerts, real-time prices, and market news — all in one app
4.8 based on 40K reviews in the App Store and Google Play
The new structure theoretically creates the opportunity to produce five blocks per second. Thanks to shorter timeframes, wallets, decentralized exchanges, and other applications will be able to access up-to-date information on the chain more quickly. The time it takes for transactions submitted by users to be included in a block may also be reduced.
However, the change doesn’t automatically double Solana’s total theoretical processing capacity. The computational limit per block will be reduced from 37.5 million units to 30 million units. Blocks will be generated more frequently, but each block will carry less computational work.
Faster blocks may make some latency-driven transactions, which exploit price fluctuations across different exchanges, more difficult. Conversely, this could increase operating costs and strain network connectivity as validators will need to submit votes more frequently.
The validity period of the current block references used in transactions will also be shortened. This could create timing issues, especially for transactions requiring hardware wallets, manual confirmation, or offline signatures.
The previous target of 250 milliseconds resulted in an actual average of around 266-269 milliseconds, indicating a possible discrepancy between the target and actual performance. Therefore, how the 200 millisecond setting performs under real network conditions, how many block opportunities validators miss, and whether transaction failures increase will be closely monitored.
*This is not investment advice.
Leave a Reply
You must be logged in to post a comment.