Build beyond EVM, on Flow: where web3 goes mainstream
EVM on Flow
Scale EVM through Flow's protocol and build beyond Solidity constraints with Cadence. This upgrade makes the Flow network available to EVM based projects. Full EVM equivalence on Flow gives developers the complete flexibility to deploy any Ethereum dApp with no changes to contract code to take full advantage of the functionality native to Flow.
This major upgrade to the Cadence programming language enables full EVM equivalence, allowing Flow to host EVM-based smart contracts, platforms, tooling, and utilities natively and fully composably with the Cadence environments.
Crescendo also completes a series of` performance improvements to the core protocol solidifying Flow as the best home for consumer-scale onchain experiences. Included in the release itself is Atree register inlining, a protocol upgrade increasing state storage efficiency by nearly 2x and reducing memory usage by 40%, which will drive significant improvements for network performance.
Dynamic Protocol State is the foundation for countermeasures such as slashing misbehaving nodes or entirely revoking their authorization to participate. Flow continues its journey towards full autonomy and Byzantine Fault Tolerance (BFT) via Dynamic Protocol State.
Interact with EVM native platforms directly from Flow and extend EVM applications with Cadence.
Tap into intuitive UX for mainstream audiences with protocol-native account linking.
Bring the magic of web3 straight to your community’s mobile device with Flow’s mobile SDK.
Flow’s architecture makes frontrunning or other attacks impactical which improves the user experience by eliminating failed transactions and invisible fees.
Flow accounts support multiple signers for improved user and developer experience.
Interaction Templates give Cadence developers a means to declare static metadata about transactions they ask users to sign.
With a low to no barrier of entry for multi-chain providers. On and off ramps and cross-chain connections will be directly available on Flow. Drastically improving liquidity and accessibility for Flow's DeFi ecosystem.
Roll-ups, data availability shards, among other scaling improvements are live, battle tested, and ready for you on Flow.
The Crescendo upgrade
I am a developer
I am a node operator
It will include a migration of execution state. For that reason it is likely to require a longer network outage than usual. More details will be available closer to upgrade time.
I am not (yet) a developer/builder, but I am interested in building on Flow
I am a user of a dapp on Flow
The dapp team should handle everything without a need for an end user to move their assets or sign transactions. But, if you’re not sure, you can reach out to the team behind the dapp and ask them about their plans to upgrade to Cadence 1.0.
Won’t the additional execution load disrupt the network?
It’s important to acknowledge how localized and non-disruptive these changes are to the rest of Flow. We have a single new smart contract to run the EVM runtime environment and a new kind of client (the gateways) that interact with the existing Flow Access API without modification. Integrating the EVM runtime environment into the Flow execution environment and the gateway is a lot of work, but we can leverage a whole lot of existing open source code from the Ethereum community to handle the hardest parts. We can provide full EVM equivalence on Flow without disrupting any existing applications or tools built with Cadence.
Are you sure this is full EVM equivalence and not just compatibility?
Learn how here