From 1ebab7f5b67d49da2f6f62312319d4f305e1fea7 Mon Sep 17 00:00:00 2001 From: Marco Walz Date: Fri, 24 Apr 2026 15:11:20 +0200 Subject: [PATCH] docs(cycles): clarify cost predictability section for general audience --- docs/concepts/cycles.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/concepts/cycles.md b/docs/concepts/cycles.md index 7bc8adba..5bcb3f18 100644 --- a/docs/concepts/cycles.md +++ b/docs/concepts/cycles.md @@ -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.