Buy & Swap Flow (FLOW)

One coin, several jobs

Flow's tokenomics page lists the jobs FLOW does on the network. Validators and delegators stake it to participate, and their service is rewarded in FLOW. Every transaction fee is paid in FLOW, from deploying a smart contract to creating an account or transferring tokens and NFTs.

FLOW also reserves storage: each account must keep a minimum balance to cover the space its data occupies on-chain. Beyond that, the page lists FLOW as a medium of exchange inside Flow applications, as collateral in DeFi apps, and as the principal coin for voting on future protocol and ecosystem development.

Bundling these jobs into one coin keeps the accounting simple for users and developers. The same coin that pays for a swap also pays the tiny fee that carries it, and the same coin that secures the chain through staking is the one applications quote prices in.^{[1], [2], [3]}

Fees measured in compute units

Flow's documentation explains that transaction fees are priced in compute units: a measure of the effort needed to include and execute a transaction. Compute units play the role that gas plays on Ethereum-style networks, and the final fee is the transaction's compute units multiplied by the current unit price, payable in FLOW.

A fee is charged whether a transaction succeeds or fails, which protects the network against spam. Senders can also set a compute limit when submitting, which caps how much fee a runaway transaction can spend.^{[4], [5]}

Cadence: Flow's own language

Flow's smart contracts are written in Cadence, a programming language created for the network and documented in its own language portal. The Crescendo upgrade delivered Cadence 1.0, which Flow describes as adding fine-grained access controls and safer, more efficient code execution.

The FLOW coin itself is defined by a Cadence contract. The developer portal publishes the FlowToken contract and its addresses across networks, including the mainnet address 0x1654653399040a61, so anyone can confirm they are looking at the real contract.^{[7], [6]}

Crescendo adds a full Ethereum lane

The Crescendo upgrade introduced Flow EVM, which Flow's documentation describes as EVM-equivalent: Ethereum applications and contracts can be deployed to Flow without code changes. The Flow EVM mainnet runs as chain ID 747 with FLOW as its currency.

Crescendo also shipped protocol-level improvements. Flow's upgrade notes describe Atree register inlining, which nearly doubled state storage efficiency and reduced memory usage by 40 percent, and a Dynamic Protocol State that underpins countermeasures such as slashing misbehaving nodes.^{[8], [10], [9]}

Staking in weekly epochs

Flow secures the network through proof of stake, and its documentation describes staking and delegation as running in epochs: recurring periods during which a set of nodes commits its stake and does its work. Token holders who do not run a node can delegate their FLOW to one.

Staking is what ties FLOW's economics to the network's security. The more value staked and delegated, the more an attacker would need to acquire to influence consensus, and the rewards for honest work are paid in the same coin.^{[11], [12]}

Two lanes, one chain

Cadence and EVM are not separate networks. Flow's documentation presents them as two environments on one chain: a Solidity contract on Flow EVM and a Cadence contract on Flow are secured by the same validator set and both use FLOW for gas.

For users this mostly stays invisible. A wallet or an app picks the environment it needs, and the coin that settles everything underneath is FLOW either way.^{[8], [4]}

How the validator set develops

Flow's documentation explains the epoch and staking machinery, and its governance design lists FLOW as the voting coin, but the size and composition of the active validator set change over time and are only visible on the live network. How decentralised that set will become is UNKNOWN from public sources.

It is not predicted here.^[11]