Flow

flow
CoinYQ Dossier

Flow grew from CryptoKitties into a four-role blockchain

Flow turned CryptoKitties' congestion lesson into a chain where four node roles and two execution environments share one economic asset. FLOW secures that machinery, but its balance does not erase the Foundation, service-account and operator coordination visible in the network's change process.

A viral game became an architecture brief

CryptoKitties' 2017 surge showed the Axiom Zen team that consumers would use blockchain applications—and that transaction cost, throughput and slow product upgrades could break the experience. After Dapper Labs was spun out, the group began Flow rather than treating the episode as a temporary traffic spike.

The important inheritance is a design problem, not a claim that one cat game caused every later scaling system. Flow's founders asked how a composable base layer could take consumer load without splitting applications across shards or making every node execute every instruction.

Four jobs move one transaction

Collectors batch transaction data, consensus nodes establish order, execution nodes compute the state transition, and verification nodes re-check that work. Flow intentionally gives execution low redundancy because deterministic computation can be verified, while ordering retains higher redundancy because there is no single naturally correct order for competing transactions.

This is also Flow's sharpest operational trade-off. Its vision describes ten or fewer powerful execution nodes in a mature example. Anyone can run an unstaked Observer node, yet block-producing roles require from 135,000 to 1,250,000 FLOW depending on the job. Reading the chain, validating it and deciding its ordered state are not identical powers.

Cadence kept its resources when EVM arrived

Cadence makes a digital asset a resource: code cannot casually copy it or discard it, and capabilities narrow who may access it. Crescendo on September 4, 2024 brought Cadence 1.0 and an EVM-equivalent environment in a coordinated upgrade that included a planned maintenance window.

Flow EVM uses chain ID 747 and FLOW for gas. It broadened the tools developers could use without replacing Cadence or issuing a second native coin. The result is one base network with two programming models—and cross-environment complexity that users should not mistake for two independent security domains.

A 1.25-billion genesis did not create a fixed cap

Genesis assigned 400.2 million FLOW to the ecosystem fund, 374.8 million to backers and the community sale, 250 million to Dapper Labs and 225 million to the development team. All genesis allocations were unlocked by October 2023. Official pages disagree on whether genesis occurred in June or October 2020, so the defensible date is simply 2020.

Supply then follows an epoch formula rather than a hard ceiling. Fees fund a target reward pool equal to 5% of total supply annually; issuance covers the shortage. Fees offset minting instead of being burned. The Foundation's completed destruction of 50,343,896.87 FLOW in February 2026 reduced supply once, while its proposed additional 50 million acquisition remained a plan. Neither event rewrote the epoch formula.

A proposal repository is not a shareholder register

FLOW can be staked or delegated to secure the protocol, and FLIPs provide a public path to propose changes. Yet governance FLIPs explicitly include node allowlisting, fee changes and actions with the service account; their documented process relies on authors, sponsors, maintainers, a review committee and community review.

That machinery makes control inspectable without turning every token into a binding corporate vote. The reviewed sources establish network utility, not equity in Dapper Labs or the Flow Foundation, a claim on treasury assets or protocol revenue, or fixed-price redemption. A holder evaluating FLOW must watch both on-chain parameters and the people and keys that coordinate their revision.

How the project changed

  1. 2017
    CryptoKitties meets Ethereum congestion

    The application's demand exposes scaling, cost and product-friction limits that the team later frames as Flow's starting problem.

  2. 2020
    Flow genesis creates 1.25 billion FLOW

    Official pages agree on the amount but conflict between June and October for the genesis month.

  3. December 2020
    Validator rewards begin

    Mainnet staking rewards activate, connecting FLOW issuance to validator and delegator service.

  4. October 2023
    Genesis allocations finish unlocking

    The technical tokenomics page reports all original allocation buckets fully unlocked.

  5. September 4, 2024
    Crescendo joins Cadence 1.0 and Flow EVM

    A coordinated mainnet upgrade introduces EVM equivalence while retaining the Cadence environment.

  6. December 8, 2025
    Transaction fee parameters change

    Higher fees fund more of the reward pool; net deflation remains conditional on sustained 250 TPS.

  7. February 23, 2026
    Foundation completes a 50,343,896.87 FLOW destruction

    The one-time burn is verified on-chain; the separately announced additional 50 million acquisition remains forward-looking in the source.

Evidence and primary sources

Last evidence review: 2026-09-05

What is Flow?

Flow is a proof-of-stake Layer 1 conceived by people from Axiom Zen and Dapper Labs after CryptoKitties' 2017 demand exposed the cost, throughput and upgrade limits of Ethereum-era consumer applications. Its transaction path assigns collection, ordering, execution and verification to different node roles instead of asking every validator to repeat every computation.

The chain now has two application environments. Cadence stores valuable assets as resources with language-enforced ownership rules. Flow EVM, introduced with the Crescendo upgrade on September 4, 2024, runs Ethereum-compatible bytecode and uses FLOW as gas on mainnet chain ID 747. These are two execution environments on one Flow network, not two unrelated FLOW tokens.

What problem does Flow solve?

CryptoKitties proved demand before it proved infrastructure. The game attracted users who then met congestion, volatile fees and product friction. The team responded with a pipeline: collection nodes batch data, consensus nodes order it, powerful execution nodes compute state changes, and verification nodes re-check the deterministic result. The design keeps more redundancy where ordering can be manipulated and less where a result can be checked.

That choice creates its own question. Flow's protocol vision explicitly accepts a small set of professionally operated execution nodes—ten or fewer in its mature design example—and relies on verification to catch bad work. An Observer node can be run without stake, but the validator roles that make blocks have large, role-specific stake requirements. Accessibility to data and authority in consensus are therefore different kinds of participation.

How does Flow work?

FLOW pays transaction fees, backs account storage, and is staked by validator operators or delegated to them. Current published minimums are 250,000 FLOW for Collection, 500,000 for Consensus, 1,250,000 for Execution, 135,000 for Verification and 100 for Access nodes. Delegation starts at 50 FLOW and the protocol assigns an 8% operator take-rate. Access nodes are staked gateways but earn no rewards and cannot receive delegations.

The 2020 genesis allocation was 1.25 billion FLOW: 400.2 million for the ecosystem fund, 374.8 million for pre-launch backers and the community sale, 250 million for Dapper Labs and 225 million for the development team. All genesis allocations were unlocked by October 2023. There is no fixed maximum supply: each epoch's target reward pool equals 5% of total supply on an annual basis, transaction fees fund it first, and the protocol mints the shortfall. Fees are not burned. The December 8, 2025 fee update is designed to make net issuance negative only at sustained 250 TPS. Separately, the Foundation completed destruction of 50,343,896.87 FLOW on February 23, 2026; its promised purchase of at least 50 million more was a future commitment, not evidence of completion.

The canonical Cadence FlowToken contract is deployed at 0x1654653399040a61. Core contracts also cover fees, storage, staking, epochs and the service account. FLIPs let anyone propose changes, including staking rules, node allowlisting, fees and service-account actions, but maintainers and a review committee shepherd acceptance through community review. The reviewed sources do not describe every FLOW balance as an automatic binding ballot, nor do they establish equity, a claim on Foundation assets or protocol revenue, fixed-value redemption, or corporate ownership.

Key facts

  • Flow emerged from the CryptoKitties team's attempt to solve consumer-application scale and upgrade friction.
  • Collection, Consensus, Execution and Verification nodes divide the transaction pipeline; verification is the check on low-redundancy execution.
  • Cadence and Flow EVM share the Flow network; Flow EVM mainnet is chain ID 747 and uses FLOW for gas.
  • Genesis created 1.25 billion FLOW across four allocation buckets, all unlocked by October 2023.
  • FLOW has no fixed cap under the current reward formula: fees fund the 5% annual target pool first and new issuance covers the shortfall.
  • Delegation requires 50 FLOW and carries an 8% operator take-rate; Access nodes do not earn staking rewards or accept delegations.
  • The FlowToken mainnet Cadence contract is 0x1654653399040a61.
  • FLIP discussion and staking are network participation mechanisms, not documented equity, redemption, revenue or automatic balance-weighted corporate voting rights.
  • The Foundation destroyed 50,343,896.87 FLOW on February 23, 2026; its additional 50 million acquisition was announced as a plan.

Official links

Categories

Related coins

Frequently asked questions

Why did Dapper Labs build Flow after CryptoKitties?

The team's accounts say CryptoKitties' 2017 demand exposed technical, economic and user-experience limits. Flow separated consensus from computation and built consumer-oriented accounts and Cadence around those lessons.

Are Cadence FLOW and Flow EVM gas different tokens?

No. Cadence and EVM are execution environments on the same network. Flow EVM mainnet uses FLOW for gas and chain ID 747; Cadence FlowToken is deployed at 0x1654653399040a61.

How much FLOW is needed to stake?

Delegation starts at 50 FLOW. Node minimums are 250,000 Collection, 500,000 Consensus, 1,250,000 Execution, 135,000 Verification and 100 Access. Access nodes receive no rewards or delegations.

Does FLOW have a maximum supply?

No fixed maximum is documented. Fees pay the 5% annual target reward pool first; the protocol mints any shortfall. High enough fee revenue can eliminate new issuance for a period, but that is conditional on network use.

Does every FLOW holder control protocol upgrades?

The FLIP process welcomes proposals and feedback, but documented acceptance involves maintainers, sponsors, a review committee and community review. Holding FLOW alone is not described as an automatic binding ballot.

Did the 2026 burn make FLOW permanently deflationary?

No such conclusion follows. The 50,343,896.87 FLOW destruction was permanent, but epoch issuance continues whenever fees do not fill the target reward pool. The additional 50 million purchase was a plan in the announcement.

What legal or economic claim does FLOW provide?

The reviewed sources establish fee, storage, staking, delegation and proposal utility. They do not establish equity, Foundation assets, protocol revenue, fixed-value redemption or corporate ownership for holders.

External trackers

Choose a tracking site for Flow: