gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[taler-marketing] branch master updated: cut down as per Leon's request


From: gnunet
Subject: [taler-marketing] branch master updated: cut down as per Leon's request
Date: Wed, 28 Apr 2021 12:29:31 +0200

This is an automated email from the git hooks/post-receive script.

grothoff pushed a commit to branch master
in repository marketing.

The following commit(s) were added to refs/heads/master by this push:
     new 8242284  cut down as per Leon's request
8242284 is described below

commit 8242284b994f6f22779fecb50b31f6382a2dc2a1
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Wed Apr 28 12:29:27 2021 +0200

    cut down as per Leon's request
---
 presentations/2021-cb/slides.tex | 127 ++++++++++++++++++++-------------------
 1 file changed, 65 insertions(+), 62 deletions(-)

diff --git a/presentations/2021-cb/slides.tex b/presentations/2021-cb/slides.tex
index f77071b..2246b4d 100644
--- a/presentations/2021-cb/slides.tex
+++ b/presentations/2021-cb/slides.tex
@@ -198,68 +198,6 @@ However, Taler is
 \end{frame}
 
 
-\begin{frame}{Taler Protocol}
-  \framesubtitle{\url{https://taler.net/papers/thesis-dold-phd-2019.pdf}}
-  \begin{itemize}
-    \item Core concept:  Blind-signed tokens of value
-    \item Based on stable, proven cryptographic constructions and primitives
-      (Chaum-style eCash with extension)
-    \item Concrete protocol with focus on data minimization
-      and transparency/auditability through digital signatures.
-    \item Documented in detail in a PhD thesis by Dold
-    \item Exchange implementation has undergone external security audit
-  \end{itemize}
-\end{frame}
-
-
-
-%\begin{frame}{CBDC is a Hot Topic}
-%  \vfill
-%\begin{center}
-%\includegraphics[width=1.0\textwidth]{cbdc-news.png}
-%\end{center}
-%\end{frame}
-
-\begin{frame}{CBDC Initiatives and Taler}
-  Many initiatives are currently at the level of requirements discussion:
-  \begin{minipage}{7cm}
-  \begin{itemize}
-    \item ECB: Report on a Digital Euro / Eurosystem report on the public 
consultation on a Digital Euro
-    \item Bank of England: Just initiated a task force
-  \end{itemize}
-  \end{minipage}
-  \begin{minipage}{5cm}
-  \includegraphics[width=0.8\textwidth]{cbdc-news.png}
-  \end{minipage}
-  \vfill
-  Taler can serve as the foundation for a \emph{bearer-based} \emph{retail} 
CBDC.
-  \begin{itemize}
-    \item Taler replicates physical cash rather than bank deposits
-    \item Taler has unique design principles and regulatory features that 
align with CBDC
-      requirements
-    \item ECB survey has identified privacy as a primary requirement of end 
users
-  \end{itemize}
-\end{frame}
-
-\begin{frame}{Design principles: Aligned with CBDC}
-  \framesubtitle{https://taler.net/en/principles.html}
-GNU Taler must ...
-\begin{enumerate}
-  \item {... be implemented as {\bf free software}.}
-  \item {... protect the {\bf privacy of buyers}.}
-  \item {... must enable the state to {\bf tax income} and crack down on
-    illegal business activities.}
-  \item {... prevent payment fraud.}
-  \item {... only {\bf disclose the minimal amount of information
-    necessary}.}
-  \item {... be usable.}
-  \item {... be efficient.}
-  \item {... avoid single points of failure.}
-  \item {... foster {\bf competition}.}
-\end{enumerate}
-\end{frame}
-
-
 \begin{frame}{Taler: Unique Regulatory Features for CBs}
   
\framesubtitle{\url{https://www.snb.ch/en/mmr/papers/id/working_paper_2021_03}}
   \begin{itemize}
@@ -394,6 +332,71 @@ Further reading:
 \begin{frame}{Backup Slides}
 \end{frame}
 
+
+
+\begin{frame}{Taler Protocol}
+  \framesubtitle{\url{https://taler.net/papers/thesis-dold-phd-2019.pdf}}
+  \begin{itemize}
+    \item Core concept:  Blind-signed tokens of value
+    \item Based on stable, proven cryptographic constructions and primitives
+      (Chaum-style eCash with extension)
+    \item Concrete protocol with focus on data minimization
+      and transparency/auditability through digital signatures.
+    \item Documented in detail in a PhD thesis by Dold
+    \item Exchange implementation has undergone external security audit
+  \end{itemize}
+\end{frame}
+
+
+
+%\begin{frame}{CBDC is a Hot Topic}
+%  \vfill
+%\begin{center}
+%\includegraphics[width=1.0\textwidth]{cbdc-news.png}
+%\end{center}
+%\end{frame}
+
+\begin{frame}{CBDC Initiatives and Taler}
+  Many initiatives are currently at the level of requirements discussion:
+  \begin{minipage}{7cm}
+  \begin{itemize}
+    \item ECB: Report on a Digital Euro / Eurosystem report on the public 
consultation on a Digital Euro
+    \item Bank of England: Just initiated a task force
+  \end{itemize}
+  \end{minipage}
+  \begin{minipage}{5cm}
+  \includegraphics[width=0.8\textwidth]{cbdc-news.png}
+  \end{minipage}
+  \vfill
+  Taler can serve as the foundation for a \emph{bearer-based} \emph{retail} 
CBDC.
+  \begin{itemize}
+    \item Taler replicates physical cash rather than bank deposits
+    \item Taler has unique design principles and regulatory features that 
align with CBDC
+      requirements
+    \item ECB survey has identified privacy as a primary requirement of end 
users
+  \end{itemize}
+\end{frame}
+
+\begin{frame}{Design principles: Aligned with CBDC}
+  \framesubtitle{https://taler.net/en/principles.html}
+GNU Taler must ...
+\begin{enumerate}
+  \item {... be implemented as {\bf free software}.}
+  \item {... protect the {\bf privacy of buyers}.}
+  \item {... must enable the state to {\bf tax income} and crack down on
+    illegal business activities.}
+  \item {... prevent payment fraud.}
+  \item {... only {\bf disclose the minimal amount of information
+    necessary}.}
+  \item {... be usable.}
+  \item {... be efficient.}
+  \item {... avoid single points of failure.}
+  \item {... foster {\bf competition}.}
+\end{enumerate}
+\end{frame}
+
+
+
 \begin{frame}[fragile]{Taler: Bank Perspective}
 \begin{adjustbox}{max totalsize={.9\textwidth}{.7\textheight},center}
 \begin{tikzpicture}

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]