[taler-marketing] branch master updated: refactor

[gnunet]

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 b977510  refactor
b977510 is described below

commit b977510b83c5b05c22ce1914c8a3607941f2e78d
Author: Christian Grothoff <grothoff@gnunet.org>
AuthorDate: Mon Oct 16 13:27:02 2023 +0200

    refactor
---
 presentations/2021-cb/boh.tex | 108 +++++++++++++++++++++---------------------
 1 file changed, 55 insertions(+), 53 deletions(-)

diff --git a/presentations/2021-cb/boh.tex b/presentations/2021-cb/boh.tex
index 80280e3..5e5899b 100644
--- a/presentations/2021-cb/boh.tex
+++ b/presentations/2021-cb/boh.tex
@@ -157,7 +157,7 @@ transparency, accountability, and security (part of the GNU 
project).
 
 \begin{frame}{Why?}
 \begin{itemize}
-\item National soverenity: remove control of payment sector from foreign 
entities
+\item National sovereignity: remove control of payment sector from foreign 
entities
 \item Limit impact of bank failures on societal financial transaction 
processing needs, especially in cashless society
 \item Access for the marginalized: children, unbanked need access to payments 
as cash disappears
 \item Financial self-determination: preserve ability to pay without 3rd party 
approval
@@ -178,44 +178,6 @@ transparency, accountability, and security (part of the 
GNU project).
 \end{frame}
 
 
-\begin{frame}{Payment Systems: Accounts vs. Tokens}
-Two types of payment systems:
-\begin{enumerate}
-\item {\bf account-based system}: transfer occurs by charging the payer’s 
account and crediting
-the payee’s account (e.g., bank deposits)
-\item {\bf token-based (value-based) system}: transfer occurs by transferring 
the value itself, or a
-token that represents the monetary asset (e.g., banknotes)
-\end{enumerate}
-Key Difference is the information carried by the information asset:
-\begin{itemize}
-\item account (assets): associated with a transaction history
-\item token (assets): carry information about value and entity that issued the 
token
-\end{itemize}
-Bitcoin, and Distributed Ledger Technologies (DLTs) in general, are 
account-based systems!
-Novelty is that the ledger is distributed (decentralized).
-\end{frame}
-
-
-\begin{frame}{Simplistic rCBDC Designs}
-  \framesubtitle{\url{https://edwardsnowden.substack.com/p/cbdcs}}
-  \begin{itemize}
-\item Account-based rCBDC (e.g., Bindseil 2020, Berentsen and Schär 2018):
-\begin{itemize}
-\item simplest solution: central bank account for all
-\item responsibility to perform KYC and ensure AML/CFT (could be outsourced);
-\item potential for mass-surveillance (threat to CB independence);
-\item in direct competition with commercial banks
-\end{itemize} \pause
-\item Token-based rCBDC:
-\begin{itemize}
-\item requires a system to ensure that electronic tokens are not easily copied
-(hardware-based or software-based) 
-\item[$\rightarrow$] double-spending problem
-%\item KYC and AML/CFT compliance?
-\end{itemize}
-\end{itemize}
-\end{frame}
-
 
 \section{What is Taler?}
 \begin{frame}{What is Taler?}
@@ -376,20 +338,6 @@ other banks to avoid being excluded.
 \end{frame}
 
 
-\begin{frame}{Taler: Project Status}
-\framesubtitle{\url{https://docs.taler.net/}}
-\begin{itemize}
-    \item Cryptographic protocols and core exchange component are stable
-    \item Current focus: KYC process polishing, programmability
-    \item Preparations for launch in Basel (as regional currency)
-    \item Pilot project at Bern University of Applied Sciences cafeteria
-  \end{itemize}
-\begin{center}
-\includegraphics[width=0.7\textwidth]{taler-in-use.png}
- \end{center}
-\end{frame}
-
-
 \section{Competitor comparison}
 \begin{frame}{Competitor comparison}
   \begin{center} \small
@@ -439,4 +387,58 @@ References:
 \end{frame}
 
 
+\begin{frame}{Payment Systems: Accounts vs. Tokens}
+Two types of payment systems:
+\begin{enumerate}
+\item {\bf account-based system}: transfer occurs by charging the payer’s 
account and crediting
+the payee’s account (e.g., bank deposits)
+\item {\bf token-based (value-based) system}: transfer occurs by transferring 
the value itself, or a
+token that represents the monetary asset (e.g., banknotes)
+\end{enumerate}
+Key Difference is the information carried by the information asset:
+\begin{itemize}
+\item account (assets): associated with a transaction history
+\item token (assets): carry information about value and entity that issued the 
token
+\end{itemize}
+Bitcoin, and Distributed Ledger Technologies (DLTs) in general, are 
account-based systems!
+Novelty is that the ledger is distributed (decentralized).
+\end{frame}
+
+
+\begin{frame}{Simplistic rCBDC Designs}
+  \framesubtitle{\url{https://edwardsnowden.substack.com/p/cbdcs}}
+  \begin{itemize}
+\item Account-based rCBDC (e.g., Bindseil 2020, Berentsen and Schär 2018):
+\begin{itemize}
+\item simplest solution: central bank account for all
+\item responsibility to perform KYC and ensure AML/CFT (could be outsourced);
+\item potential for mass-surveillance (threat to CB independence);
+\item in direct competition with commercial banks
+\end{itemize} \pause
+\item Token-based rCBDC:
+\begin{itemize}
+\item requires a system to ensure that electronic tokens are not easily copied
+(hardware-based or software-based) 
+\item[$\rightarrow$] double-spending problem
+%\item KYC and AML/CFT compliance?
+\end{itemize}
+\end{itemize}
+\end{frame}
+
+\begin{frame}{Taler: Project Status}
+\framesubtitle{\url{https://docs.taler.net/}}
+\begin{itemize}
+    \item Cryptographic protocols and core exchange component are stable
+    \item Current focus: KYC process polishing, programmability
+    \item Preparations for launch in Basel (as regional currency)
+    \item Pilot project at Bern University of Applied Sciences cafeteria
+  \end{itemize}
+\begin{center}
+\includegraphics[width=0.7\textwidth]{taler-in-use.png}
+ \end{center}
+\end{frame}
+
+
+
+
 \end{document}

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