From 61e6528b92d7495dc922f68e03be3e05a33fe6cf Mon Sep 17 00:00:00 2001 From: Florian Dold Date: Wed, 15 Jan 2020 23:02:29 +0100 Subject: remove developer-centric glossary, it has moved to docs.git --- template/glossary.html.j2 | 258 ---------------------------------------------- 1 file changed, 258 deletions(-) delete mode 100644 template/glossary.html.j2 diff --git a/template/glossary.html.j2 b/template/glossary.html.j2 deleted file mode 100644 index 81b593f7..00000000 --- a/template/glossary.html.j2 +++ /dev/null @@ -1,258 +0,0 @@ -{% extends "common/base.j2" %} -{% block body_content %} -
- -
-
{{ _("auditor") }}
-
- {% trans %} - trusted third party that verifies that the `exchange` is operating correctly - {% endtrans %} -
-
{{ _("bank") }}
-
- {% trans %} - traditional financial service provider who offers wire `transfers` between accounts - {% endtrans %} -
-
{{ _("coin") }}
-
- {% trans %} - coins are individual token representing a certain amount of value, also known as the `denomination` of the coin - {% endtrans %} -
-
{{ _("contract") }}
-
- {% trans %} - the proposal signed by the wallet. - {% endtrans %} -
-
{{ _("denomination") }}
-
- {% trans %} - unit of currency, specifies both the currency and the face value of a - `coin` - {% endtrans %} -
-
{{ _("denomination key") }}
-
- {% trans %} - RSA key used by the exchange to certify that a given `coin` is valid and - of a particular `denomination` - {% endtrans %} -
-
{{ _("deposit") }}
-
- {% trans %} - operation by which a merchant passes coins to an exchange, expecting the - exchange to credit his `bank` account in the future using a wire - `transfer` - {% endtrans %} -
-
{{ _("dirty") }}
-
- {% trans %} - a `coin` is dirty if its public key may be known to an entity other than - the customer, thereby creating the danger of some entity being able to - link multiple transactions of coin's owner if the coin is not refreshed - first - {% endtrans %} -
-
{{ _("exchange") }}
-
- {% trans %} - Taler's payment service provider. Issues electronic `coins` during - `withdrawal` and redeems them when they are `deposited` by merchants. - {% endtrans %} -
-
{{ _("expired") }}
-
- {% trans %} - Various operations come with time limits. In particular, `denomination keys` - come with strict time limits for the various operations involving the - `coin` issued under the `denomination`. The most important limit is the - `deposit` expiration, which specifies until when wallets are allowed to - use the coin in `deposit` or `refreshing` operations. There is also a "legal" - expiration, which specifies how long the exchange keeps records beyond the - `deposit` expiration time. This latter expiration matters for legal disputes - in courts and also creates an upper limit for `refreshing` operations on - special `zombie coin`. - {% endtrans %} -
-
{{ _("extension") }}
-
- {% trans %} - implementation of a `wallet` for browsers - {% endtrans %} -
-
{{ _("fresh coin") }}
-
- {% trans %} - a `coin` is fresh if its public key is only known to the customer - {% endtrans %} -
-
{{ _("master key") }}
-
- {% trans %} - offline key used by the exchange to certify denomination keys and - message signing keys - {% endtrans %} -
-
{{ _("message signing key") }}
-
- {% trans %} - key used by the exchange to sign online messages, other than coins - {% endtrans %} -
-
{{ _("offer") }}
-
- {% trans %} - specification of the details of a transaction, specifies the payment obligations - for the customer (i.e. the amount), the deliverables of the merchant and other - related information, such as deadlines or locations; However, it lacks some - information that the backend is supposed to provide. - In other words, after the backend adds the missing information to the offer and - signs it, it becomes a proposal. - {% endtrans %} -
-
{{ _("owner") }}
-
- {% trans %} - a `coin` is owned by the entity that knows the private key of the coin - {% endtrans %} -
-
{{ _("payback") }}
-
- {% trans %} - operation by which an exchange returns the value of coins affected - by a `revocation` to their `owner`, either by allowing the owner to - withdraw new coins or wiring funds back to the bank account of the `owner` - {% endtrans %} -
-
{{ _("proof") }}
-
- {% trans %} - message that cryptographically demonstrates that a particular claim is correct - {% endtrans %} -
-
{{ _("proposal") }}
-
- {% trans %} - a sketch that has been completed and signed by the merchant backend. - {% endtrans %} -
-
{{ _("reserve") }}
-
- {% trans %} - funds set aside for future use; either the balance of a customer at the - exchange ready for `withdrawal`, or the funds kept in the exchange's bank - account to cover obligations from coins in circulation - {% endtrans %} -
-
{{ _("refreshing") }}
-
- {% trans %} - operation by which a `dirty` `coin` is converted into one or more - `fresh` coins - {% endtrans %} -
-
{{ _("refund") }}
-
- {% trans %} - operation by which a merchant steps back from the right to funds that he - obtained from a `deposit` operation, giving the right to the funds back - to the customer - {% endtrans %} -
-
{{ _("revocation") }}
-
- {% trans %} - exceptional operation by which an exchange withdraws a denomination from - circulation, either because the signing key was compromised or because - the exchange is going out of operation; unspent coins of a revoked - denomination are subjected to payback. - {% endtrans %} -
-
{{ _("sharing") }}
-
- {% trans %} - users can share ownership of a `coin` by sharing access to the coin's - private key, thereby allowing all co-owners to spend the coin at any - time. - {% endtrans %} -
-
{{ _("signing key") }}
-
- {% trans %} - see message signing key. - {% endtrans %} -
-
{{ _("spending") }}
-
- {% trans %} - operation by which a customer gives a merchant the right to `deposit` - coins in return for merchandise - {% endtrans %} -
-
{{ _("transfer") }}
-
- {% trans %} - method of sending funds between `bank` accounts - {% endtrans %} -
-
{{ _("transaction") }}
-
- {% trans %} - method by which ownership is exclusively transferred from one entity - to another - {% endtrans %} -
-
{{ _("transaction id") }}
-
- {% trans %} - unique number by which a merchant identifies a `transaction` - {% endtrans %} -
-
{{ _("wallet") }}
-
- {% trans %} - software running on a customer's computer; withdraws, stores and - spends coins - {% endtrans %} -
-
{{ _("wire transfer") }}
-
- {% trans %} - see `transfer` - {% endtrans %} -
-
{{ _("wire transfer identifier") }}
-
- {% trans %} - subject of a wire `transfer`; usually a random string to uniquely - identify the `transfer` - {% endtrans %} -
-
{{ _("withdrawal") }}
-
- {% trans %} - operation by which a `wallet` can convert funds from a reserve to - fresh coins - {% endtrans %} -
-
{{ _("zombie coin") }}
-
- {% trans %} - a `coin` is a zombie coin if the coin was (1) used as the `dirty` coin - in `refreshing`, (2) the `denomination` of the `fresh` coins created during the - `refreshing` was subject to `revocation`, resulting in the `fresh` coin - from the refresh operation being subjected to `payback`; as a result, - the formerly `dirty` coin is eligible for - `refreshing`, even if the dirty coin's denomination is `expired` for - `deposit` operations (but not if it is expired past the legal - data retention requirement). - {% endtrans %} -
- -
-{% endblock body_content %} -- cgit v1.2.3