Technology
The ICP Reverse Gas Model Explained
On most blockchains, every user pays gas for every transaction. The Internet Computer inverts this: the canister — the app itself — pays for its own execution out of a prepaid balance of cycles. Users interact for free. Here is how the reverse gas model works and why it changes the app experience.
August 16, 2026 · 5 min read
The classic gas problem
On Ethereum or Solana, a user calling a smart contract pays a transaction fee denominated in the network's token. The fee can spike with congestion, the user needs to hold the gas token, and a poorly written frontend can quietly burn a user's balance in failed transactions. For a mainstream consumer, that friction is one of the biggest reasons blockchain apps never feel like ordinary websites.
How the reverse gas model works
The Internet Computer's model is closer to a prepaid cloud account than to gas:
- The developer buys ICP and converts it into cycles in the NNS.
- Cycles are credited to the canister's balance — 1 trillion cycles = 1 XDR.
- Every update call, byte of storage, and outcall burns a small amount of that balance.
- Users call the app without ever paying; the canister covers the cost.
Read-only queries are free on top of that. Because queries skip consensus, they burn no cycles at all — so checking a balance, searching a directory, or loading a dashboard costs nothing, even for the developer.
What it feels like for users
From the user's side there is no gas token to hold, no fee slider, no "approve" popup. Sign in with Internet Identity and the app just works — sending ICP, creating a bucket, or tipping a profile costs the user nothing extra beyond the amount being moved. This is the biggest reason ICP apps can match the onboarding ease of a Web2 product.
What it means for developers
The trade-off is that the developer carries the cost and must monitor it. A canister's cycle balance is like a utility account — popular apps burn cycles fast, and an empty balance freezes the canister. Good operations on ICP mean topping up cycles, watching burn rates, and (in products like ICPay Cloud) charging users a product price that covers the underlying cycles.
That last point is the revenue model in miniature: an app can charge its users in ICP for storage or services while the actual infrastructure cost is paid in stable-priced cycles. The margin between what users pay and what cycles cost is the business.
Why it is deflationary
Converting ICP into cycles burns the ICP. Every conversion permanently removes tokens from supply, which is deflationary when the network is busy. Meanwhile cycles themselves are stable — pegged to XDR — so infrastructure costs do not swing with ICP's market price.