restructure

1 files changed, 82 insertions, 6 deletions

diff --git a/introduction.tex b/introduction.tex
index c1341aa..943bea9 100644
--- a/introduction.tex
+++ b/introduction.tex
@@ -1,22 +1,98 @@
 \chapter{Introduction}
 
+The design of payment systems shapes economies and societies.  Strong,
+developed nation states have adopted highly transparent payment systems, such
+as the MasterCard and VisaCard credit card schemes and computerized bank
+transactions such as SWIFT.  These systems enable mass surveillance by both
+governments and private companies.  Aspects of this surveillance sometimes
+benefit society by providing information about tax evasion or crimes like
+extortion.
+
+At the other extreme, weaker developing nation states have economic
+activity based largely on coins, paper money or even barter.  Here,
+the state is often unable to effectively monitor or tax economic
+activity, and this limits the ability of the state to shape the
+society.
+
+% account vs register based
+
 Payment systems shape our society.
 
 Mention GDPR, data minimization
 
 blockchain + e-cash/taler as full-stack payment system that can be deployed by everybody
 
-% demo walk-through of GNU Taler as user
+% FIXME: demo walk-through of GNU Taler as user
 
+% FIXME:  give the whole blind sigatures as carbon paper signing analogy
 
-\section{Contributions}
+\section{Requirement for Payment Systems}
+(Discuss different requirements, stress that payment systems are typically
+used as stacks of multiple systems, and that no one size fits all)
+
+\section{Existing Payment Systems}
+Or:  Why another payment system?
+
+\section{Design Goals for GNU Taler}
+
+\begin{enumerate}
+  \item \textbf{GNU Taler must be implemented as free software.}
+  \item \textbf{GNU Taler must protect the privacy of buyers.}
+  \item \textbf{GNU Taler must enable the state to tax income and crack down on
+    illegal business activities.}
+  \item \textbf{GNU Taler must only disclose the minimal amount of information
+    necessary.}
+  \item \textbf{GNU Taler must prevent payment fraud.}
+  \item \textbf{GNU Taler must be usable.}
+  \item \textbf{GNU Taler must be efficient.}
+  \item \textbf{GNU Taler must avoid single points of failure.}
+  \item \textbf{GNU Taler must foster competition.}
+\end{enumerate}
 
+\section{Walkthrough of a GNU Taler Payment}
+
+
+\section{Features of E-Cash}
+This section discusses our requirements for a privacy-preserving e-cash system.
+
+\subsection{Change and Divisibility}
+\subsection{Offline Payments}
+Anonymous digital cash schemes since Chaum were frequently designed
+to allow the merchant to be offline during the transaction,
+by providing a means to deanonymize customers involved in
+double-spending.  We consider this problematic as either the
+exchange or the merchant still requires an out-of-band
+means to recover funds from the customer, an expensive and
+unreliable proposition.  Worse, there are unacceptable risks that
+a customer may accidentally deanonymize herself, for example by
+double-spending a coin after restoring from backup.
+
+\subsection{Income Transparency}
+\subsection{Traceability and Anonymity Control}
+\subsection{Refunds}
+\subsection{Tipping}
+\subsection{Transferability}
+\subsection{User Suspension}
+Electronic Cash with Anonymous User Suspension
+\subsection{Recoverability}
+(Ecash vs off-line recovery)
+
+FIXME:  discuss ways to handle extortion / perfect crime / kidnapping
+\subsection{Fair Exchange}
+
+\section{Contributions}
 
 \begin{itemize}
-  \item we design, implement and analyze an efficient byzantine consensus protocol on set structures that allows the optimized implementation of permissioned blockchains
-  \item Notion of income transparency, with an instantiation in chaum-style e-cash and proofs
-  \item consideration of practical aspects including aborts, network failures, refunds, multi-coin payments, faults from synchronization and their effects on anonymity; showing the necessity of a refresh operation
-  \item seamless/native integration of e-cash into web architecture, discussion of pitfalls / security and privacy problems
+  \item we design, implement and analyze an efficient byzantine consensus
+    protocol on set structures that allows the optimized implementation of
+    permissioned blockchains
+  \item Notion of income transparency, with an instantiation in chaum-style
+    e-cash and proofs
+  \item consideration of practical aspects including aborts, network failures,
+    refunds, multi-coin payments, faults from synchronization and their effects
+    on anonymity; showing the necessity of a refresh operation
+  \item seamless/native integration of e-cash into web architecture, discussion
+    of pitfalls / security and privacy problems
   \item implementation of Taler with performance evaluation
 \end{itemize}