[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[taler-docs] 11/36: remove dangerous API as per discussion with FD

From: gnunet
Subject: [taler-docs] 11/36: remove dangerous API as per discussion with FD
Date: Tue, 22 Jun 2021 19:35:07 +0200

This is an automated email from the git hooks/post-receive script.

grothoff pushed a commit to branch master
in repository docs.

commit 60f61204fdfa89aa32abf0b916f05021ee89295e
Author: Christian Grothoff <>
AuthorDate: Sat May 15 13:30:16 2021 +0200

    remove dangerous API as per discussion with FD
 core/api-wire.rst | 12 ------------
 1 file changed, 12 deletions(-)

diff --git a/core/api-wire.rst b/core/api-wire.rst
index e05aa84..f82ceaa 100644
--- a/core/api-wire.rst
+++ b/core/api-wire.rst
@@ -204,18 +204,6 @@ Querying the transaction history
       // The reserve public key extracted from the transaction details.
       reserve_pub: EddsaPublicKey;
-      // Set to 'true' if this wire transfer originates from
-      // a bank account with a partner bank that implies that
-      // the KYC has already been satisfied for this reserve
-      // because of it.
-      // FIXME: is this acceptable? Seems like users could
-      // easily be tricked into wiring funds to a reserve that
-      // they do NOT own, and then being held responsibe for
-      // the resulting account. So when setting this bit,
-      // we'd need at least a reserve_sig over the credit_account,
-      // which we do not get here... (DANGEROUS API).
-      // => need to discuss KYC more with real banks.
-      kyc_completed: boolean;
   .. ts:def:: IncomingWadTransaction

To stop receiving notification emails like this one, please contact

reply via email to

[Prev in Thread] Current Thread [Next in Thread]