Crescendo is coming to Flow this July! Flow supercharges the Ethereum ecosystem with full EVM-equivalency and the power of Cadence 1.0.
Flow Roadmap

Scaling Flow

Last updated: Aug 8, 2023

On average, Flow sees 500,000-1 million transactions per day, with sufficient room to support 10 times transaction throughput growth – even with sequential transaction execution. While scaling transactions per second (TPS) for the core protocol will always be a high priority, it is essential that the protocol is also able to scale for state growth as more data is being stored on-chain. 

With the below upgrades, the barriers to running a node and data accessibility are significantly reduced. Users will benefit from secure, permissionless access to the network without sacrificing noticeable hardware requirements on their computer. They will not have to rely on third parties for data or network access when they use apps.


Support massive state sizes

Achieving ultimate scalability through concurrent execution

Secure and permissionless access for everyone

Current progress

Atree register inlining is estimated to be completed by the end of August 2023. State migration will still need to be accomplished before deploying this optimized execution state, which will take place during a future Flow network upgrade.

A proof of concept trial for storing the execution state on disk concluded with encouraging results, with less than a 60 percent reduction of data access speeds from storing the execution state in Pebble DB on SSD. The design is being workshopped to complete the second milestone in Q3 2023, laying the foundation for reduced execution node memory usage by approximately 50 percent.

Foundational work for concurrent execution concluded with refactoring the execution runtime (FVM) to ensure Flow can run multiple execution threads with no side effects. The UUID generation that caused transaction conflicts was also refactored, and work on refactoring further causes of transaction conflicts and concurrent execution blockers – including fee deduction, side effects caused by programs cache, and Cadence type checker integration – has begun.

Later this year, the work to enable trustless access to the complete set of the execution data available on the public network, with access and observer nodes enabled to execute scripts locally should be wrapped up.