slides

1 files changed, 156 insertions, 8 deletions

diff --git a/presentation/slides.tex b/presentation/slides.tex
index d5ebbff..d1ba885 100644
--- a/presentation/slides.tex
+++ b/presentation/slides.tex
@@ -126,13 +126,35 @@ Can/should we have a payment system for the internet?
 %--------------------
 
 \begin{frame}
+\frametitle{What are payment systems?}
+Payment systems complex (tech) stacks.
+
+Value-based vs register-based.
+
+Different requirements.
+
+\end{frame}
+
+%----------------------------
+
+\begin{frame}
 \frametitle{Contributions}
+This thesis focuses mainly on value-based payments
+on top of an existing register-based system.  Also makes
+contribution towards register layer.
+
 Income-transparent online e-cash
 
 Byzantine Set-Union Consensus
 \end{frame}
 
-%--------------------
+%----------------------------
+
+\section{Income-transparent offline E-cash}
+
+\subsection{Design}
+
+%----------------------------
 
 \begin{frame}
 \frametitle{Design Goals}
@@ -156,11 +178,9 @@ Not all payment systems have the same requirements.  We want ours to
 %----------------------------
 
 \begin{frame}
-\frametitle{Architecture of Payment Systems}
-Payment systems complex (tech) stacks.
+\frametitle{Technical foundation: E-cash}
 \end{frame}
 
-
 %----------------------------
 
 \begin{frame}
@@ -188,6 +208,34 @@ Payment systems complex (tech) stacks.
 
 %----------------------------
 
+\begin{frame}
+\Huge{\centerline{Implementation Demo}}
+\end{frame}
+
+%----------------------------
+
+\begin{frame}
+\frametitle{E-Cash features and trade-offs}
+\end{frame}
+
+%----------------------------
+
+\begin{frame}
+\frametitle{What is new/different in GNU Taler}
+Existing work:  surprisingly little focus on practical use.
+
+Auditor
+  (Technically Obvious, but makes you think about what goes wrong,
+  and \emph{what happens then}.)
+
+
+Income Transparency
+
+Robustness against data loss / restore from backup.
+\end{frame}
+
+%----------------------------
+
 \begin{frame}{Taxability}
   We say Taler is taxable because:
   \begin{itemize}
@@ -204,20 +252,95 @@ Payment systems complex (tech) stacks.
 
 %----------------------------
 
+\subsection{Overview of Protocol}
+
+%----------------------------
+
+\begin{frame}{Setup}
+\end{frame}
+
+\begin{frame}{Withdrawal / Deposit}
+\end{frame}
+
+\begin{frame}{Obtaining Change (Refreshing)}
+\end{frame}
+
+%----------------------------
+
+\subsection{Implementation}
+
+%----------------------------
+
+\begin{frame}
+\frametitle{Implementation Design Decisions}
+\end{frame}
+
+%----------------------------
 
 \begin{frame}
-\frametitle{The auditor}
-Technically Obvious, but makes you think about what goes wrong,
-  and \emph{what happens then}.
+\frametitle{Entities / PKI}
+% entities
 \end{frame}
 
 \begin{frame}
-\frametitle{Compromise Scenarios}
+\frametitle{Exchange Architecture}
+\end{frame}
+
+\begin{frame}
+\frametitle{Auditor Architecture}
+\end{frame}
+
+\begin{frame}
+\frametitle{Merchant Architecture}
+\end{frame}
+
+%----------------------------
+
+\begin{frame}
+\frametitle{Practical Points}
+% mention code-less payments
+Separation between merchant front-end and backend
+
+Different register-layers (SEPA / Blockchain / taler-test) can be used.  Architecture is plugin-based.
+
+Additional features (tipping, ...)
+\end{frame}
+
+%----------------------------
+
+\begin{frame}{Web Integration}
+  payto://
+\end{frame}
+
+%----------------------------
+
+\begin{frame}
+\frametitle{Alternatives?}
+Talk about web payments.
+\end{frame}
+
+%----------------------------
+
+\subsection{Security}
+
+%----------------------------
+
+\begin{frame}
+\frametitle{Post-compromise Security}
+\framesubtitle{What if something goes wrong?}
+Compromise Scenarios
 \end{frame}
 
 %----------------------------
 
 \begin{frame}
+\frametitle{Provable Security}
+How do you know that your protocols are ``secure''?
+\end{frame}
+
+%---------------------------
+
+\begin{frame}
 \frametitle{Security Properties}
 Other systems don't focus that much on aborts.  Something goes wrong, then what do you do?
 
@@ -261,6 +384,18 @@ No considerations of practical compromise.
 
 %----------------------------
 
+\begin{frame}
+\frametitle{Formal Model}
+\end{frame}
+
+%----------------------------
+
+\begin{frame}
+\frametitle{Provable Security:  Limitations}
+\end{frame}
+
+%----------------------------
+
 \section{Byzantine Set Consensus}
 
 \frame{\tableofcontents[currentsection]}
@@ -273,11 +408,24 @@ No considerations of practical compromise.
   \frametitle{Byzantine Consensus Over (Super-)Sets}
 \end{frame}
 
+\begin{frame}
+  \frametitle{BSC and Payments?}
+\end{frame}
+
 %----------------------------
 
 \begin{frame}
+  \frametitle{But what about Blockchain}
 \end{frame}
 
+%----------------------------
+
+\begin{frame}
+\frametitle{Conclusion / Summary}
+\end{frame}
+
+%----------------------------
+
 \begin{frame}
 \frametitle{Future Academic Work}
   \begin{itemize}