mention scalability, cite RSCoin on that

2 files changed, 19 insertions, 0 deletions

diff --git a/doc/paper/taler.bib b/doc/paper/taler.bib
index 5b6d9a5e..5d59d31b 100644
--- a/doc/paper/taler.bib
+++ b/doc/paper/taler.bib
@@ -27,6 +27,18 @@
     note = {\url{http://eprint.iacr.org/2016/701}},
 }
 
+@inproceedings{danezis2016rscoin,
+  author    = {George Danezis and
+               Sarah Meiklejohn},
+  title     = {Centrally Banked Cryptocurrencies},
+  booktitle = {23nd Annual Network and Distributed System Security Symposium, {NDSS}
+               2016, San Diego, California, USA, February 21-24, 2016},
+  year      = {2016},
+  booktitle  = {23nd Annual Network and Distributed System Security Symposium, {NDSS}
+               2016, San Diego, California, USA, February 21-24, 2016},
+  publisher = {The Internet Society},
+}
+
 @Misc{greece2015cash,
   author =    {Reuters},
   title =     {Greek council recommends 60 euro limit on ATM withdrawals from Tuesday},
diff --git a/doc/paper/taler.tex b/doc/paper/taler.tex
index cb8577eb..313954f3 100644
--- a/doc/paper/taler.tex
+++ b/doc/paper/taler.tex
@@ -1485,6 +1485,13 @@ these experimental results show that computing-related business costs
 will only marginally contribute to the operational costs of the Taler
 payment system.
 
+Scalability of the design is also not a concern, as the exchange's
+database can be easily shareded over the different public keys as
+desired.  Similar to the RSCoin~\cite{danezis2016rscoin} design, this
+ensures that conflicting transactions end up in the same shard,
+enabling linear scalability of the database operations.  Similarly,
+the cryptographic verification in the frontend can be distributed over
+as many compute nodes as required.
 
 \section{Discussion}