marketing

Marketing materials (presentations, posters, flyers)
Log | Files | Refs

pqc.tex (3467B)

      1 \documentclass[aspectratio=169,t]{beamer}
      2 \input taler-macros
      3 \usepackage{msc,eurosym}
      4 \usepackage{hyperref}
      5 
      6 \newcommand{\TITLE}{Post-Quantum Cryptography in GNU Taler}
      7 \newcommand{\SUB}{}
      8 \newcommand{\AUTHOR}{GNU Taler Team}
      9 \newcommand{\SPEAKER}{GNU Taler Team}
     10 \newcommand{\INST}{BFH \& TU/e \& Taler Systems SA}
     11 \newcommand{\DATE}{\\ \ \vspace{0.5cm} \\ October 28\textsuperscript{th} 2026}
     12 
     13 % Do not edit this part
     14 \title{\TITLE}
     15 \subtitle{\SUB}
     16 \date{\DATE}
     17 \author[\SPEAKER]{\AUTHOR}
     18 \institute{\INST}
     19 
     20 \begin{document}
     21 
     22 \begin{frame}[plain]
     23 \maketitle
     24 \end{frame}
     25 
     26 
     27 \begin{frame}{Pre NGI TALER}
     28 
     29 \textbf{GNU Taler protocol provides asymetric privacy.}
     30     \begin{center}
     31       \includegraphics[width=0.8\textwidth]{operations.png}
     32     \end{center}
     33 \textbf{Problem 1: Many constructions used in the protocol are not PQ-safe.}
     34 \textbf{Problem 2: For the ``refresh'' step, no suitable construction is known.}
     35 \end{frame}
     36 
     37 
     38 \begin{frame}{NGI TALER objectives}
     39   Work for TU/e team (Tanja Lange, Jonathan Levin, Elisa Pioldi and others):
     40   \begin{enumerate}
     41   \item Complete inventory of constructions and PQ impact ({\color{blue} \href{https://www.taler.net/presentations/d5.3-ngi-ImpactOfQuantumComputersOnTaler.pdf}{DONE}})
     42   \item Alternative protocol formulation for ``refresh'' step
     43     where suitable constructions exist (DONE) {\bf (*)}
     44   \item Recommendation of good primitives for each procol step (WiP)
     45   \end{enumerate}
     46       {\bf (*)}: For the new $k$-unique signature design suitable constructions exist,
     47       but currently available primitives introduce additional limitations implementations have
     48       to work around or have higher computational complexity.
     49 \end{frame}
     50 
     51 
     52 \begin{frame}{Next steps}
     53   \begin{enumerate}
     54   \item Implement recommended new primitives (especially for blinding and $k$-unique signatures,
     55     for both of which no standard implementations exist)
     56   \item Integrate cipher-agility into the existing implementation
     57   \item Ensure $k$-unique signature limitations are reasonably mitigated
     58   \item Test, benchmark, optimize, ship
     59   \end{enumerate}
     60 \end{frame}
     61 
     62 
     63 \begin{frame}{Cost estimates}
     64   \begin{itemize}
     65   \item[24 PM] Implement recommended new primitives, including on server backends and clients (iOS, Android)
     66   \item[36 PM] Integrate new primitives into the existing implementation (cipher-agility)
     67   \item[6 PM] Address $k$-unique signature limitations at the application layer
     68   \item[6 PM] Test, benchmark, optimize, ship
     69   \end{itemize}
     70   The first two can in theory be done by two people in parallel.
     71   \begin{center}
     72     $\Rightarrow$ Needs at least 18--24 months
     73   \end{center}
     74   Budget: $\approx$ \EUR{750k}.
     75 \end{frame}
     76 
     77 
     78 
     79 % This should be last...
     80 \begin{frame}{Acknowledgments}
     81 
     82   \begin{minipage}{0.45\textwidth} \ \\
     83     {\tiny Funded by the European Union (Project 101135475).}
     84 
     85     \begin{center}
     86       \includegraphics[width=0.5\textwidth]{images/bandera.jpg}
     87     \end{center}
     88   \end{minipage}
     89   \hfill
     90   \begin{minipage}{0.45\textwidth}
     91     {\tiny Funded by SERI (HEU-Projekt 101135475-TALER).}
     92 
     93     \begin{center}
     94       \includegraphics[width=0.65\textwidth]{images/sbfi.jpg}
     95     \end{center}
     96   \end{minipage}
     97 
     98   \vfill
     99 
    100   {\tiny
    101 
    102     Views and opinions expressed are however those of the author(s) only
    103     and do not necessarily reflect those of the European Union. Neither the
    104     European Union nor the granting authority can be held responsible for
    105     them.
    106 
    107   }
    108 \end{frame}
    109 
    110 \end{document}