Authors: Alexander Hentschel, Dieter Shirley, and Layne Lafrance
Year: 2019
Project: Flow
License: No paper-specific reuse license is stated in the paper or arXiv record.
Official source: Flow: Separating Consensus and Compute (2019 paper)
This page covers the 2019 research paper Flow: Separating Consensus and Compute. It explains an early scaling proposal for Flow; it is not a complete description of the current network, its programming languages, or every later protocol change.
Publication and Scope
Alexander Hentschel, Dieter Shirley, and Layne Lafrance posted the paper on September 12, 2019. Its central idea is to separate transaction ordering and consensus from transaction execution. The proposal aims to use specialized nodes more efficiently while keeping applications on a shared state, rather than splitting application state across shards. The paper says a complete system would still need additional mechanisms for verifying execution, specifying consensus, and incentivizing node behavior.
What the Paper Reports
The paper reports a throughput increase of up to 56 times in a proof-of-concept simulation using 32 globally distributed nodes. This result compares a simplified setup that separates consensus and computation with one that combines them; it is not a mainnet benchmark or a promise of production throughput. The authors note that the simulation omits extra steps needed to verify computation and commit results. The paper’s experimental setup and limitations are described in its performance-simulation section.
From the Proposal to Flow’s Current Architecture
The 2019 paper focuses on two roles: consensus nodes order transactions, and execution nodes compute their results. A companion paper later examined distributed execution verification, and a separate 2020 paper covered block formation and execution. These are related publications, not additional authors or sections of the 2019 paper: the execution-verification paper and the block-formation and execution paper.
Current Flow developer documentation describes five specialized roles: Collection, Consensus, Execution, Verification, and Access. Their duties now include gathering transaction collections, ordering blocks, executing transactions, checking execution results, and routing client requests. This current design should not be collapsed into the original paper’s two-role model. Flow’s network-architecture documentation describes the current roles.
Cadence and EVM Support
Cadence is part of Flow’s later development, not the subject of the 2019 paper. Its current documentation describes a resource-oriented language with ownership and capability rules for digital assets. These language features can constrain how contracts handle resources; they do not make a blockchain implementation immune to software bugs. Flow’s September 4, 2024 Crescendo upgrade introduced Cadence 1.0 alongside EVM equivalence, so Flow now supports both Cadence and EVM-based development. Cadence’s language documentation and Flow’s Crescendo announcement describe these later features.
Security and Limitations
On December 27, 2025, Flow reported that a vulnerability in the Cadence runtime had allowed counterfeit tokens to be created. Its technical postmortem estimated about $3.9 million in extracted assets and said validators halted the network before it resumed on December 29. Flow’s postmortem states that existing user balances were not accessed or compromised; that is the project’s account of the incident. On January 30, 2026, Flow reported that 87.4 billion counterfeit FLOW tokens had been destroyed. The incident shows why a resource-oriented language or a specialized node architecture should not be treated as a guarantee against implementation flaws. Flow’s technical postmortem and its final remediation update provide the project’s chronology and findings.
Social Media Sentiment
A December 28, 2025 discussion in r/CryptoCurrency about the Flow incident showed strong skepticism about the network response and what it meant for decentralization. Commenters debated the recovery process and user trust; some characterized it as evidence of centralized control. This was one discussion during an active incident, not a representative survey or a current measure of Flow users’ views.
Last updated: 2026-10
Related Terms
Flow · NFT · Proof of Stake
See Also
HotStuff Whitepaper · Ethereum Beacon Chain / Gasper Whitepaper · Algorand Whitepaper
References
Hentschel, A., Shirley, D., and Lafrance, L., “Flow: Separating Consensus and Compute” (2019) — the original paper and its simulation results.
Hentschel et al., “Flow: Separating Consensus and Compute — Execution Verification” (2019) — a related paper on distributed verification.
Hentschel et al., “Flow: Separating Consensus and Compute — Block Formation and Execution” (2020) — a separate follow-on publication.
Flow Developer Portal, “Flow Network Architecture” — current descriptions of Flow’s node roles.
Flow, “Flow Security Incident 27th December: Technical Post-Mortem” — the project’s incident and recovery report.
Last updated: 2026-10-11