Flow Network Resumes Block Production After Attack as Phase 1 Restoration Opens Cadence Environment with EVM Read-Only Mode

Flow Network has resumed block production following a recent attack that temporarily disrupted consensus and service availability. The restart marks a controlled recovery step after the incident, with validators gradually rejoining the network and block finality returning under monitored conditions. The incident prompted an orchestrated restoration plan that prioritized node integrity, ledger consistency, and developer access to smart contract environments.

As part of the initial recovery actions, the team opened a Phase 1 restoration window that enables developers to access the Cadence smart contract environment in a restricted configuration. This environment is being offered in an EVM read-only mode, allowing developers and auditors to inspect contract state and transaction history without executing state-changing operations. The read-only capability aims to strike a balance between transparency for debugging and protection against unintended writes while the wider network continues to stabilize.

Flow validators are monitoring synchronization metrics, chain height parity, and mempool integrity as they bring the network back to full operation. The staged approach reduces the risk of cascading failures; it also enables the project to detect residual issues in transaction propagation or consensus safety before enabling full write access across all environments. Network operators are also coordinating with external node operators and third-party indexers to ensure ecosystem services reflect the recovered state accurately.

Company Dapper Labs, a primary contributor to Flow’s ecosystem tooling, has been referenced by community posts as engaging in diagnostics and ecosystem coordination. Company Dapper Labs and other service providers are participating in post-incident reviews and alerting downstream applications about the limited write policy in the Cadence environment.

Implications for developers and users: The EVM read-only mode means that decentralized applications (dApps), wallets, and explorers can query contract storage, confirm transaction inclusions, and run off-chain analyses without risking further state mutations. For traders and market participants, the immediate effect is reduced on-chain activity originating from Flow smart contracts, which can temporarily affect liquidity for Flow-native tokens and secondary markets that depend on on-chain operations.

Security and forensics: The post-attack phase emphasizes forensic data collection and deterministic replay where safe. Operators are capturing logs, consensus proofs, and validator telemetry to build a root-cause analysis. This information will be essential for implementing hardening patches and refining incident response playbooks.

Market outlook: While block production has resumed, market participants should remain cautious. The phased restoration reduces systemic risk, but residual uncertainty may persist until full write access is reinstated and independent audits confirm that vulnerabilities have been mitigated. Traders should watch for restored on-chain activity as a signal for normalized liquidity and confidence.

Next steps: The team plans incremental enabling of write operations following validation of chain health metrics and successful audits. Community channels and official status pages will communicate milestones and timelines. Stakeholders should follow official channels for verified updates and avoid relying on unconfirmed third-party reports.

Editor note: This report focuses on technical recovery procedures, developer access restrictions, and short-term market implications. It aims to provide clear guidance on what the EVM read-only Cadence environment means for different ecosystem actors during Phase 1 of the restoration.