[Top][All Lists]

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

[GNUnet-SVN] [taler-api] branch master updated: fields are again mandato

From: gnunet
Subject: [GNUnet-SVN] [taler-api] branch master updated: fields are again mandatory
Date: Sun, 17 Sep 2017 16:59:40 +0200

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

grothoff pushed a commit to branch master
in repository api.

The following commit(s) were added to refs/heads/master by this push:
     new 5e646ef  fields are again mandatory
5e646ef is described below

commit 5e646ef3a1c103e2fe2a24509f3486967a426f8b
Author: Christian Grothoff <address@hidden>
AuthorDate: Sun Sep 17 16:59:38 2017 +0200

    fields are again mandatory
 api-exchange.rst | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/api-exchange.rst b/api-exchange.rst
index 575832c..f2af78c 100644
--- a/api-exchange.rst
+++ b/api-exchange.rst
@@ -94,15 +94,13 @@ possibly by using HTTPS.
       // is sabotaging end-user anonymity by giving disjoint denomination keys 
       // different users.  If a exchange were to do this, this signature 
allows the
       // clients to demonstrate to the public that the exchange is dishonest.
-      // Only returned if "last_issue_date" was not specified (or not used for 
-      // reason and thus the full set of current keys was returned).
-      eddsa_sig?: EddsaSignature;
+      eddsa_sig: EddsaSignature;
       // Public EdDSA key of the exchange that was used to generate the 
       // Should match one of the exchange's signing keys from /keys.  It is 
       // explicitly as the client might otherwise be confused by clock skew as 
       // which signing key was used.
-      eddsa_pub?: EddsaPublicKey;
+      eddsa_pub: EddsaPublicKey;
   .. _tsref-type-Denom:

To stop receiving notification emails like this one, please contact

reply via email to

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