Skip to content

docs(cycles): clarify cost predictability section #144

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
marc0olo merged 1 commit into from
Apr 24, 2026
Merged

docs(cycles): clarify cost predictability section #144

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/concepts/cycles.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,7 +77,7 @@ These responsibilities can be automated. Tools like [CycleOps](https://cycleops.

The XDR peg and flat per-resource pricing make ICP costs predictable:

- **No fee auctions**: there is no bidding for block space. Cycle prices are set by the NNS and change infrequently.
- **No surge pricing**: cycle prices are set by the [NNS](../concepts/governance.md) (ICP's on-chain governance system) and change infrequently. There are no congestion fees.
- **No per-transaction fees for users**: apps absorb all costs, like SaaS businesses absorb server bills.
- **Stable unit economics**: because cycles are pegged to XDR (not ICP price), infrastructure costs remain consistent even when ICP token price swings.

Expand Down
Loading