[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[taler-marketing] branch master updated: typos
From: |
gnunet |
Subject: |
[taler-marketing] branch master updated: typos |
Date: |
Fri, 28 Jan 2022 16:48:19 +0100 |
This is an automated email from the git hooks/post-receive script.
martin-schanzenbach pushed a commit to branch master
in repository marketing.
The following commit(s) were added to refs/heads/master by this push:
new cfc01a9 typos
cfc01a9 is described below
commit cfc01a97404cf726a866ed26c26d7ee503e962d3
Author: Martin Schanzenbach <schanzen@gnunet.org>
AuthorDate: Fri Jan 28 16:48:16 2022 +0100
typos
---
2022-privacy/privacy.tex | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/2022-privacy/privacy.tex b/2022-privacy/privacy.tex
index bc6c02b..18d9f0b 100644
--- a/2022-privacy/privacy.tex
+++ b/2022-privacy/privacy.tex
@@ -84,7 +84,7 @@ are very heterogeneous and based on different principles.
Some use accounts
with balances with a blockchain used to establish a consensus on the account
balances (Bitcoin was the first currency to use it), while others allow the
transfer of fungible tokens that are disassociated from any transaction
-history (Z-cash\cite{zcash}). Among those using a blockchain, some use proof
+history (Zcash~\cite{zcash}). Among those using a blockchain, some use proof
of work (Bitcoin, Ethereum), others use proof of stake
(Ethereum, expected in Q2 2022~\cite{merge2022,nelson2021}) or most recently
proof of wasted human lifetime (Play to Earn~\cite{p2e2022}). Some are rather
@@ -113,7 +113,7 @@ may introduce new failure modes into the system. As a
result, payment service
providers are generally regulated entities, at least when they deal with
traditional fiat currencies. Examples for payment systems used with
crypto-currencies include the various proprietary crypto-trading platforms as
-well as distributed layer-2 solutions like the Lightening
+well as distributed layer-2 solutions like the Lightning
network~\cite{lightening}.
In the rest of this paper we will focus on the design principles for a Central
--
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.