[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GNUnet-SVN] [taler-marketing] branch master updated: keep only up-to-da
|
From: |
gnunet |
|
Subject: |
[GNUnet-SVN] [taler-marketing] branch master updated: keep only up-to-date slides |
|
Date: |
Mon, 09 Oct 2017 15:22:00 +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 5743e6d keep only up-to-date slides
5743e6d is described below
commit 5743e6d868781058a6269fb1c2e42dde6a92a2c1
Author: Christian Grothoff <address@hidden>
AuthorDate: Mon Oct 9 15:21:57 2017 +0200
keep only up-to-date slides
---
presentations/investors/investors2017ls.tex | 302 ++++++++++++++--------------
1 file changed, 152 insertions(+), 150 deletions(-)
diff --git a/presentations/investors/investors2017ls.tex
b/presentations/investors/investors2017ls.tex
index 9192007..c088d62 100644
--- a/presentations/investors/investors2017ls.tex
+++ b/presentations/investors/investors2017ls.tex
@@ -540,6 +540,158 @@ Taler is an electronic instant payment system.
\end{frame}
+\begin{frame}{16. Next steps}
+ \begin{itemize}
+ \item[1.]{Complete solution in v0.5 (alpha)}
+ \item[2.]{Complete first seed fouding round for \EUR{1.5-2m}}
+ \item[3.]{Integrate with one or more distribution channels \\
+ (Tor browser, Mozilla browser, p$\equiv$p, \ldots)}
+ \item[4.]{Launch successfully in one of the niches
+ \begin{itemize}
+ \item Newspapers
+ \item Entertainment \& Media
+ \item Gaming
+ \item Platform provider under threat from \\
+ ApplePay, GooglePay, Amazon, \ldots
+ \end{itemize}}
+ \end{itemize}
+\end{frame}
+
+
+\section{Risks}
+\begin{frame}{17. Main Risks}
+ \begin{itemize}
+ \item[1.]{Technical risk --- {\color{green} resolved}}
+ \item[2.]{Cryptographic risk --- {\color{green} resolved}}
+ \item[3.]{Distribution on customer side challenging}
+ \item[4.]{Distribution on merchant side challenging}
+ \item[5.]{Regulator does not approve}
+ \item[6.]{System hacked (by internal admin staff)}
+ \end{itemize}
+\end{frame}
+
+
+\begin{frame}{18. Risk Mitigation}
+ \begin{itemize}
+ \item[1.]{Technical risk --- {\color{green} resolved}}
+ \item[2.]{Cryptographic risk --- {\color{green} resolved}}
+ \item[3.]{Distribution on customer side challenging \\
+ {\color{green} Partner with reach on consumer end}}
+ \item[4.]{Distribution on merchant side challenging \\
+ {\color{green} Partner with platform merchant, or \\
+ Partner with large financial service player \\
+ Focus on e-commerce}}
+ \item[5.]{Regulator does not approve \\
+ {\color{green} Initial reviews by specialists see no issues \\
+ Partner with large financial service player}}
+ \item[6.]{System hacked (by internal admin staff) \\
+ {\color{green} Automated reporting shows maximum exposure \\
+ Audits conducted regularly \\
+ Vetting of admin personnel}}
+ \end{itemize}
+\end{frame}
+
+
+\begin{frame}{19. Business risks and measures}
+ \begin{center} \tiny
+ \begin{tabular}{p{3cm}|p{3cm}|p{3cm}}
+ {\bf Risk} & {\bf Impact} & {\bf
Countermeasure} \\ \hline \hline
+ Usability too low & few users, insufficient income & usability
testing \\ \hline
+ Exchange data loss & financial damage & backups \\
\hline
+ Exchange compromise & financial damage & limit loss by
key rotation \\ \hline
+ Exchange offline & reputation loss & redundant
\mbox{operation} \\ \hline
+ Compliance issues & illegal to operate & work with
\mbox{regulators} \\ \hline
+ No bank license & illegal to operate & work with
banks \\
+ \end{tabular}
+ \end{center}
+\end{frame}
+
+
+\begin{frame}{20. Recent Press}
+ {\tiny
+ \setlist[description]{leftmargin=1cm,labelindent=0.5cm}
+ \begin{description}
+ \item[09-2015]\ \\
+ \begin{itemize}
+ \item
\url{https://bitcoinmagazine.com/21901/bitcoin-governments-without-privacy-taxes/}
+ \item \url{http://www.heise.de/tp/artikel/46/46089/1.html}
+ \end{itemize}
+ \item[06-2016]\ \\
+ \begin{itemize}
+ \item
\url{http://www.theregister.co.uk/2016/06/06/gnu_cryptocurrency_aims_at_the_mainstream_economy_not_the_black_market/}
+ \item
\url{http://www.golem.de/news/halbanonymes-bezahlsystem-gnu-taler-soll-kryptowaehrungen-gerechter-machen-1606-121323.html}
+ \item
\url{http://www.heise.de/newsticker/meldung/GNU-Taler-Open-Source-Protokoll-fuer-Zahlungen-in-Version-0-0-0-erschienen-3228525.html}
+ \end{itemize}
+ \item[08-2016]\ \\
+ \begin{itemize}
+ \item
\url{https://www.theguardian.com/technology/2016/sep/01/online-publishers-readers-ad-block-surveillance-donate-anonymously}
+ \end{itemize}
+ \item[02-2017]\ \\
+ \begin{itemize}
+ \item \url{http://hackerpublicradio.org/eps.php?id=2222}
+ \end{itemize}
+ \end{description}
+ }
+ \begin{center}
+ Complete list at \url{https://taler.net/press}
+ \end{center}
+\end{frame}
+
+
+\begin{frame}{Contact details}
+ \begin{center}
+ \begin{tabular}{p{5cm}p{5cm}}
+ % {\bf CEO} & {\bf CTO} \\ & \\
+ Leon Schumacher & Dr. Christian Grothoff \\
+ {\tt address@hidden & {\tt address@hidden \\
+ +41-79-865-9365 & +33-2-99-84-71-45 \\
+% \url{http://taler.net/ceo/} & \url{http://taler.net/cto/} \\
+ \end{tabular}
+
+ \vspace{2cm}
+ \url{https://www.taler.net/}
+ \end{center}
+\end{frame}
+
+
+\begin{frame}
+ \begin{center}
+ \includegraphics[width=0.66\textwidth]{taler-logo-2017.pdf}
+ \end{center}
+\end{frame}
+
+
+\begin{frame}{Potential Synergies between Taler and Blockchains}
+ \begin{block}{What can Blockchains do for Taler?}
+ Taler cannot cryptographically prove the {\bf timing} of
+ transactions. Using a blockchain for {\bf timestamping} would
+ allow GNU Taler to provide hard proof of {\bf when} a payment
+ happened.
+ \end{block}
+ \begin{block}{What can Taler do for Blockchains?}
+ Blockchains have inherently high transaction {\bf costs} and little
+ {\bf privacy}. Taler can operate as a {\bf side-chain}, providing
+ enhanced privacy and {\bf performance} for crypto currencies.
+ \end{block}
+\end{frame}
+
+
+\begin{frame}{License model}
+ \begin{center}
+ \begin{tabular}{p{2cm}|c|p{5.5cm}}
+ {\bf Component} & {\bf License} & {\bf Why?} \\ \hline \hline
+ Exchange & Affero GPL & competitors must share
\mbox{extensions} \\ \hline
+ Wallets & GPLv3+ & enable community development \\
\hline
+ Merchant & Lesser GPL & maximize market adoption \\
+ \end{tabular}
+ \end{center}
+\end{frame}
+
+\end{document}
+
+
+
+
\section{Next steps}
\begin{frame}{16. Next steps in development and timeline}
@@ -702,156 +854,6 @@ PM $=$ Person month
\end{frame}
-\begin{frame}{21. Next steps}
- \begin{itemize}
- \item[1.]{Complete solution in v0.5 (alpha)}
- \item[2.]{Complete first seed fouding round for \EUR{1.5-2m}}
- \item[3.]{Integrate with one or more distribution channels \\
- (Tor browser, Mozilla browser, p$\equiv$p, \ldots)}
- \item[4.]{Launch successfully in one of the niches
- \begin{itemize}
- \item Newspapers
- \item Entertainment \& Media
- \item Gaming
- \item Platform provider under threat from \\
- ApplePay, GooglePay, Amazon, \ldots
- \end{itemize}}
- \end{itemize}
-\end{frame}
-
-
-\section{Risks}
-\begin{frame}{22. Main Risks}
- \begin{itemize}
- \item[1.]{Technical risk --- {\color{green} resolved}}
- \item[2.]{Cryptographic risk --- {\color{green} resolved}}
- \item[3.]{Distribution on customer side challenging}
- \item[4.]{Distribution on merchant side challenging}
- \item[5.]{Regulator does not approve}
- \item[6.]{System hacked (by internal admin staff)}
- \end{itemize}
-\end{frame}
-
-
-\begin{frame}{23. Risk Mitigation}
- \begin{itemize}
- \item[1.]{Technical risk --- {\color{green} resolved}}
- \item[2.]{Cryptographic risk --- {\color{green} resolved}}
- \item[3.]{Distribution on customer side challenging \\
- {\color{green} Partner with reach on consumer end}}
- \item[4.]{Distribution on merchant side challenging \\
- {\color{green} Partner with platform merchant, or \\
- Partner with large financial service player \\
- Focus on e-commerce}}
- \item[5.]{Regulator does not approve \\
- {\color{green} Initial reviews by specialists see no issues \\
- Partner with large financial service player}}
- \item[6.]{System hacked (by internal admin staff) \\
- {\color{green} Automated reporting shows maximum exposure \\
- Audits conducted regularly \\
- Vetting of admin personnel}}
- \end{itemize}
-\end{frame}
-
-
-\begin{frame}{24. Business risks and measures}
- \begin{center} \tiny
- \begin{tabular}{p{3cm}|p{3cm}|p{3cm}}
- {\bf Risk} & {\bf Impact} & {\bf
Countermeasure} \\ \hline \hline
- Usability too low & few users, insufficient income & usability
testing \\ \hline
- Exchange data loss & financial damage & backups \\
\hline
- Exchange compromise & financial damage & limit loss by
key rotation \\ \hline
- Exchange offline & reputation loss & redundant
\mbox{operation} \\ \hline
- Compliance issues & illegal to operate & work with
\mbox{regulators} \\ \hline
- No bank license & illegal to operate & work with
banks \\
- \end{tabular}
- \end{center}
-\end{frame}
-
-
-\begin{frame}{25. Recent Press}
- {\tiny
- \setlist[description]{leftmargin=1cm,labelindent=0.5cm}
- \begin{description}
- \item[09-2015]\ \\
- \begin{itemize}
- \item
\url{https://bitcoinmagazine.com/21901/bitcoin-governments-without-privacy-taxes/}
- \item \url{http://www.heise.de/tp/artikel/46/46089/1.html}
- \end{itemize}
- \item[06-2016]\ \\
- \begin{itemize}
- \item
\url{http://www.theregister.co.uk/2016/06/06/gnu_cryptocurrency_aims_at_the_mainstream_economy_not_the_black_market/}
- \item
\url{http://www.golem.de/news/halbanonymes-bezahlsystem-gnu-taler-soll-kryptowaehrungen-gerechter-machen-1606-121323.html}
- \item
\url{http://www.heise.de/newsticker/meldung/GNU-Taler-Open-Source-Protokoll-fuer-Zahlungen-in-Version-0-0-0-erschienen-3228525.html}
- \end{itemize}
- \item[08-2016]\ \\
- \begin{itemize}
- \item
\url{https://www.theguardian.com/technology/2016/sep/01/online-publishers-readers-ad-block-surveillance-donate-anonymously}
- \end{itemize}
- \item[02-2017]\ \\
- \begin{itemize}
- \item \url{http://hackerpublicradio.org/eps.php?id=2222}
- \end{itemize}
- \end{description}
- }
- \begin{center}
- Complete list at \url{https://taler.net/press}
- \end{center}
-\end{frame}
-
-
-\begin{frame}{Contact details}
- \begin{center}
- \begin{tabular}{p{5cm}p{5cm}}
- % {\bf CEO} & {\bf CTO} \\ & \\
- Leon Schumacher & Dr. Christian Grothoff \\
- {\tt address@hidden & {\tt address@hidden \\
- +41-79-865-9365 & +33-2-99-84-71-45 \\
-% \url{http://taler.net/ceo/} & \url{http://taler.net/cto/} \\
- \end{tabular}
-
- \vspace{2cm}
- \url{https://www.taler.net/}
- \end{center}
-\end{frame}
-
-
-\begin{frame}
- \begin{center}
- \includegraphics[width=0.66\textwidth]{taler-logo-2017.pdf}
- \end{center}
-\end{frame}
-
-
-\begin{frame}{Potential Synergies between Taler and Blockchains}
- \begin{block}{What can Blockchains do for Taler?}
- Taler cannot cryptographically prove the {\bf timing} of
- transactions. Using a blockchain for {\bf timestamping} would
- allow GNU Taler to provide hard proof of {\bf when} a payment
- happened.
- \end{block}
- \begin{block}{What can Taler do for Blockchains?}
- Blockchains have inherently high transaction {\bf costs} and little
- {\bf privacy}. Taler can operate as a {\bf side-chain}, providing
- enhanced privacy and {\bf performance} for crypto currencies.
- \end{block}
-\end{frame}
-
-\end{document}
-
-
-
-\begin{frame}{License model}
- \begin{center}
- \begin{tabular}{p{2cm}|c|p{5.5cm}}
- {\bf Component} & {\bf License} & {\bf Why?} \\ \hline \hline
- Exchange & Affero GPL & competitors must share
\mbox{extensions} \\ \hline
- Wallets & GPLv3+ & enable community development \\
\hline
- Merchant & Lesser GPL & maximize market adoption \\
- \end{tabular}
- \end{center}
-\end{frame}
-
\section{Financials}
--
To stop receiving notification emails like this one, please contact
address@hidden
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [GNUnet-SVN] [taler-marketing] branch master updated: keep only up-to-date slides,
gnunet <=