[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[taler-exchange] branch master updated: -fix doc
From: |
gnunet |
Subject: |
[taler-exchange] branch master updated: -fix doc |
Date: |
Wed, 17 Jan 2024 21:11:25 +0100 |
This is an automated email from the git hooks/post-receive script.
grothoff pushed a commit to branch master
in repository exchange.
The following commit(s) were added to refs/heads/master by this push:
new 129223e1 -fix doc
129223e1 is described below
commit 129223e1d0d4ff54ceff44485afcc4abeaa0ee83
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Wed Jan 17 21:11:23 2024 +0100
-fix doc
---
src/include/taler_exchange_service.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/include/taler_exchange_service.h
b/src/include/taler_exchange_service.h
index 8a59f157..2aeb6469 100644
--- a/src/include/taler_exchange_service.h
+++ b/src/include/taler_exchange_service.h
@@ -2690,9 +2690,9 @@ struct TALER_EXCHANGE_Withdraw2Handle;
* Withdraw a coin from the exchange using a /reserves/$RESERVE_PUB/withdraw
* request. This API is typically used by a merchant to withdraw a tip
* where the blinding factor is unknown to the merchant. Note that unlike
- * the #TALER_EXCHANGE_withdraw() API, this API neither unblinds the signatures
+ * the #TALER_EXCHANGE_batch_withdraw() API, this API neither unblinds the
signatures
* nor can it verify that the exchange signatures are valid, so these tasks
- * are left to the caller. Wallets probably should use
#TALER_EXCHANGE_withdraw()
+ * are left to the caller. Wallets probably should use
#TALER_EXCHANGE_batch_withdraw()
* which integrates these steps.
*
* Note that to ensure that no money is lost in case of hardware
--
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [taler-exchange] branch master updated: -fix doc,
gnunet <=