taler-docs

commit 0337d0b116ffe5fba2b4b16b581578d66d03291d
parent 27450d99d9db6a3e5a126accd4330d1b56d90ee3
Author: Mikolai Gütschow <mikolai.guetschow@tu-dresden.de>
Date:   Wed, 11 Oct 2023 16:55:00 +0200

api-common: fix order of fields in GNUNET_CRYPTO_EccSignaturePurpose

see https://docs.gnunet.org/doxygen/d7/d7f/structGNUNET__CRYPTO__EccSignaturePurpose.html as reference

Diffstat:
M
core/api-common.rst
 | 
13
+++++--------

1 file changed, 5 insertions(+), 8 deletions(-)
diff --git a/core/api-common.rst b/core/api-common.rst
@@ -957,9 +957,11 @@ Any piece of signed data, complies to the abstract data structure given below.
   /*From gnunet_crypto_lib.h*/
   struct GNUNET_CRYPTO_EccSignaturePurpose {
     /**
-
-    The following constraints apply for a valid amount:
-
+     * This field equals the number of bytes being signed,
+     * namely 'sizeof (struct Data)'.
+     */
+    uint32_t size;
+    /**
      * This field is used to express the context in
      * which the signature is made, ensuring that a
      * signature cannot be lifted from one part of the protocol
@@ -967,11 +969,6 @@ Any piece of signed data, complies to the abstract data structure given below.
      * exchange's codebase (git://taler.net/exchange).
      */
     uint32_t purpose;
-    /**
-     * This field equals the number of bytes being signed,
-     * namely 'sizeof (struct Data)'.
-     */
-    uint32_t size;
   };