commit cd4a79eaa1e745c50551bb20c08d9425885172b1
parent b4d936c5787492f7e3917bf30ee8a9832085fffb
Author: Florian Dold <florian.dold@gmail.com>
Date: Fri, 13 May 2016 14:03:24 +0200
address comment about undefined acronym
Diffstat:
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/articles/ui/ui.tex b/articles/ui/ui.tex
@@ -281,6 +281,7 @@ and to other currencies incurs substantial fees~\cite{BTCfees}.
There is now an extreme diversity of Bitcoin-related payment
technologies, but usability improvements are usually achieved by
adding a ``trusted'' third party, and there have been many incidents
+% FIXME: citation for embezzlement
where such parties then embezzled funds from their customers. The
classical Bitcoin payment workflow consisted of entering payment
details into a peer-to-peer application. The user would access his
@@ -445,7 +446,7 @@ that customers and merchants incur by using a particular exchange.
\end{itemize}
The specific protocol between wallet and merchant depends on the
-setting. For a traditional store, an NFC protocol might be used
+setting. For a traditional store, a near field communication (NFC) protocol might be used
between a point-of-sale system and a mobile application. In this
paper, we focus on Web payments for an online shop.
