[taler-marketing] branch master updated: -more writing

[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 cb1ec59  -more writing
cb1ec59 is described below

commit cb1ec59ed750a9c25200f56343e6d88527d824f1
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Fri Nov 25 13:27:41 2022 +0100

    -more writing
---
 depolymerization/en.tex | 121 +++++++++++++++++++++++++++++++++++++++++++++++-
 1 file changed, 119 insertions(+), 2 deletions(-)

diff --git a/depolymerization/en.tex b/depolymerization/en.tex
index a88a041..0df7c89 100644
--- a/depolymerization/en.tex
+++ b/depolymerization/en.tex
@@ -274,20 +274,137 @@ show that the ``withdraw'' operation has completed.
 
 \section{Making Peer-to-Peer payments}
 
+This section describes how to transact directly between Taler wallets.  It is
+possible to either create a QR code to send money to another wallet, or to
+create a QR code that allows the recipient to pay the sender.
+
 \subsection{Sending money}
 
+To send money, select the ``send funds'' button just next to the current
+balance (Figure~\ref{fig:p2p:menu}). If a wallet contains multiple currencies,
+one needs to first select the desired currency.
+
+\begin{figure}[h!]
+\begin{center}
+%\includegraphics[width=0.6\textwidth]{}
+\end{center}
+\caption{The buttons for peer-to-peer payments are next to the balance on the
+  screen with the transaction history.}
+\label{fig:p2p:menu}
+\end{figure}
+
+Next, the wallet will ask for the amount to send, and ask for the destination
+(Figure~\ref{fig:p2p:amount}).  Sending back ``to a bank account'' will be
+discussed in Section~\ref{sec:to_chain}, for peer-to-peer payments select ``to
+another wallet''.
+
+\begin{figure}[h!]
+\begin{center}
+%\includegraphics[width=0.6\textwidth]{}
+\end{center}
+\caption{The buttons for peer-to-peer payments are next to the balance on the
+  screen with the transaction history.}
+\label{fig:p2p:amount}
+\end{figure}
+
+% The wallet will now show the applicable fees.  FIXME: not implemented!
+
+Finally, a purpose for the transfer must be specified
+(Figure~\ref{fig:p2p:subject}). This is basically the summary message that
+will be shown in the transaction history (of both parties) for this
+transaction.
+
+\begin{figure}[h!]
+  \begin{center}
+% FIXME: fees not shown!
+%\includegraphics[width=0.6\textwidth]{}
+\end{center}
+\caption{The buttons for peer-to-peer payments are next to the balance on the
+  screen with the transaction history.}
+\label{fig:p2p:subject}
+\end{figure}
+
+Once all of the information has been specified, the wallet will show a QR code
+that the recipient must scan to receive the funds. It is also possible to copy
+the URL encoded in the QR code to the clipboard to exchange it via some secure
+messaging application.  Note that the first person to scan the code or enter
+the URL will receive the funds.
+
+To scan the QR code, the recipient must use the QR code button in the bottom
+right corner of the Taler wallet app. To enter a URL or paste one from a
+clipboard, hold the QR code button to get to the ``Enter Taler URI'' dialog
+(Figure~\ref{fig:qr:entry}).
+
+\begin{figure}[h!]
+  \begin{center}
+%\includegraphics[width=0.6\textwidth]{}
+\end{center}
+\caption{Entering a Taler payment URL into the Android wallet requires briefly
+  holding the QR code button.}
+\label{fig:qr:entry}
+\end{figure}
+
+After scanning the QR code or pasting the URL the wallet will show the
+purpose and amount of the payment and allow the user to confirm the action
+before proceeding.
+
+% FIXME: fees not shown!
+\begin{figure}[h!]
+\begin{center}
+%\includegraphics[width=0.6\textwidth]{}
+\end{center}
+\caption{Entering a Taler payment URL into the Android wallet requires briefly
+  holding the QR code button.}
+\label{fig:qr:accept}
+\end{figure}
+
+
 \subsection{Sending invoices}
 
+To send money, select the ``receive funds'' button just next to the current
+balance (Figure~\ref{fig:p2p:menu}).  The remaining dialogs mirror the
+process for sending money, except that this time the direction of the
+transfer is reversed.
+
+% FIXME: expand once we have invoice attestation!
 
 \section{Paying Taler-enabled merchants}
 
+\subsection{Configuring the merchant backend}
 
-\section{Going back onto the chain}
+% configure currency
+% configure exchange trust
+% setup instance:
+% - add wire method
+% - configure acceptable fees
+
+\subsection{Making the payment}
+
+From the user's perspective, paying a Taler-enabled merchant is very similar
+to paying a peer-to-peer invoice, in that the user needs to scan the QR code,
+check the amount and purpose of the payment, and hit the confirm button.  With
+the WebExtension wallet, the process can be even further simplified: after
+granting the wallet the permission to ``Automatically open wallet based on
+page content'' in the settings, Web pages can directly transition into the
+wallet payment dialog without ever showing a QR code or asking the user to
+explicitly open the Taler wallet.  Note that it is also possible to make
+payments on Web sites opened in a browser on a desktop with a mobile wallet
+running on a different device.
+
+\section{Going back onto the chain} \label{sec:to_chain}
 
 Last but not least, it is possible to transfer the BITCOINBTC from the Taler
 wallet back to a Bitcoin wallet, effectively moving the funds out of the Taler
-exchange escrow and back onto the chain.
+payment system and back onto the chain.
+
+The process is started via the ``send funds'' button next to the current
+balance (Figure~\ref{fig:p2p:menu}).  When the wallet asks for the amount to
+send and the destination (Figure~\ref{fig:p2p:amount}, sending the money to a
+Bitcoin wallet corresponds to the ``to a bank account'' action, as in Bitcoin,
+the equivalent of a bank account is an actual native Bitcoin wallet.
 
+% FIXME: maybe change text shown for bitcoin?
+% FIXME: current Android wallet dialog for sending funds back onto chain is 
broken!
 
 
 \section{Future work}

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