taler-docs

commit c9c8c0c1653acdac88d7e979cc43adc90fce5e7c
parent 63945799842c5ae3cfb6fbe7a323622092364091
Author: Özgür Kesim <oec-taler@kesim.org>
Date:   Sat,  3 May 2025 16:06:38 +0200

[exchange] move description of old linking protocol

Diffstat:
M
core/api-exchange.rst
 | 
11
+++++------

1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/core/api-exchange.rst b/core/api-exchange.rst
@@ -3442,12 +3442,6 @@ 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.
 
-However, the new coins are linkable from the private keys of all old coins
-using the ``/refresh/link`` request.  While ``/refresh/link`` must be implemented by
-the exchange to achieve taxability, wallets do not really ever need that part of
-the API during normal operation.
-
-
 .. _melt:
 .. http:post:: /melt
 
@@ -3670,6 +3664,11 @@ the API during normal operation.
   various arguments are given ``kappa``-times in this step.  At present ``kappa``
   is always 3.
 
+  The new coins are linkable from the private keys of all old coins using the
+  ``/refresh/link`` request.  While ``/refresh/link`` must be implemented by
+  the exchange to achieve taxability, wallets do not really ever need that part
+  of the API during normal operation.
+
   The base URL for ``/coins/``-requests may differ from the main base URL of the
   exchange. The exchange MUST return a 307 or 308 redirection to the correct
   base URL if this is the case.