Key Takeaways
- Optimistic Execution (OE) is now part of Cosmos SDK, enhancing block creation efficiency.
- Load tests on Sei Network show OE reduces block processing time by ~300ms, with potential for sub-1-second blocks on fast networks.
- The platform aims to further optimize OE by reducing execution abort time and improving context handling for block execution.
Optimistic Execution (OE) is now on Cosmos SDK, and users cannot be more hyped up for this latest update. OE involves processing a block in advance, ensuring a prepared response when requested by the consensus layer. This approach is called optimistic because Execution begins, even though rejection is infrequent in most cases. Now, that’s an update that we can get behind on! Read on to find out more.
The Integration
The implementation of OE is currently accessible within the Cosmos SDK and is set to be included in the upcoming v0.50 release. Optimistic Execution empowers Cosmos SDK chains to create blocks at an unprecedented speed, pushing the boundaries of block processing times and overall efficiency.
In load tests conducted on the Sei Network, the introduction of Optimistic Execution resulted in a reduction of approximately 300 milliseconds in block processing time. When applied to fast block-producing networks like Injective, OE has the potential to facilitate the generation of sub-1-second blocks effortlessly.
The platform is now actively exploring avenues to enhance the implementation of Optimistic Execution. Among the primary focuses is reducing the time needed to abort a running execution and other potential improvements.
In the future, they plan to make modules aware of a cancellable context to enable transactions to return as soon as Execution is aborted. Moreover, they are focused on caching all the essential context for block execution, eliminating the need to wait for the completion of the previous (aborted) Execution. Let’s see how this new update turns out!
Source
