[GNUnet-SVN] [taler-exchange] branch master updated (c50ee80 -> ca2c54e)

[gnunet]

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

burdges pushed a change to branch master
in repository exchange.

    from c50ee80  fix typo
     new 2e2dee1  Parenthetical comments
     new ca2c54e  Comment on Ripple fine in relation to BOLT

The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 doc/paper/taler.bib | 30 ++++++++++++++++++++++++++++++
 doc/paper/taler.tex | 19 ++++++++++---------
 2 files changed, 40 insertions(+), 9 deletions(-)

diff --git a/doc/paper/taler.bib b/doc/paper/taler.bib
index e3dda1b..1e5b9a7 100644
--- a/doc/paper/taler.bib
+++ b/doc/paper/taler.bib
@@ -68,6 +68,36 @@
 }
 
 
address@hidden,
+  author = {Steve Hudak},
+  title = {FinCEN Fines Ripple Labs Inc. in First Civil Enforcement Action 
Against a Virtual Currency Exchanger},
+  month = {May},
+  day = {5},
+  year = {2015},
+  note = 
{\url{https://www.fincen.gov/news/news-releases/fincen-fines-ripple-labs-inc-first-civil-enforcement-action-against-virtual}},
+}
+
address@hidden,
+  author = {Megan Geuss},
+  title = {Cryptocurrency maker Ripple Labs fined \$700K for flouting 
financial regs},
+  subtitle = {Virtual currency Wild West is done, registration as a Money 
Services Business required.},
+  month = {May},
+  day = {5},
+  year = {2015},
+  note = 
{\url{https://arstechnica.com/tech-policy/2015/05/cryptocurrency-maker-ripple-labs-fined-700k-for-flouting-financial-regs/}},
+  url_coindesk = 
{http://www.coindesk.com/fincen-fines-ripple-labs-700000-bank-secrecy-act/}
+}
+
address@hidden,
+  author = {Stan Higgins},
+  title = {FinCEN Fines Ripple Labs for Bank Secrecy Act Violations},
+  month = {May},
+  day = {5},
+  year = {2015},
+  note = 
{\url{http://www.coindesk.com/fincen-fines-ripple-labs-700000-bank-secrecy-act/}},
+}
+
+
 @inproceedings{danezis2016rscoin,
   author    = {George Danezis and
                Sarah Meiklejohn},
diff --git a/doc/paper/taler.tex b/doc/paper/taler.tex
index 47a17cc..9b6f1ec 100644
--- a/doc/paper/taler.tex
+++ b/doc/paper/taler.tex
@@ -332,10 +332,11 @@ In general, these off-chain payment channels, like BOLT 
and the
 Lightning Network, improve the blockchain based payment schemes by
 centralizing payment processing, but they remain orders of magnitude
 more costly than Taler with the same degree of centralization.
-In addition, they require that miners act far more like traditional
-payment processors than conventional cryptocurrencies, exposing miners
-to legal risks.  Taler is explicitly designed to help a Taler exchange
-navigate these legal risks.
+In addition, they require nodes act far more like payment processors
+than like conventional miners, potentially exposing miners to legal
+risks, not unlike the financial violations for which Ripple was fined
+\cite{RippleFined-ArsTechnica}.  Taler is explicitly designed to help
+a Taler exchange navigate these legal risks.
 
 GreenCoinX\footnote{\url{https://www.greencoinx.com/}} is a more
 recent AltCoin where the company promises to identify the owner of
@@ -1428,8 +1429,8 @@ information known by the merchant in the above.  As a 
result, this
 proves that our linking protocol \S\ref{subsec:linking} does not
 degrade privacy.  We note that the exchange could lie in the linking
 protocol about the transfer public key to generate coins that it can
-link (at a financial loss to the exchange that it would have to share
-with its auditor).  However, in the normal course of payments the link
+link, at a financial loss to the exchange that it would have to share
+with its auditor.  However, in the normal course of payments the link
 protocol is never used.
 
 \subsection{Exculpability arguments}
@@ -1614,9 +1615,9 @@ we then pushed the t2.micro instance to the resource limit
 from a network with $\approx$ 160 ms latency to
 the EC2 instance.  At that point, the instance managed about 8 HTTP
 requests per second, which roughly corresponds to one full business
-transaction (as a full business transaction is expected to involve
-withdrawing and depositing several coins).  The network traffic was
-modest at approximately 50 kbit/sec from the exchange
+transaction, given that a full business transaction is expected to
+involve withdrawing and depositing several coins.  The network traffic
+was modest at approximately 50 kbit/sec from the exchange
 %(Figure~\ref{fig:out})
 and 160 kbit/sec to the exchange.
 %(Figure~\ref{fig:in}).

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