summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFlorian Dold <florian.dold@gmail.com>2019-02-22 11:48:11 +0100
committerFlorian Dold <florian.dold@gmail.com>2019-02-22 11:48:11 +0100
commit91ef32405533c1160479bf34bcf53b38bd544024 (patch)
tree5d73487c475a199092302a48da65cc0c2cef0ec8
parentded1e4123ab82b489a23bce8cf670f09e54a3815 (diff)
downloaddold-thesis-phd-91ef32405533c1160479bf34bcf53b38bd544024.tar.gz
dold-thesis-phd-91ef32405533c1160479bf34bcf53b38bd544024.tar.bz2
dold-thesis-phd-91ef32405533c1160479bf34bcf53b38bd544024.zip
slides
-rw-r--r--presentation/slides.tex39
1 files changed, 32 insertions, 7 deletions
diff --git a/presentation/slides.tex b/presentation/slides.tex
index d52a2d8..5512b71 100644
--- a/presentation/slides.tex
+++ b/presentation/slides.tex
@@ -182,7 +182,7 @@ Income-transparent online e-cash
\item Consideration of aborts, network failures, refunds, multi-coin
payments, faults from wallet synchronization and their effects on anonymity;
showing the practical necessity of a refresh operation.
- \item
+ \pause
\item Auditor component: Detection mechanism and responses to
different compromise scenarios.
\item Provisions against blackmailing / kidnapping scenarios.
@@ -269,6 +269,14 @@ Byzantine \emph{Set-Union} Consensus
%----------------------------
\begin{frame}
+\frametitle{How does a payment work?}
+ \begin{enumerate}
+ \end{enumerate}
+\end{frame}
+
+%----------------------------
+
+\begin{frame}
\frametitle{E-Cash features and trade-offs}
Some selected aspects (more in thesis)
\begin{enumerate}[<+- | alert@+>]
@@ -290,6 +298,7 @@ Byzantine \emph{Set-Union} Consensus
\item Anti-feature, enables black markets / tax evasion!
\item Taler provides \emph{income transparency}, roughly the \emph{opposite}
\end{itemize}
+ \item Atomic Swaps / Fair Exchange \uncover<+->{$\Rightarrow$ Supported, coin serial no. is private key}
\end{enumerate}
\end{frame}
@@ -300,13 +309,19 @@ Byzantine \emph{Set-Union} Consensus
\begin{itemize}
\item Existing work: surprisingly little focus on practical use.
\begin{itemize}
- \item working out all the details!
+ \item What do customers do \textbf{before} the blind signature protocol?
+ \item How do customers agree to specific contract terms for a transaction?
+ \item How are payments with multiple coins handled?
+ \item How are refunds handled?
+ \item What happens after data loss / aborts / restore from backup?
\end{itemize}
+ \item Income Transparency (to help detect tax evasion)
\item Auditor
- (Technically Obvious, but makes you think about what goes wrong,
- and \emph{what happens then}.)
- \item Income Transparency
- \item Robustness against data loss / restore from backup.
+ \begin{itemize}
+ \item Technically Obvious, but makes you think about what goes wrong,
+ and \emph{what happens then}.
+ \end{itemize}
+ \item Measures against ``perfect crime'' with e-cash
\end{itemize}
\end{frame}
@@ -316,11 +331,21 @@ Byzantine \emph{Set-Union} Consensus
A coin that is e.g.
\begin{itemize}
\item partially spent, or
- \item revealed aborted transaction
+ \item revealed in aborted transaction
\item restored from offline backup
\end{itemize}
is \emph{dirty}, and can break anonymity.
+\pause
+\vfill
+
+Strawman idea: Spend coin with exchange, obtain fresh coin
+via blind signing.
+
+$\Rightarrow$ Can be abused: Merchant provides (blinded) fresh coin to customer
+
+$\Rightarrow$ Naive refresh protocol enables tax evasion
+
\end{frame}