[taler-docs] branch master updated: more terms

[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 1e31a13  more terms
1e31a13 is described below

commit 1e31a13c03ecb5505646e9de17cb38b7e7cbaf04
Author: Christian Grothoff <address@hidden>
AuthorDate: Sun Mar 1 13:23:44 2020 +0100

    more terms
---
 developers-manual.rst     | 20 ++++++++++++++++++++
 taler-exchange-manual.rst |  2 ++
 2 files changed, 22 insertions(+)

diff --git a/developers-manual.rst b/developers-manual.rst
index 27ea00a..ee8fc28 100644
--- a/developers-manual.rst
+++ b/developers-manual.rst
@@ -954,6 +954,14 @@ use when talking to end users or even system 
administrators.
   coins
     coins are individual token representing a certain amount of value, also 
known as the :term:`denomination` of the coin
 
+  commitment
+  refresh commitment
+    data that the wallet commits to during the :term:`melt` stage of the
+    :term:`refresh` protocol where it
+    has to prove to the :term:`exchange` that it is deriving the :term:`fresh`
+    coins as specified by the Taler protocol.  The commitment is verified
+    probabilistically (see: :term:`kappa`) during the :term:`reveal` stage.
+
   contract
   contracts
     formal agreement between :term:`merchant` and :term:`customer` specifying 
the
@@ -1036,6 +1044,11 @@ use when talking to end users or even system 
administrators.
     commonly used in the Taler protocol as the payload of HTTP requests
     and responses.
 
+  kappa
+    security parameter used in the :term:`refresh` protocol. Defined to be 3.
+    The probability of successfully evading the income transparency with the
+    refresh protocol is 1:kappa.
+
   LibEuFin
     FIXME: explain
 
@@ -1079,6 +1092,13 @@ use when talking to end users or even system 
administrators.
     by a :term:`revocation` to their :term:`owner`, either by allowing the 
owner to
     withdraw new coins or wiring funds back to the bank account of the 
:term:`owner`.
 
+  planchet
+    precursor data for a :term:`coin`. A planchet includes the coin's internal
+    secrets (coin private key, blinding factor), but lacks the RSA signature
+    of the :term:`exchange`.  When :term:`withdrawing`, a :term:`wallet`
+    creates and persists a planchet before asking the exchange to sign it to
+    get the coin.
+
   purchase
     Refers to the overall process of negotiating a :term:`contract` and then
     making a payment with :term:`coins` to a :term:`merchant`.
diff --git a/taler-exchange-manual.rst b/taler-exchange-manual.rst
index bd1733e..af5eea5 100644
--- a/taler-exchange-manual.rst
+++ b/taler-exchange-manual.rst
@@ -130,6 +130,7 @@ components:
 
 -  Wire adapter
    A wire adapter is a component that enables exchange to talk to a bank.
+
    (1) The libtalerfakebank implements a bank with a wire adapter API
        inside of a testcase.
    (2) For the demonstration Web site (or local currencies),
@@ -138,6 +139,7 @@ components:
    (3) For production, libeufin's Nexus component implements a wire
        adapter towards the traditional SEPA banking system with IBAN
        accounts.
+
    The client-side wire adapter API is implemented in libtalerbank and
    is used by the aggregator to execute wire transfers and for the
    auditor to query bank transaction histories.

-- 
To stop receiving notification emails like this one, please contact
address@hidden.