taler-docs

Documentation for GNU Taler components, APIs and protocols
Log | Files | Refs | README | LICENSE

commit 5a80cb9e577fa1f43dfefdebd53cbce245c44df1
parent 74597ed06bcdf8b3b1a99e277d08106b7199fa41
Author: Mikolai Gütschow <mikolai.guetschow@tu-dresden.de>
Date:   Wed,  8 Apr 2026 17:24:05 +0200

api-exchange: fix high-level description of refresh

Diffstat:
Mcore/api-exchange.rst | 8++++----
1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/core/api-exchange.rst b/core/api-exchange.rst @@ -327,14 +327,14 @@ and prove that the age restriction was set correctly. Refreshing ---------- -Refreshing creates ``n`` new coins from ``m`` old coins, where the sum of -denominations of the new coins must be smaller than the sum of the old coins' -denominations plus melting (refresh) and withdrawal fees charged by the exchange. +Refreshing exchanges one old coin against ``n`` new coins, where the sum of +denominations of the new coins must be smaller than the old coin's +denomination plus melting (refresh) and withdrawal fees charged by the exchange. The refreshing API can be used by wallets to melt partially spent coins, making transactions with the freshly exchangeed coins unlinkabe to previous transactions by anyone except the wallet itself. -Refreshing is a two step process, consisting of +Refreshing is a two-step process, consisting of 1. the **melting** of the old coin, together with ``kappa`` batches of blinded planchets candidates,