commit 6ac5974f388b75f08e7be9689d02b19f16b93e91
parent 38ea9140024fba3aeb535cff0d74e411a5a11432
Author: Christian Grothoff <christian@grothoff.org>
Date: Sat, 11 May 2019 11:56:29 +0200
add payto://
Diffstat:
6 files changed, 61 insertions(+), 6 deletions(-)
diff --git a/presentations/comprehensive/bankademia.tex b/presentations/comprehensive/bankademia.tex
@@ -143,6 +143,57 @@
\end{frame}
+\section{payto://}
+
+
+\begin{frame}{Prelude: \texttt{draft-dold-payto}}
+ \vfill
+ \begin{center}
+ {\huge payto://}
+ \end{center}
+ \vfill
+ {\small See also: \\
+ \url{https://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml}}
+ \vfill
+
+\end{frame}
+
+\begin{frame}{}
+ \vfill
+\includegraphics[width=0.5\textwidth]{einzahlschein-ch.jpeg}
+\hfill
+\includegraphics[width=0.4\textwidth]{de-ueberweisungsformular.png}
+ \vfill
+\end{frame}
+
+
+% FIXME: Start with payto:// (warm-up!)
+
+\begin{frame}[fragile]{\texttt{payto:} Uniform Identifiers for Payments and Accounts}
+ \vfill
+ Like \texttt{mailto:}, but for bank accounts instead of email accounts!
+ \vfill
+ \begin{verbatim}
+ payto://<PAYMENT-METHOD>/<ACCOUNT-NR>
+ ?subject=InvoiceNr42
+ &amount=EUR:12.50
+ \end{verbatim}
+ \vfill
+ Default action: Open app to review and confirm payment.
+ \vfill
+\end{frame}
+
+\begin{frame}[fragile]{Benefits of Payto}
+ \begin{itemize}
+ \item Standardized way to represent financial resources (bank account, bitcoin wallet)
+ and payments to them
+ \item Useful on the client-side on the Web and for FinTech backend applications
+ \item Payment methods (such as SEPA, ACH, Bitcoin) are registered with
+ IANA and allow extra options
+ \end{itemize}
+\end{frame}
+
+
\begin{frame}{GNU Taler}
\vfill
\begin{center}
@@ -162,11 +213,6 @@
\end{frame}
-\section{payto://}
-
-% FIXME: Start with payto:// (warm-up!)
-
-
\section{What is Taler?}
\begin{frame}{What is Taler?}
\vfill
@@ -487,6 +533,9 @@ But of course we use modern instantiations.
\item The corresponding public keys $O$ and $(e,n)$ are certified using
Taler's public key infrastructure (which uses offline-only keys).
\end{itemize}
+\begin{center}
+\includegraphics[width=0.5\textwidth]{taler-diagram-signatures.png}
+\end{center}
\vfill
\begin{center}
{\bf What happens if those private keys are compromised?}
@@ -510,6 +559,9 @@ But of course we use modern instantiations.
\item[$\Rightarrow$] Taler frequently rotates denomination signing keys and
deletes $d$ after the signing period of the respective key expires.
\end{itemize}
+\begin{center}
+\includegraphics[width=0.5\textwidth]{taler-diagram-denom-expiration.png}
+\end{center}
\end{frame}
@@ -555,9 +607,12 @@ and (likely) would presume an evil exchange, forcing it to pay both merchants.
\item Gives change, can provide refunds
\item Integrates nicely with HTTP, handles network failures
\item High performance
-\item Formal security proofs
\item Free Software
+\item Formal security proofs
\end{itemize}
+\begin{center}
+\includegraphics[width=0.5\textwidth]{provable-security.png}
+\end{center}
\item More information at \url{https://taler.net/}.
\end{itemize}
\end{frame}
diff --git a/presentations/comprehensive/de-ueberweisungsformular.png b/presentations/comprehensive/de-ueberweisungsformular.png
Binary files differ.
diff --git a/presentations/comprehensive/einzahlschein-ch.jpeg b/presentations/comprehensive/einzahlschein-ch.jpeg
Binary files differ.
diff --git a/presentations/comprehensive/provable-security.png b/presentations/comprehensive/provable-security.png
Binary files differ.
diff --git a/presentations/comprehensive/taler-diagram-denom-expiration.png b/presentations/comprehensive/taler-diagram-denom-expiration.png
Binary files differ.
diff --git a/presentations/comprehensive/taler-diagram-signatures.png b/presentations/comprehensive/taler-diagram-signatures.png
Binary files differ.
