[taler-docs] branch master updated: use 32 byte hash for hpayto, use that for joins on queries to better align queries with partitions

[gnunet]

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

grothoff pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new 3646a7c  use 32 byte hash for hpayto, use that for joins on queries to 
better align queries with partitions
3646a7c is described below

commit 3646a7cc3d14bd327327aac9183f5491195d2060
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Thu Mar 3 23:52:16 2022 +0100

    use 32 byte hash for hpayto, use that for joins on queries to better align 
queries with partitions
---
 core/api-common.rst   | 2 +-
 core/api-exchange.rst | 6 +++---
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/core/api-common.rst b/core/api-common.rst
index 4aa609f..2390721 100644
--- a/core/api-common.rst
+++ b/core/api-common.rst
@@ -610,7 +610,7 @@ uses 512-bit hash codes (64 bytes).
 .. sourcecode:: c
 
    struct TALER_PaytoHash {
-     struct GNUNET_HashCode hash;
+     struct GNUNET_ShortHashCode hash;
    };
 
 .. sourcecode:: c
diff --git a/core/api-exchange.rst b/core/api-exchange.rst
index bcd6994..acbaf29 100644
--- a/core/api-exchange.rst
+++ b/core/api-exchange.rst
@@ -3709,7 +3709,7 @@ KYC status updates
     }
 
 
-.. http:GET:: /kyc-proof/$PAYMENT_TARGET_UUID
+.. http:GET:: /kyc-proof/$H_PAYTO
 
   Update KYC status of a particular payment target. Provides
   the token to the exchange that allows it to verify that the
@@ -3718,10 +3718,10 @@ KYC status updates
 
   **Request:**
 
-  :query code=CODE: OAuth 2.0 code argument.
+  :query code=CODE:  OAuth 2.0 code argument.
   :query state=CODE: OAuth 2.0 state argument.
 
-    ..note::
+    .. note::
 
       Depending on the OAuth variant used, additional
       query parameters may need to be passed here.

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.