[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[taler-marketing] branch master updated: cleanup
|
From: |
gnunet |
|
Subject: |
[taler-marketing] branch master updated: cleanup |
|
Date: |
Thu, 25 Jan 2024 23:04:03 +0100 |
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 d840c63 cleanup
d840c63 is described below
commit d840c63803896b63a683f0ed15650bdd3aea699f
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Thu Jan 25 23:04:00 2024 +0100
cleanup
---
ekrona/e-krona.tex | 292 ---------------
ekrona/rapport_ekrona_170920_eng.pdf | Bin 1139369 -> 0 bytes
ekrona/taler-arch-full.sh | 1 -
illiterate/illiterate.tex | 464 ------------------------
illiterate/myoralvillage.png | Bin 18528 -> 0 bytes
illiterate/taler-logo-2021-plain.pdf | Bin 2540 -> 0 bytes
pep/pep-taler-arch.svg | 669 -----------------------------------
prototype-2018/application.txt | 138 --------
8 files changed, 1564 deletions(-)
diff --git a/ekrona/e-krona.tex b/ekrona/e-krona.tex
deleted file mode 100644
index 499b520..0000000
--- a/ekrona/e-krona.tex
+++ /dev/null
@@ -1,292 +0,0 @@
-\documentclass{memoir} % {article} % {acmart}
-
-\usepackage{url}
-\usepackage{eurosym}
-\usepackage[T1]{fontenc}
-% \usepackage{lmodern}
-% \usepackage{verbatim}
-\usepackage[utf8]{inputenc}
-\usepackage{graphicx}
-\usepackage[a4paper,left=25mm,right=25mm, top=25mm, bottom=25mm]{geometry}
-
-\makeevenhead{plain}{}{}{\logo}
-\makeoddhead{plain}{}{}{\logo}
-%\makeevenfoot{plain}{}{}{}
-%\makeoddfoot{plain}{}{}{}
-
-\begin{document}
-\pagestyle{plain}
-% \thispagestyle{empty}
-
-\newcommand\logo{\includegraphics[width=0.07\textwidth]{../presentations/comprehensive/taler-big-accent.pdf}}
-
-\begin{center}
-{\huge Taler for e-Krona}
-
-\medskip
-
-% \begin{tabular}{l l}
-% Project Acronym & LAC - Latent Anonymous Commons (LAKE) \\
-% Principal Investigator & Jeffrey Burdges \\
-% Host Institution & University of Luxembourg \\
-% Main Partner & pEp SA \\
-% \end{tabular}
-\end{center}
-
-\def\red{} % FIXME
-
-
-\section*{Introduction}
-
-Taler Systems is developing an online payment system called Taler,
-that could easily fit the requirements of the e-Krona project.
-
-Taler is an open source system based on a consumer wallet, merchant
-backend and a central exchange for payment processing. It provides
-instant one-click payments, implements privacy-by-design and assures
-receiver transparency for tax purposes using modern cryptography. It
-is fast and efficient, and can hence also cover micro-payments
-(payments of 1 cent) economically.
-
-The USPs of Taler are:
-
-\begin{itemize}
-\item All operations provide cryptographically secured, with mathematical
- proofs for courts and auditors
-\item Customer payments are privacy-preserving, like cash
-\item Merchants are identifiable in each payment they receive
-\item Payments are in existing currencies
-\item Payment fraud is eliminated, short of catastrophic failure in
cryptographic primitives
-\item Linear scalability ensures Taler handles transaction volumes of widely
used systems
-\item Suitable for micro-payments due to very low transaction costs
-\item Ease of use (one-click, instant, no authentication during payment, again
like cash)
-\item Open standard protocol without patents, with free reference
implementation
-\end{itemize}
-
-The Taler architecture includes a register-based system of bank accounts
-for customers and merchants with an escrow-account for the exchange. The
-exchange signs electronic coins into existence, customers use them to sign
-contracts and merchants deposit them in return for a credit to the register.
-The exchange collects cryptographic proofs that it operates correctly, which
-are then checked by an auditor (auditor not shown):
-
-\begin{minipage}{13cm}
-\includegraphics[width=\textwidth]{taler-arch-full.pdf}
-\end{minipage}
-\begin{minipage}{3cm}
- {\Huge \}} register-based
-\vspace{3cm}
-
-{\Huge \}} value-based
-\end{minipage}
-
-
-\section*{What would a solution for a register-based e-Krona look like?}
-
-Taler's focus is on a cryptographic protocol for a value-based
-transaction system. However, Taler requires integration with
-some register-based accounting system, equivalent to traditional
-bank accounts. For this, it would be possible to use a permissioned
-block chain. Taler aggregates many small transactions from different
-customers to the same merchant, thereby reducing the transaction
-rate in the register-based solution.
-
-\section*{What would a solution for a value-based e-Krona look like?}
-
-Taler issues electronic coins based on deposits into an escrow
-account. Citizens could use their wallets to withdraw e-Krona
-from their traditional bank accounts, or they could be provided
-e-Krona directly (for example via social security) if they lack
-a bank account. Electronic coins are blindly signed
-by the issuing exchange, which is obliged to exchange e-Krona
-back into Krona when they are deposited by merchants. An auditor
-supervises the operation of the exchange.
-
-Our vision is thus very close to the electronic cash system
-``DigiCash'' proposed by David Chaum in the 1990s, except that
-Taler's design and implementation supports key features such
-as giving change, providing refunds, securely handling aborts
-and various other practical issues previous technical solutions
-lacked.
-
-\section*{What is your vision for an e-Krona?}
-% Are there other possible solutions than register-based and value-based that
you consider to be more appropriate?}
-
-We imagine a realistic e-Krona solution based on the Taler system to
-be effectively a hybrid solution, with a register-based component and
-a value based component, in order to fulfill the maximum requirements
-outlined in ``The Riksbank’s e-Krona project'' report.
-
-The e-Krona Taler wallet can exist on smartphones, in browsers, on
-smartcards or secure USB sticks. It is filled via wire-transfer to the
-Taler exchange's escrow account, where the subject identifies the
-Taler wallet eligible to withdraw the e-Krona. Regulators could
-limit the amount an entity is entitled to exchange from Krona into
-e-Krona, like ATM limits. When withdrawing electronic coins, they are
-blindly signed by the Taler exchange and stored in the consumer's wallet,
-which is value-based. The consumer can then spend its coins at
-merchants using cryptographic signatures over electronic contracts.
-Merchants must immediately deposit the coins at the exchange, which
-performs an online check for double-spending. The exchange will then
-credit the merchant's register-based accounts.
-
-Thus, the Taler system combines value-based and register-based
-accounting, providing anti-money laundering capabilities by making
-income transparent, identifying the users of the system (upon
-withdrawal and deposit), but also providing privacy for citizens by
-not requiring identification of the buyer for ordinary transactions.
-Thus, Taler is a hybrid system combining the advantages of value-based
-and register-based solutions.
-
-Specifically, Taler addresses the following requirements outlined in
-the report:
-
-\begin{description}
-\item[Specified in Swedish Krona]
- Taler is designed to work for all currencies for which
- a register-based accounting system exists.
-\item[Payment size]
- Taler is designed to handle micropayments as well as arbitrarily large
payments between consumers, companies and authorities.
- Regulation may impose limits on withdrawals and maximum amounts transacted.
-\item[Direct claim on Riksbank]
- The Taler design involves the exchange owning an escrow account
- (for example, with the Riksbank) to keep the funds to back the issued
electronic coins.
- The contractual obligations of the system are supposed to entitle the holder
of
- e-Krona to exchange them anytime into other representations of Krona.
-\item[Accessible in real-time]
- Customers and merchants always have access to their full account
- histories and their balances on their local computer. Backups and
- cross-device synchronization will also be supported.
-\item[Payments in real-time]
- Payments typically clear in one network RTT.
- The system is designed for 24/7 operations.
-\item[Offline payments]
- For Taler transactions, either the payer or the merchant must be online and
able to
- communicate with the exchange. Otherwise the merchant cannot be sure that
the payer
- did not double-spend and risks being defrauded.
-\item[Anonymous payments]
- Taler is designed for payers to remain anonymous when buying goods, unless
regulation
- requires disclosure (i.e. for particular sensitive purchases).
- However, the merchant is never anonymous.
-\item[e-Krona account]
- A register-based account is required for merchants to receive transactions.
- The exchange also must have an escrow account.
-\item[Riksbank functions]
- The Riksbank would primarily hold the escrow account. It could also either
- (1) run the operations of the exchange and guarantee the exchange of e-Krona
- in Swedish Krona directly, or (2) else audit privately operated exchanges
- similar to its regulatory oversight of conventional banks and payment
processors.
-\item[No bank account necessary]
- Taler can enable distribution of funds (i.e. from social security) directly
to
- wallets. Thus, citizens having a Taler wallet could be given remittances
without
- the need for a bank account. However, merchants must have a register-based
- bank account to receive payments.
-\item[Interest payments]
- Taler could theoretically support interest on e-Krona by varying the exchange
- rate between e-Krona and Krona. Taler can also theoretically support {\em
negative}
- interest on coins held long-term in wallets.
-\item[Connection to existing payment systems]
- With proper system integration, wire transfers, debit and credit cards or
even
- NFC-enabled ATMs could all be used to fund the e-Krona wallet.
-\end{description}
-
-Taler effectively provides electronic cash and thus solves the problem
-of gaining access to risk-free assets. As the Riksbank supervises the
-e-Krona escrow funds (either directly or by auditing the private
-operator), the government can assure citizens that they can always
-exchange e-Kronas back to cash. Thus, in Taler's design, the government
-acts as a trust anchor.
-
-Taler removes inefficiencies the current system creates through fraud
-risks inherent in register-based systems. In Taler, citizens only
-ever authenticate to their bank (or social services). By avoiding
-disclosing personally identifying information or even performing
-credit card-style authentication via third parties, Taler improves
-usability and eliminates most vectors of authentication token
-compromise.
-
-
-\section*{What challenges and opportunities do you envisage?}
-
-Taler provides the advantages of cash while supporting taxation and
-limiting criminal abuse, as recipients of payments are identifiable.
-Furthermore, Taler transactions are faster, easier and more secure
-than cash or credit card transactions.
-
-The main challenge is the integration of the Taler merchant backend
-into the diverse POS systems that exist today. While integrating
-Taler can be done with a few hundred lines of code, NFC-enabled POS
-systems would require at least a firmware update. Convincing vendors
-to upgrade their systems will thus require a major up-front
-investment.
-
-Taler also requires further development to ensure that wallets are
-available on all relevant platforms. However, consumer systems are
-much less diverse and hence this effort is significantly smaller.
-
-Deploying Taler at scale should have no major impact on monetary
-policy because the issued e-Krona would be 1:1 backed by Swedish Krona
-in the escrow account at the Riksbank. However, if there is a
-significant shift from the use of credit-cards to e-Krona, there might
-be a reduction in M2 from fractional reserve banking as e-Krona is
-debit-based while credit-cards are credit-based. Thus, instead of
-commercial bank money being created from debts, consumers may
-effectively hold e-Krona claims against the escrow account at the
-central bank. The resulting reduction in M2, and the loss of revenue
-at banks from credit-card interest payments, may require adjustments
-in monetary policies.
-
-
-\section*{What is missing in our concept?}
-
-
-A key requirement for governments considering electronic payment
-systems is the preservation of the Commons. Cash is a Commons as all
-market participants have equal liberties in handling cash. If cash is
-replaced by proprietary solutions such as Visa's credit card system or
-ApplePay, these companies have exclusive control over critical
-infrastructure, which often leads to high fees. Worse, such payment
-service providers may discriminate against individuals or certain
-businesses and can refuse service to individuals or businesses without
-judicial oversight.
-
-In contrast, Taler is implemented as Free Software distributed under
-the GNU General Public License, and without patent encumbrances. This
-ensures that any government retains sovereignty after deploying Taler,
-as it can liberally inspect, use and modify the software. In
-particular, no foreign government or company can impose their own
-restrictions or regulatory regime. Governments can foster competition
-between multiple Taler exchange operators, or run a Taler exchange as
-a government monopoly equivalent to a government mint for coins.
-
-
-
-\section*{Contact}
-
-\renewcommand\logo{}
-
-\begin{center}
-
\includegraphics[width=0.5\textwidth]{../presentations/comprehensive/taler-big-accent.pdf}
- \vfill
- {\Large \url{https://taler.net/}}
- \vfill
-
-\begin{tabular}{l l l}
-C. Grothoff & grothoff@taler.net & +41 78 692 6894 \\
-L. Schumacher & schumacher@taler.net & +41 79 865 9365 \\
-M. Widmer & widmer@taler.net & +41 79 900 4000 \\
-\end{tabular}
-\end{center}
-
-\vfill
-
-\includegraphics[width=0.2\textwidth]{../presentations/investors/partner-logos/ashoka.png}
-\hfill
-
\includegraphics[width=0.1\textwidth]{../presentations/investors/partner-logos/inria.png}
-\hfill
-\includegraphics[width=0.1\textwidth]{../presentations/investors/partner-logos/tum.png}
-\hfill
-
\includegraphics[width=0.1\textwidth]{../presentations/investors/partner-logos/gnu.jpeg}
-
-\end{document}
-
diff --git a/ekrona/rapport_ekrona_170920_eng.pdf
b/ekrona/rapport_ekrona_170920_eng.pdf
deleted file mode 100644
index 1cbf7f4..0000000
Binary files a/ekrona/rapport_ekrona_170920_eng.pdf and /dev/null differ
diff --git a/ekrona/taler-arch-full.sh b/ekrona/taler-arch-full.sh
deleted file mode 100644
index d432613..0000000
--- a/ekrona/taler-arch-full.sh
+++ /dev/null
@@ -1 +0,0 @@
-inkscape ../taler-arch-full.svg --export-pdf=taler-arch-full.pdf
diff --git a/illiterate/illiterate.tex b/illiterate/illiterate.tex
deleted file mode 100644
index e181d42..0000000
--- a/illiterate/illiterate.tex
+++ /dev/null
@@ -1,464 +0,0 @@
-\documentclass{article} % {article} % {acmart}
-
-\usepackage{url}
-\usepackage{eurosym}
-\usepackage[T1]{fontenc}
-% \usepackage{lmodern}
-% \usepackage{verbatim}
-\usepackage[utf8]{inputenc}
-\usepackage{graphicx}
-\usepackage[a4paper,left=25mm,right=25mm, top=25mm, bottom=25mm]{geometry}
-\usepackage{enumerate}
-
-\begin{document}
-\pagestyle{plain}
-% \thispagestyle{empty}
-
-\newcommand\logo{\includegraphics[width=0.07\textwidth]{../presentations/comprehensive/taler-big-accent.pdf}}
-
-\begin{center}
-{\huge Centrally Banked Digital Currency \\ for Illiterate and Low-literate
People }
-\end{center}
-
-\begin{center}
-\includegraphics[width=3cm]{taler-logo-2021-plain.pdf}
-\hskip1cm
-\includegraphics[width=5cm]{myoralvillage.png}
-\end{center}
-
-
-\def\red{} % FIXME
-
-\begin{abstract}
- Taler is a cryptographic protocol with a Free Software reference
- implementation for a value-based transaction system. Taler payments are
- executed in fiat currency with privacy and regulatory compliance, which
- makes Taler suitable for a Central Bank Digital Currency (CBDC).
-
- My Oral Village (MOVE) has been developing user interfaces for electronic
- payment systems that can be used by illiterate and innumerate groups,
- with field experience from Kenya and Pakistan where substantial
- portions of the population cannot read multi-digit
- numbers or text.
-
- We propose to integrate the user interface work of My Oral Village
- with the Taler payment system to create an inclusive payment solution
- that minimizes the digital divide.
-\end{abstract}
-
-
-\section{Introduction to GNU Taler}
-
-Taler Systems SA is developing an online payment system called Taler, that
-broadly fits the requirements of CBDCs. The major parts
-of the system have already been built. Taler's unique focus is
-on regulatory compliance, efficiency and data minimization. Cryptography is
-employed for security. While Taler includes privacy features, it can still
-guarantee that cash flows to merchants/retailers are transparent for anti-%
-money-laundering (AML) and know-your-customer (KYC) auditing requirements.
-Transactions with Taler execute in one network round-trip time. Taler is
-economically viable for micro-payments (payments of 1 cent) as its design
-minimizes requirements in terms of CPU time (typically less than 1 M cycles
-per transaction), bandwidth (typically 1-10 KB/transaction), and storage
-(again a few KB/transaction, with the ability to delete old data once legal
-data retention periods have expired).
-
-\subsection{Unique sales propositions}
-
-The unique sales propositions of Taler as it exists today are:
-
-\begin{itemize}
-\item All operations are cryptographically secured, with mathematically sound
- proofs for courts and auditors
-\item Customer payments are privacy-preserving, like cash
-\item Merchants are identifiable in each payment they receive
-\item Payments are in existing currencies
-\item Payment fraud is eliminated, short of catastrophic failure in
cryptographic primitives
-\item Linear scalability ensures Taler can handle transaction volumes seen in
global payment systems today
-\item Suitable for micro-payments due to very low transaction costs
-\item The patent-free, open standard protocol and the free reference
implementation provide
- long-term sustainability and technological independence from foreign
providers
-%\item Can be used for smart contracts
-\item Ease of use (one-click, instant, no authentication during payment, again
like cash)
-\end{itemize}
-
-The proposed work will extend this list by making Taler {\bf suitable for
-illiterate and innumerate adults}. After consultation with My Oral Village, we
-believe the payment process with Taler can be made safe and convenient for
-their use. Based on years of direct field research, MOVE develops
-locally-validated solutions that blend graphical representations of money,
-iconographic navigation cues and metaphors, and experimental insights from
-cognitive psychology. We also have plans to make Taler suitable for (numerate)
-children.
-
-\subsection{Taler architecture}
-
-The Taler architecture includes a register-based system of bank accounts
-for customers and merchants with an escrow-account for the exchange. The
-exchange signs electronic coins into existence, customers use them to sign
-contracts and merchants deposit them in return for a credit to the register.
-The exchange collects cryptographic proofs that it operates correctly, which
-are then checked by an auditor (auditor not shown):
-
-\begin{center}
-\includegraphics[width=\textwidth]{../presentations/comprehensive/operations.png}
-\end{center}
-
-Thus, the following components form the core of the system:
-
-\begin{enumerate}
- \item An \emph{Electronic wallet} software stores cryptographic
- tokens of value (called digital coins), implemented via blind
- signatures. Wallets are typically managed by the end user; a
- \emph{wallet provider} can manage storage of cryptographic
- material for the user, providing backup, synchronization and
- recovery.
-
- \item The \emph{Exchange} issues digital coins to wallets, after
- receiving fiat money in an escrow account, or based on a
- central bank creating the digital coins as a central bank liability.
- The authorized electronic
- wallet is identified using an ephemeral \emph{reserve public key}
- encoded in the wire payment instructions. As blind signatures are
- used, the exchange knows that it issued coins of a certain
- monetary value, but not to which wallet. Digital coins are always
- denominated in a fiat currency (e.g. Euro).
-
- \item The \emph{Merchant} proposes contracts to customers and
- receives payment in the form of contracts signed using digital
- coins. The merchant must then immediately clear these
- \emph{deposit permissions} with the exchange. The exchange checks
- against double-spending, and if everything is in order provides
- the merchant with an instant \emph{deposit confirmation}. After
- possibly aggregating many micro-transactions, the exchange sends
- money from the escrow account to the merchant's bank account.
-
- \item \emph{Auditors} are entities that certify which Exchanges can
- be trusted as legitimate. They are not strictly needed in a CBDC
- setting, but can be used by the central bank to verify that its
- own operations have not been compromised.
-\end{enumerate}
-
-The implementation of all core components is licensed as free and open
-source software (FOSS).
-
-
-\subsection{Vision}
-
-Our vision is close to the electronic cash system ``DigiCash'' proposed by
-David Chaum in the 1990s, except that Taler's design and implementation
-supports key features such as giving change, providing refunds, securely
-handling aborts and various other practical issues previous technical
-solutions lacked.
-
-In summary, the overall system roughly operates as follows: The Taler wallet
-is filled via wire-transfer to the Taler exchange's escrow account, where the
-subject identifies the Taler wallet eligible to withdraw the CBDC. Regulators
-can limit the amount an entity is entitled to exchange from rand into CBDC,
-like ATM withdrawal limits. When withdrawing electronic coins, they are
-blindly signed by the Taler exchange and stored in the consumer's wallet,
-which is value-based. The consumer can then spend its coins at merchants
-using cryptographic signatures over electronic contracts. Merchants must
-immediately deposit the coins at the exchange, which performs an online check
-for double-spending. The exchange will then credit the merchant's
-register-based accounts using aggregated wire-transfers.
-
-
-\subsection{Company Profile: My Oral Village}
-
-My Oral Village is a not-for-profit social enterprise incorporated in
-Canada. Engaged in human-centred design and field research at the oral-digital
-frontier, we build trusted, usable financial-interface solutions for the
-world's billion functionally illiterate and innumerate adults to support their
-transition into financial inclusion.
-
-Our suite of ``oral information management'' (OIM) tools and solutions enable
-poorly schooled individuals to safely and confidently engage in formal
-financial transactions. We are currently piloting a hybrid (digital and
-paper-based) solution for entrepreneurial pastoralists in northern Kenya, and
-testing our ``cash calculator'' for Android in Pakistan. We recently designed
-a passbook for new credit union members in Sierra Leone. With MicroSave, we
-wireframed a full 'concept-level' mobile money app for northern India. Our OIM
-solution for savings groups in the Solomon Islands has been adopted by the
-Ministry of Women and the Anglican Church of Melanesia. We are also developing
-a field experiment in Kenya with a team of numerical cognition researchers at
-the Universities of Tuebingen and Western Ontario.
-
-
-\subsection{Company profile: Taler Systems SA}
-
-Taler Systems SA was established in 2016 and is headquartered in Luxembourg,
-but also has developers in Argentina, Brazil, Germany, Switzerland and the
-United States of America. Taler Systems SA was founded as a startup by with
-support from INRIA, the French national institute for research in computer
-security (\url{https://www.inria.fr/}) and the Free Software community
-(\url{https://www.gnu.org/}). % The company is privately owned and debt-free.
-
-Taler Systems SA business model is to provide technical support for users of
-the Taler payment system, and to possibly dual-license the Free Software for
-users that have specific licensing requirements. Taler Systems is in the
-unique position of not having technological business secrets to protect, as
-all of our code and documentation is freely available. Thus, we can easily
-find and train local partners in our technology and focus on providing
-second-level support.
-
-We have been involved in consultations with the Swiss National Bank, the
-European Central Bank, and the Swedish Riksbank, as all three were interested
-in Taler in their respective CBDC initiatives. However, none of them is yet
-at the point where the respective central banks have made any commitments for
-any particular direction or technical solution.
-
-\section*{Contact}
-
-\begin{tabular}{l l}
- Dr. C. Grothoff & grothoff@taler.net \\
- Dr. F. Dold & dold@taler.net \\
- L. Schumacher & schumacher@taler.net \\
- B. Matthews & brett@myoralvillage.org \\
-\end{tabular}
-
-\vfill
-
-\includegraphics[width=0.05\textwidth]{../presentations/investors/partner-logos/ashoka.png}
-\hfill
-\includegraphics[width=0.1\textwidth]{../presentations/investors/partner-logos/inria.png}
-\hfill
-\includegraphics[width=0.1\textwidth]{../presentations/comprehensive/bfh.png}
-\hfill
-\includegraphics[width=0.025\textwidth]{../presentations/investors/partner-logos/tum.png}
-\hfill
-\includegraphics[width=0.025\textwidth]{../presentations/investors/partner-logos/gnu.jpeg}
-
-\end{document}
-
-
-
-\subsection*{What would a solution for a register-based CBDC look like?}
-
-
-\subsection*{What would a solution for a value-based CBDC look like?}
-
-
-\section*{What is your vision for an CBDC?}
-% Are there other possible solutions than register-based and value-based that
you consider to be more appropriate?}
-
-
-
-
-\section*{What challenges and opportunities do you envisage?}
-
-Taler provides the advantages of cash while supporting taxation and
-limiting criminal abuse, as recipients of payments are identifiable.
-Furthermore, Taler transactions are faster, easier and more secure
-than cash or credit card transactions.
-
-The main challenge is the integration of the Taler merchant backend
-into the diverse POS systems that exist today. While integrating
-Taler can be done with a few hundred lines of code, NFC-enabled POS
-systems would require at least a firmware update. Convincing vendors
-to upgrade their systems will thus require a major up-front
-investment.
-
-Taler also requires further development to ensure that wallets are
-available on all relevant platforms. However, consumer systems are
-much less diverse and hence this effort is significantly smaller.
-
-Deploying Taler at scale should have no major impact on monetary
-policy because the issued CBDC would be 1:1 backed by fiat currency
-in the escrow account at the central bank. However, if there is a
-significant shift from the use of credit-cards to CBDC, there might
-be a reduction in M2 from fractional reserve banking as CBDC is
-debit-based while credit-cards are credit-based. Thus, instead of
-commercial bank money being created from debts, consumers may
-effectively hold CBDC claims against the escrow account at the
-central bank. The resulting reduction in M2, and the loss of revenue
-at banks from credit-card interest payments, may require adjustments
-in monetary policies.
-
-
-\section*{What is missing in our concept?}
-
-
-A key requirement for governments considering electronic payment
-systems is the preservation of the Commons. Cash is a Commons as all
-market participants have equal liberties in handling cash. If cash is
-replaced by proprietary solutions such as Visa's credit card system or
-ApplePay, these companies have exclusive control over critical
-infrastructure, which often leads to high fees. Worse, such payment
-service providers may discriminate against individuals or certain
-businesses and can refuse service to individuals or businesses without
-judicial oversight.
-
-In contrast, Taler is implemented as Free Software distributed under
-the GNU General Public License, and without patent encumbrances. This
-ensures that any government retains sovereignty after deploying Taler,
-as it can liberally inspect, use and modify the software. In
-particular, no foreign government or company can impose their own
-restrictions or regulatory regime. Governments can foster competition
-between multiple Taler exchange operators, or run a Taler exchange as
-a government monopoly equivalent to a government mint for coins.
-
-
-
-\section{Addressing CBDC Requirements}
-
-We now sketch how the Taler components map to a Centrally Banked Digital
-Currency system run by the ECB or national central banks (NCBs), according to
-the draft requirements. Taler is a value-based payment system (as opposed to
-an account-based system), and thus we will address the common requirements
-C1-C8 and requirements V1-V4 specific to the value-based model.
-
-\paragraph{C1. Tokenization:} \emph{Units of digital currency (CBDC units) are
only created against money
-blocked on a transit account, which will be held by ECB/NCBs}.
-
-The ECB/NCBs would simultaneously take the role of the Taler Exchange
-and Taler Auditor (or could outsource operations to qualified third parties).
-
-\paragraph{C2. Issuance:} \emph{A central authority creates new CBDC units on
-the reception of the transfer of an equivalent EUR amount from the
-participating bank to the transit account. The same logic applies to the
-destruction of existing CBDC units, where the central authority destroys CBDC
-and releases EUR that were previously held by the ECB/NCBs in the transit
-account.}
-
-The ECB/NCBs create new CBDC units by issuing Taler digital coins,
-and destroy CBDC units by accepting digital coin deposits from merchants,
subsequently releasing
-funds blocked in the escrow account and sending them to the merchant's bank
account.
-
-\paragraph{C4. 1-on-1 parity rule:} \emph{The parity rule applies when CBDC
units are newly created or destroyed,
-meaning that for each EUR blocked in (released from) the transit account there
will be exactly
-one CBDC created (destroyed). The parity rule also applies when CBDC are
exchanged for
-commercial bank deposits or physical cash, and vice versa.}
-
-Digital coins in GNU Taler correspond 1-on-1 to a
-value in a fiat currency such as the Euro.
-
-\paragraph{C4. Two-tier structure:} \emph{The central authority issues CBDC
only to entities entitled to deposit funds
-in the transit account held at ECB/NCBs in exchange for newly issued CBDC
units. Also, end-
-users’ access to the CBDC payment system is intermediated via other entitled
entities, acting as
-gateways. All these entities, hereafter “tier-2 entities”, could be commercial
banks or non-banks
-(for example, payment service providers (PSPs), wallet providers etc.).}
-
-
-With Taler, national banks could serve as
-the primary Tier-2 entity, establish customer's identities (KYC) during bank
-account setup, and facilitate the transfer from a customer's bank
-account to the exchange's escrow account. A secondary Tier-2 entity are the
wallet providers.
-Banks can serve as wallet providers, but other third party businesses could
offer
-a wallet backup/sync/restore services as well. Customers are also given the
option to be
-responsible for the security of their wallet on their own, and manage private
keys directly
-and on their own device.
-
-
-\paragraph{C5. Compliance with AML regulation:} \emph{Transactions with
amounts above a certain threshold must be
-disclosed to relevant parties as required by the AML regulation. In general,
the system must be
-designed in a way that discourages end-users from using it for anonymous
large-value
-transactions.}
-
-Strict withdrawal limits can
-be placed on customers' bank accounts. Merchants can be required to collect
-customer data for critical transactions. Due to the technical measures
-that provide transparency of cash flows to merchants, the compliance of
-merchants is easy to verify.
-
-\paragraph{C6. Fees:} \emph{The system should enable fee collection. The
issuance of CBDC to banks and the
-destruction of returned CBDC are free of charge for the entitled tier-2
entities (i.e. banks). Tier-2
-entities can, however, charge fees to end-users for services they provide,
such as their
-involvement in the transfers of CBDC and/or the exchange of EUR into CBDC and
vice versa.}
-
-Taler has a flexible fee structure that is easily configured so that Tier-2
banks
-can charge for CBDC creation and other activities.
-
-
-\paragraph{C7. Availability:} \emph{Payments are processed 24 hours a day, 7
days a week, 365 days a year, without
-operational downtimes.}
-
-Taler requires no manual processing and can be made highly
-available with standard software deployment and operations techniques.
-
-
-\paragraph{C8. Throughput, transaction time and micropayments:} \emph{The
-payment system must be able to handle a sufficiently large amount of
-transactions. Each transaction must be processed real-time (to be compliant
-with the SEPA Instant Credit Transfer (SCT Inst) scheme, the transaction time
-would have to be maximum ten seconds). Furthermore, the payment system
-should/could enable micropayments (low value, large volume, low cost, real time
-transactions).}
-
-Transactions
-with Taler are processed in the order of milliseconds. Unlike DLTs, Taler can
-be easily scaled both horizontally (sharding, more processing nodes) and
-vertically (faster machines). Since multiple payments to a merchant can be
aggregated into
-one bank transfer, even micropayments with fractions of a cent are possible.
All coins
-are issued with expiration dates, ensuring that the exchange may eventually
delete ancient
-transactions.
-
-\paragraph{V1. Non-interest-bearing:} \emph{In the value-based model, holdings
of CBDC do not bear interest - neither
-positive nor negative.}
-
-In Taler, digital coins do not bear interest; however,
-when coins expire it is possible to charge fees when the electronic wallets
trade
-expiring coins for fresh coins. This feature may be used to
-provide a mechanism for negative interest rates (for non-circulating coins).
-
-
-\paragraph{V2. Limitation of bank runs:} \emph{In the value-based model, to
avoid a situation, in which end-users
-(suddenly) shift large amounts of their commercial bank deposits to CBDC,
daily (potentially also
-weekly or monthly) limits should be imposed on the amount that can be
converted from
-commercial bank deposits into CBDC.}
-
-Bank runs are discouraged and limited with Taler: (1) Withdrawal
-limits can be imposed by the Tier-2 banks on the withdrawal of CBDC units; (2)
wallet providers may place limits
-on how much money can be stored in online wallets; (3) customers that mange
their own wallet are discouraged from
-storing large amounts of CBDC units in their wallets, as they must ensure its
safety similar to a physical wallet;
-(4) modest expiration times with modest refresh fees make hoarding coins
unattractive.
-
-
-\paragraph{V3. Anonymity and AML:} \emph{The system should allow anonymous
low-value transactions (below a
-certain amount used as threshold). Moreover, it should be possible to trace
large-value
-transactions and link them to the identities of the participants (through
KYC). Furthermore, as
-countermeasure against splitting large-value transactions into multiple
low-value anonymous
-transactions, it should be possible to identify multiple low-value
transactions which are
-processed within a certain period of time and which sum up to an amount
greater than the
-chosen threshold.}
-
-The exchange does not know which customer owns which coin
-due to the use of blind signatures during the withdrawal process.
-AML measures are based on the \emph{income transparency} feature,
-where cash flows to merchants are visible to the exchanges (and
-thus ECB/NCBs). As the merchant redeems CBDC units with a transaction to
their bank account, the KYC process
-already happened when the merchant opened their SEPA bank account.
Furthermore, the
-deposit permissions are linked to the contract with the customer, allowing
authorities
-to validate the plausiblity of the transaction during tax audits.
-With Taler, ownership of digital coins between mutually distrusting parties
can only be securely transferred with a digital coin deposit via the exchange.
-This discourages ``invisible'' payments by sharing digital coins between
wallets
-without involving the exchange.
-
-\paragraph{V4. Ownership and spending rights of CBDC:} \emph{In the
value-based model, units of CBDC are held by
-end-users themselves. Each end-user has cryptographic information (e.g.
private keys, other
-secrets) without which CBDC units associated with that particular
cryptographic information
-material cannot be spent. Spending rights are defined by technology (e.g. if
you have private
-keys you can spend).}
-
-Technically literate
-users have the option to manage their own wallets and private keys, whereas
-other users can use wallet backup/sync/restore providers.
-
-\section*{Contrast and Relationship to DLT-based Systems}
-
-The Taler payment system is independent from Distributed Leder
-Technology (DLT) systems. In particular, Taler payments are not
-necessarily backed by any blockchain or cryptocurrency. Even though
-Taler uses cryptographically secured payment tokens, it is distinct
-from ``cryptocurrencies'': Taler is a very efficient electronic
-payment system with certain characteristics like cash, but it is not a
-currency. Taler is designed to serve as a payment instrument for
-retail commerce, in contrast to DLTs which are generally used more as
-a long-term stores-of-value or as speculative assets.
-
-Some technological advancements made by DLTs could potentially benefit Taler.
-For example, public cryptographic key material and data relevant for auditing
-could be further secured by a distributed ledger. Yet a distributed ledger is
-not mandatory to operate Taler, as payments are facilitated by a federation of
-trusted entities, with oversight from each other and/or a central institution,
-not too dissimilar from how traditional banking systems work.
diff --git a/illiterate/myoralvillage.png b/illiterate/myoralvillage.png
deleted file mode 100644
index 2d7c315..0000000
Binary files a/illiterate/myoralvillage.png and /dev/null differ
diff --git a/illiterate/taler-logo-2021-plain.pdf
b/illiterate/taler-logo-2021-plain.pdf
deleted file mode 100644
index 1f817a5..0000000
Binary files a/illiterate/taler-logo-2021-plain.pdf and /dev/null differ
diff --git a/pep/pep-taler-arch.svg b/pep/pep-taler-arch.svg
deleted file mode 100644
index 6d3691e..0000000
--- a/pep/pep-taler-arch.svg
+++ /dev/null
@@ -1,669 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<svg
- xmlns:dc="http://purl.org/dc/elements/1.1/";
- xmlns:cc="http://creativecommons.org/ns#";
- xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#";
- xmlns:svg="http://www.w3.org/2000/svg";
- xmlns="http://www.w3.org/2000/svg";
- xmlns:xlink="http://www.w3.org/1999/xlink";
- xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd";
- xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape";
- sodipodi:docname="pep-taler-arch.svg"
- inkscape:version="1.0 (4035a4fb49, 2020-05-01)"
- id="svg17046"
- version="1.1"
- viewBox="0 0 210 297"
- height="297mm"
- width="210mm">
- <defs
- id="defs17040">
- <marker
- inkscape:stockid="Arrow1Lend"
- orient="auto"
- refY="0"
- refX="0"
- id="Arrow1Lend"
- style="overflow:visible"
- inkscape:isstock="true"
- inkscape:collect="always">
- <path
- id="path56929"
- d="M 0,0 5,-5 -12.5,0 5,5 Z"
-
style="fill:#000000;fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:1pt;stroke-opacity:1"
- transform="matrix(-0.8,0,0,-0.8,-10,0)" />
- </marker>
- <marker
- inkscape:isstock="true"
- style="overflow:visible"
- id="marker10915"
- refX="0"
- refY="0"
- orient="auto"
- inkscape:stockid="Arrow1Lend">
- <path
- transform="matrix(-0.8,0,0,-0.8,-10,0)"
-
style="fill:#000000;fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:1pt;stroke-opacity:1"
- d="M 0,0 5,-5 -12.5,0 5,5 Z"
- id="path10913" />
- </marker>
- <radialGradient
- inkscape:collect="always"
- xlink:href="#linearGradient57292"
- id="radialGradient57499"
- gradientUnits="userSpaceOnUse"
- gradientTransform="matrix(1,0,0,0.12311535,84.852814,197.72798)"
- cx="526.22192"
- cy="462.79678"
- fx="526.22192"
- fy="462.79678"
- r="155.8974" />
- <linearGradient
- inkscape:collect="always"
- id="linearGradient57292">
- <stop
- style="stop-color:#a7ffff;stop-opacity:1;"
- offset="0"
- id="stop57288" />
- <stop
- style="stop-color:#a7ffff;stop-opacity:0;"
- offset="1"
- id="stop57290" />
- </linearGradient>
- <marker
- inkscape:stockid="Arrow1Lend"
- orient="auto"
- refY="0"
- refX="0"
- id="marker57204"
- style="overflow:visible"
- inkscape:isstock="true">
- <path
- id="path57202"
- d="M 0,0 5,-5 -12.5,0 5,5 Z"
-
style="fill:#a7ffff;fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:1pt;stroke-opacity:1"
- transform="matrix(-0.8,0,0,-0.8,-10,0)" />
- </marker>
- <marker
- inkscape:stockid="Arrow1Lstart"
- orient="auto"
- refY="0"
- refX="0"
- id="Arrow1Lstart"
- style="overflow:visible"
- inkscape:isstock="true"
- inkscape:collect="always">
- <path
- id="path10955"
- d="M 0,0 5,-5 -12.5,0 5,5 Z"
-
style="fill:#000000;fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:1pt;stroke-opacity:1"
- transform="matrix(0.8,0,0,0.8,10,0)" />
- </marker>
- <marker
- inkscape:isstock="true"
- style="overflow:visible"
- id="marker11275"
- refX="0"
- refY="0"
- orient="auto"
- inkscape:stockid="Arrow1Lend"
- inkscape:collect="always">
- <path
- transform="matrix(-0.8,0,0,-0.8,-10,0)"
-
style="fill:#000000;fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:1pt;stroke-opacity:1"
- d="M 0,0 5,-5 -12.5,0 5,5 Z"
- id="path11273" />
- </marker>
- <radialGradient
- inkscape:collect="always"
- xlink:href="#linearGradient57292"
- id="radialGradient57499-5"
- gradientUnits="userSpaceOnUse"
-
gradientTransform="matrix(0.11701702,0,0,0.01440659,84.246916,23.615455)"
- cx="526.22192"
- cy="462.79678"
- fx="526.22192"
- fy="462.79678"
- r="155.8974" />
- <marker
- inkscape:stockid="Arrow1Lend"
- orient="auto"
- refY="0"
- refX="0"
- id="marker57204-8"
- style="overflow:visible"
- inkscape:isstock="true">
- <path
- inkscape:connector-curvature="0"
- id="path57202-0"
- d="M 0,0 5,-5 -12.5,0 5,5 Z"
-
style="fill:#a7ffff;fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:1pt;stroke-opacity:1"
- transform="matrix(-0.8,0,0,-0.8,-10,0)" />
- </marker>
- <marker
- inkscape:stockid="Arrow1Lstart"
- orient="auto"
- refY="0"
- refX="0"
- id="Arrow1Lstart-9"
- style="overflow:visible"
- inkscape:isstock="true">
- <path
- inkscape:connector-curvature="0"
- id="path10955-7"
- d="M 0,0 5,-5 -12.5,0 5,5 Z"
-
style="fill:#000000;fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:1pt;stroke-opacity:1"
- transform="matrix(0.8,0,0,0.8,10,0)" />
- </marker>
- <marker
- inkscape:isstock="true"
- style="overflow:visible"
- id="marker11275-3"
- refX="0"
- refY="0"
- orient="auto"
- inkscape:stockid="Arrow1Lend">
- <path
- inkscape:connector-curvature="0"
- transform="matrix(-0.8,0,0,-0.8,-10,0)"
-
style="fill:#000000;fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:1pt;stroke-opacity:1"
- d="M 0,0 5,-5 -12.5,0 5,5 Z"
- id="path11273-6" />
- </marker>
- <marker
- inkscape:isstock="true"
- style="overflow:visible"
- id="marker11960"
- refX="0"
- refY="0"
- orient="auto"
- inkscape:stockid="Arrow1Lstart">
- <path
- transform="matrix(0.8,0,0,0.8,10,0)"
-
style="fill:#000000;fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:1pt;stroke-opacity:1"
- d="M 0,0 5,-5 -12.5,0 5,5 Z"
- id="path11958" />
- </marker>
- <marker
- inkscape:stockid="Arrow1Lend"
- orient="auto"
- refY="0"
- refX="0"
- id="marker12042"
- style="overflow:visible"
- inkscape:isstock="true"
- inkscape:collect="always">
- <path
- id="path12040"
- d="M 0,0 5,-5 -12.5,0 5,5 Z"
-
style="fill:#000000;fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:1pt;stroke-opacity:1"
- transform="matrix(-0.8,0,0,-0.8,-10,0)" />
- </marker>
- <marker
- inkscape:isstock="true"
- style="overflow:visible"
- id="marker12132"
- refX="0"
- refY="0"
- orient="auto"
- inkscape:stockid="Arrow1Lend">
- <path
- transform="matrix(-0.8,0,0,-0.8,-10,0)"
-
style="fill:#000000;fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:1pt;stroke-opacity:1"
- d="M 0,0 5,-5 -12.5,0 5,5 Z"
- id="path12130" />
- </marker>
- </defs>
- <sodipodi:namedview
- inkscape:window-maximized="1"
- inkscape:window-y="0"
- inkscape:window-x="3840"
- inkscape:window-height="2086"
- inkscape:window-width="3840"
- showgrid="false"
- inkscape:document-rotation="0"
- inkscape:current-layer="layer1"
- inkscape:document-units="mm"
- inkscape:cy="361.5953"
- inkscape:cx="404.76214"
- inkscape:zoom="2.8"
- inkscape:pageshadow="2"
- inkscape:pageopacity="0.0"
- borderopacity="1.0"
- bordercolor="#666666"
- pagecolor="#ffffff"
- id="base" />
- <metadata
- id="metadata17043">
- <rdf:RDF>
- <cc:Work
- rdf:about="">
- <dc:format>image/svg+xml</dc:format>
- <dc:type
- rdf:resource="http://purl.org/dc/dcmitype/StillImage"; />
- <dc:title></dc:title>
- </cc:Work>
- </rdf:RDF>
- </metadata>
- <g
- id="layer1"
- inkscape:groupmode="layer"
- inkscape:label="Layer 1">
- <rect
-
style="opacity:0.6;fill:#a7ffff;fill-opacity:1;stroke:#00ff00;stroke-width:0.101595;stroke-linejoin:round;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1"
- id="rect54956-3"
- width="38.29689"
- height="41.305897"
- x="3.8212283"
- y="7.0921359"
- ry="8.0270567" />
- <g
- id="g56735"
- transform="matrix(0.11701702,0,0,0.11701702,-48.331595,4.6312035)">
- <text
- id="text56430"
- y="300"
- x="609.28101"
-
style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:53.3333px;line-height:45px;font-family:'Bitstream
Charter';-inkscape-font-specification:'Bitstream
Charter';text-align:center;letter-spacing:0px;word-spacing:0px;text-anchor:middle;fill:#000000;fill-opacity:1;stroke:none;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
- xml:space="preserve"><tspan
- y="300"
- x="609.28101"
- id="tspan56428"
- sodipodi:role="line">Payer's</tspan><tspan
- id="tspan56432"
- y="345"
- x="609.28101"
- sodipodi:role="line">Bank</tspan></text>
- <g
- id="g7071-9"
- transform="matrix(0.31078808,0,0,0.31078808,513.21117,49.678125)">
- <g
- id="g1327-5">
- <path
- d="M 70.693333,1.8858667 C 26.602667,1.8858667 1.8176,24.6816
1.8176,71.2576 v 480.1312 c 0,43.56693 22.288,66.3776 66.338133,66.3776 H
550.31467 c 44.0608,0 66.3776,-21.66933 66.3776,-66.3776 V 71.2576 c
0,-45.441067 -22.3168,-69.3717333 -67.75574,-69.3717333 -0.004,0
-478.394663,-0.1525334 -478.243197,0 z"
- style="fill:#111111;stroke:#eeeeee;stroke-width:3.6352"
- id="path1329-9"
- inkscape:connector-curvature="0" />
- </g>
- <path
-
style="font-size:12px;opacity:0.2;fill:#ffffff;fill-opacity:1;fill-rule:evenodd;stroke:#ffffff;stroke-width:1.32418;stroke-opacity:1"
- d="M 308.11126,42.898171 39.247865,247.59942 H 93.020191 V
575.98448 H 254.33859 V 441.27715 h 111.23247 l 3.7e-4,134.70733 H 523.20236 V
247.59942 h 53.77269 z"
- id="path645-7"
- sodipodi:nodetypes="cccccccccccccc"
- inkscape:connector-curvature="0" />
- <path
- sodipodi:nodetypes="cccccccccccccc"
- id="path3198-2"
- d="M 308.11126,32.231504 39.247865,236.93276 H 93.020191 V
575.98448 H 254.33859 V 441.27715 h 111.23247 l 3.7e-4,134.70733 H 523.20236 V
236.93276 h 53.77269 z"
-
style="font-size:12px;opacity:1;fill:none;fill-opacity:1;fill-rule:evenodd;stroke:#ffffff;stroke-width:21.3333;stroke-linejoin:round;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1"
- inkscape:connector-curvature="0" />
- <g
- id="g4998-1"
- transform="translate(-177.88465,62.418967)">
- <g
- id="g5004-4">
- <path
-
style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:323.145px;line-height:125%;font-family:'Arial
Unicode MS';-inkscape-font-specification:'Arial Unicode
MS';text-align:start;writing-mode:lr-tb;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;stroke-width:1.06667px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
- d="m 496.42877,164.09649 c 0.24375,0.10338 1.15824,0.30988
2.74347,0.61951 24.99587,4.13015 43.77336,11.66746 56.3325,22.61192
12.55879,10.94468 18.83828,25.29652 18.83846,43.05557 -1.8e-4,18.17218
-6.88933,33.91791 -20.66744,47.23723 -13.77846,13.31935 -32.86076,20.5469
-57.24699,21.68266 v 28.18746 h -19.57005 v -27.87771 c -24.87416,-2.37477
-43.95648,-9.21513 -57.247,-20.52109 -13.29059,-11.30593 -20.78939,-27.12909
-22.49641,-47.46954 l 32.92159,-4.95604 c 2.56052,15. [...]
- id="text2413-7"
- inkscape:connector-curvature="0" />
- </g>
- <path
- sodipodi:nodetypes="cc"
- id="path4370-1"
- d="M 485.73522,46.322425 V 329.03573"
-
style="fill:none;fill-rule:evenodd;stroke:#ffffff;stroke-width:32;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1"
- inkscape:connector-curvature="0" />
- </g>
- </g>
- </g>
- <g
- id="g56721"
- transform="matrix(0.11701702,0,0,0.11701702,162.95391,3.4222642)">
- <rect
- ry="68.597343"
- y="31.361891"
- x="39.933308"
- height="352.99051"
- width="327.27625"
- id="rect54956"
-
style="opacity:0.6;fill:#a7ffff;fill-opacity:1;stroke:#00ff00;stroke-width:0.868204;stroke-linejoin:round;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1"
/>
- <g
- transform="translate(-3.1150281e-6,-2.1686764)"
- id="g56705">
- <g
- transform="matrix(0.31078808,0,0,0.31078808,107.45869,61.820985)"
- id="g7071">
- <g
- id="g1327">
- <path
- inkscape:connector-curvature="0"
- id="path1329"
- style="fill:#111111;stroke:#eeeeee;stroke-width:3.6352"
- d="M 70.693333,1.8858667 C 26.602667,1.8858667 1.8176,24.6816
1.8176,71.2576 v 480.1312 c 0,43.56693 22.288,66.3776 66.338133,66.3776 H
550.31467 c 44.0608,0 66.3776,-21.66933 66.3776,-66.3776 V 71.2576 c
0,-45.441067 -22.3168,-69.3717333 -67.75574,-69.3717333 -0.004,0
-478.394663,-0.1525334 -478.243197,0 z" />
- </g>
- <path
- inkscape:connector-curvature="0"
- sodipodi:nodetypes="cccccccccccccc"
- id="path645"
- d="M 308.11126,42.898171 39.247865,247.59942 H 93.020191 V
575.98448 H 254.33859 V 441.27715 h 111.23247 l 3.7e-4,134.70733 H 523.20236 V
247.59942 h 53.77269 z"
-
style="font-size:12px;opacity:0.2;fill:#ffffff;fill-opacity:1;fill-rule:evenodd;stroke:#ffffff;stroke-width:1.32418;stroke-opacity:1"
/>
- <path
- inkscape:connector-curvature="0"
-
style="font-size:12px;opacity:1;fill:none;fill-opacity:1;fill-rule:evenodd;stroke:#ffffff;stroke-width:21.3333;stroke-linejoin:round;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1"
- d="M 308.11126,32.231504 39.247865,236.93276 H 93.020191 V
575.98448 H 254.33859 V 441.27715 h 111.23247 l 3.7e-4,134.70733 H 523.20236 V
236.93276 h 53.77269 z"
- id="path3198"
- sodipodi:nodetypes="cccccccccccccc" />
- <g
- transform="translate(-177.88465,62.418967)"
- id="g4998">
- <g
- id="g5004">
- <path
- inkscape:connector-curvature="0"
- id="text2413"
- d="m 496.42877,164.09649 c 0.24375,0.10338 1.15824,0.30988
2.74347,0.61951 24.99587,4.13015 43.77336,11.66746 56.3325,22.61192
12.55879,10.94468 18.83828,25.29652 18.83846,43.05557 -1.8e-4,18.17218
-6.88933,33.91791 -20.66744,47.23723 -13.77846,13.31935 -32.86076,20.5469
-57.24699,21.68266 v 28.18746 h -19.57005 v -27.87771 c -24.87416,-2.37477
-43.95648,-9.21513 -57.247,-20.52109 -13.29059,-11.30593 -20.78939,-27.12909
-22.49641,-47.46954 l 32.92159,-4.95604 c 2.56052,1 [...]
-
style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:323.145px;line-height:125%;font-family:'Arial
Unicode MS';-inkscape-font-specification:'Arial Unicode
MS';text-align:start;writing-mode:lr-tb;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;stroke-width:1.06667px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
/>
- </g>
- <path
- inkscape:connector-curvature="0"
-
style="fill:none;fill-rule:evenodd;stroke:#ffffff;stroke-width:32;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1"
- d="M 485.73522,46.322425 V 329.03573"
- id="path4370"
- sodipodi:nodetypes="cc" />
- </g>
- </g>
- <text
- xml:space="preserve"
-
style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:53.3333px;line-height:45px;font-family:'Bitstream
Charter';-inkscape-font-specification:'Bitstream
Charter';text-align:center;letter-spacing:0px;word-spacing:0px;text-anchor:middle;fill:#000000;fill-opacity:1;stroke:none;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
- x="203.87518"
- y="312.85718"
- id="text56442"><tspan
- sodipodi:role="line"
- id="tspan56440"
- x="203.87518"
- y="312.85718">Payee's</tspan><tspan
- sodipodi:role="line"
- x="203.87518"
- y="357.85718"
- id="tspan56444">Bank</tspan></text>
- </g>
- </g>
- <g
- id="g2992"
- transform="matrix(0.20260914,0,0,0.20260914,84.146501,64.608036)">
- <g
- id="logo">
- <g
- id="circles"
-
style="fill:#0042b3;fill-opacity:1;fill-rule:evenodd;stroke:none;stroke-width:0.327943">
- <path
- d="m 86.662153,1.1211936 c 15.589697,0 29.129227,9.4011664
35.961027,23.2018054 h -5.81736 C 110.4866,13.623304 99.349002,6.5180852
86.662153,6.5180852 c -19.690571,0 -35.652876,17.1120008 -35.652876,38.2205688
0,10.331797 3.825597,19.704678 10.03957,26.582945 -1.342357,1.120912
-2.771532,2.127905 -4.275488,3.006754 C 50.071485,66.553412 45.974857,56.15992
45.974857,44.738654 c 0,-24.089211 18.216325,-43.6174604 40.687296,-43.6174604
z M 122.51416,65.375898 c -6.86645,13.680 [...]
- id="path2350" />
- <path
- d="m 64.212372,1.1211936 c 1.052607,0 2.095998,0.042919
3.128684,0.1270583 C 64.288864,2.8094199 61.427378,4.728606 58.802653,6.9555572
41.679542,9.7498571 28.559494,25.601563 28.559494,44.738654 c 0,14.264563
7.29059,26.702023 18.093843,33.268925 -1.593656,0.26719 -3.226966,0.406948
-4.890748,0.406948 -1.239545,0 -2.46151,-0.07952 -3.663522,-0.229364 C
29.191129,70.184015 23.525076,58.171633 23.525076,44.738654 23.525076,20.649443
41.7414,1.1211936 64.212372,1.1211936 Z M 6 [...]
- id="path2352" />
- <path
- d="m 41.762589,1.1211936 c 1.064296,0 2.118804,0.044379
3.162607,0.1302161 -3.046523,1.558961 -5.903162,3.4745139 -8.52358,5.6968133 C
19.254624,9.7205882 6.1097128,25.583465 6.1097128,44.738654 c 0,21.108568
15.9624012,38.22057 35.6528762,38.22057 12.599746,0 23.672446,-7.007056
30.013748,-17.583802 h 5.838515 C 70.748498,79.055727 57.26924,88.356116
41.762589,88.356116 c -22.470907,0 -40.6871998,-19.52825 -40.6871998,-43.617462
0,-24.089211 18.2162928,-43.6174604 40.687199 [...]
- id="path2354" />
- </g>
- <g
- id="letters">
- <path
- d="m 76.135411,34.409066 h 9.161042 V 29.36588 H 61.857537 v
5.043186 h 9.161137 v 25.92317 h 5.116737 z"
- id="path2346" />
- <path
- d="m 92.647571,52.856334 h 13.659009 l 2.93009,7.476072 h 5.36461
L 101.89122,29.144903 H 97.187186 L 84.477089,60.332406 h 5.199533 z m
11.802109,-4.822276 h -9.944771 l 4.951718,-12.386462 z"
- id="path2362" />
- <path
- d="m 123.80641,29.366084 h -4.58038 v 30.966322 h 20.54728 v
-4.910253 c -5.32227,0 -10.64463,0 -15.9669,0 z"
- id="path2356" />
- <path
- d="m 166.4722,29.366084 h -21.37564 v 30.966322 h 21.58203 v
-4.910253 h -16.54771 v -8.27275 h 14.48439 V 42.23925 h -14.48439 v -7.962811
h 16.34132 z"
- id="path2360" />
- <path
- d="m 191.19035,39.474593 c 0,1.59947 -0.53646,2.87535
-1.61628,3.818883 -1.07281,0.95124 -2.52409,1.422837 -4.34678,1.422837 h
-7.44851 V 34.276439 h 7.4073 c 1.9051,0 3.38376,0.435027 4.42939,1.312178
1.05226,0.870258 1.57488,2.167734 1.57488,3.885976 z m 6.06602,20.857813
-7.79911,-11.723191 c 1.01771,-0.294794 1.94631,-0.714813 2.78553,-1.260566
0.83885,-0.545619 1.56122,-1.209263 2.16629,-1.990627 0.60541,-0.781738
1.07981,-1.681096 1.42369,-2.698345 0.34378,-1.017553 0. [...]
- id="path2358" />
- </g>
- </g>
- </g>
- <g
- id="g57752"
- transform="matrix(0.11701702,0,0,0.11701702,-7.5850827,-0.17502012)">
- <text
- id="text56498"
- y="227.10675"
- x="610.51172"
-
style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:32px;line-height:1000px;font-family:'Bitstream
Charter';-inkscape-font-specification:'Bitstream
Charter';text-align:center;letter-spacing:0px;word-spacing:0px;text-anchor:middle;fill:#000000;fill-opacity:1;stroke:none;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
- xml:space="preserve"><tspan
- y="227.10675"
- x="610.51172"
- id="tspan56496"
- sodipodi:role="line">2. wire transfer</tspan></text>
- <path
- inkscape:connector-curvature="0"
- id="path56924"
- d="M 457.09402,254.70537 H 759.63471"
-
style="fill:url(#radialGradient57499);fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:3.77953;stroke-linecap:round;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1;marker-end:url(#marker57204)"
/>
- </g>
- <text
- xml:space="preserve"
-
style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:3.74454px;line-height:117.017px;font-family:'Bitstream
Charter';-inkscape-font-specification:'Bitstream
Charter';text-align:center;letter-spacing:0px;word-spacing:0px;text-anchor:middle;fill:#000000;fill-opacity:1;stroke:none;stroke-width:0.117017px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
- x="145.74298"
- y="25.747398"
- id="text56502"><tspan
- style="stroke-width:0.117017px"
- sodipodi:role="line"
- id="tspan56500"
- x="145.74298"
- y="25.747398">7. wire transfer</tspan></text>
- <path
-
style="fill:url(#radialGradient57499-5);fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:0.442269;stroke-linecap:round;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1;marker-end:url(#marker57204-8)"
- d="m 127.80547,30.28278 h 35.40241"
- id="path56924-1"
- inkscape:connector-curvature="0" />
- <g
- id="g56781"
- transform="matrix(0.11701702,0,0,0.11701702,-18.664087,-4.0166692)">
- <rect
- ry="68.597343"
- y="94.933319"
- x="892.07617"
- height="352.99051"
- width="327.27625"
- id="rect54956-1"
-
style="opacity:0.6;fill:#a7ffff;fill-opacity:1;stroke:#00ff00;stroke-width:0.868204;stroke-linejoin:round;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1"
/>
- <g
- transform="translate(1.2553075,-1.0972245)"
- id="g56765">
- <text
- xml:space="preserve"
-
style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:53.3333px;line-height:45px;font-family:'Bitstream
Charter';-inkscape-font-specification:'Bitstream
Charter';text-align:center;letter-spacing:0px;word-spacing:0px;text-anchor:middle;fill:#000000;fill-opacity:1;stroke:none;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
- x="1054.6827"
- y="374.28571"
- id="text56436"><tspan
- sodipodi:role="line"
- id="tspan56434"
- x="1054.6827"
- y="374.28571">Exchange's</tspan><tspan
- sodipodi:role="line"
- x="1054.6827"
- y="419.28571"
- id="tspan56438">Bank</tspan></text>
- <g
- transform="matrix(0.31078808,0,0,0.31078808,958.34624,125.39241)"
- id="g7071-3">
- <g
- id="g1327-8">
- <path
- inkscape:connector-curvature="0"
- id="path1329-2"
- style="fill:#111111;stroke:#eeeeee;stroke-width:3.6352"
- d="M 70.693333,1.8858667 C 26.602667,1.8858667 1.8176,24.6816
1.8176,71.2576 v 480.1312 c 0,43.56693 22.288,66.3776 66.338133,66.3776 H
550.31467 c 44.0608,0 66.3776,-21.66933 66.3776,-66.3776 V 71.2576 c
0,-45.441067 -22.3168,-69.3717333 -67.75574,-69.3717333 -0.004,0
-478.394663,-0.1525334 -478.243197,0 z" />
- </g>
- <path
- inkscape:connector-curvature="0"
- sodipodi:nodetypes="cccccccccccccc"
- id="path645-5"
- d="M 308.11126,42.898171 39.247865,247.59942 H 93.020191 V
575.98448 H 254.33859 V 441.27715 h 111.23247 l 3.7e-4,134.70733 H 523.20236 V
247.59942 h 53.77269 z"
-
style="font-size:12px;opacity:0.2;fill:#ffffff;fill-opacity:1;fill-rule:evenodd;stroke:#ffffff;stroke-width:1.32418;stroke-opacity:1"
/>
- <path
- inkscape:connector-curvature="0"
-
style="font-size:12px;opacity:1;fill:none;fill-opacity:1;fill-rule:evenodd;stroke:#ffffff;stroke-width:21.3333;stroke-linejoin:round;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1"
- d="M 308.11126,32.231504 39.247865,236.93276 H 93.020191 V
575.98448 H 254.33859 V 441.27715 h 111.23247 l 3.7e-4,134.70733 H 523.20236 V
236.93276 h 53.77269 z"
- id="path3198-7"
- sodipodi:nodetypes="cccccccccccccc" />
- <g
- transform="translate(-177.88465,62.418967)"
- id="g4998-0">
- <g
- id="g5004-8">
- <path
- inkscape:connector-curvature="0"
- id="text2413-8"
- d="m 496.42877,164.09649 c 0.24375,0.10338 1.15824,0.30988
2.74347,0.61951 24.99587,4.13015 43.77336,11.66746 56.3325,22.61192
12.55879,10.94468 18.83828,25.29652 18.83846,43.05557 -1.8e-4,18.17218
-6.88933,33.91791 -20.66744,47.23723 -13.77846,13.31935 -32.86076,20.5469
-57.24699,21.68266 v 28.18746 h -19.57005 v -27.87771 c -24.87416,-2.37477
-43.95648,-9.21513 -57.247,-20.52109 -13.29059,-11.30593 -20.78939,-27.12909
-22.49641,-47.46954 l 32.92159,-4.95604 c 2.56052,1 [...]
-
style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:323.145px;line-height:125%;font-family:'Arial
Unicode MS';-inkscape-font-specification:'Arial Unicode
MS';text-align:start;writing-mode:lr-tb;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;stroke-width:1.06667px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
/>
- </g>
- <path
- inkscape:connector-curvature="0"
-
style="fill:none;fill-rule:evenodd;stroke:#ffffff;stroke-width:32;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1"
- d="M 485.73522,46.322425 V 329.03573"
- id="path4370-4"
- sodipodi:nodetypes="cc" />
- </g>
- </g>
- </g>
- </g>
- <path
-
style="fill:none;fill-rule:evenodd;stroke:#000000;stroke-width:0.117017px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;marker-start:url(#marker11960);marker-end:url(#marker12042)"
- d="M 104.87245,50.170485 V 63.042357"
- id="path11950"
- inkscape:connector-curvature="0" />
- <image
- id="image16008"
-
xlink:href="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAABEwAAAFoEAYAAAAdlLJ+AAAMYmlDQ1BJQ0MgUHJvZmlsZQAASImV
VwdYU8kWnltSSWiBUKSE3kTpBJASQosgIFUQlZAEEkqMCUHFzrqsgmsXUSwruiqi6FoAWQsidhfF
3hcLKsq6WLCh8iYksK77yvfO982dP2fO/Kdk5t4ZAHQ6+DJZPqoLQIG0UJ4QGcoal5bOIj0CGDAF
WsAd6PAFChknPj4GQBns/y5vrwFE1V92VXH9c/y/ir5QpBAAgGRAnCVUCAogbgYALxHI5IUAEMOg
3mZqoUyFxRAbyGGAEM9U4Rw1XqrCWWq8ZcAmKYELcSMAZBqfL88BQLsV6llFghzIo/0IYjepUCIF
QMcA4iCBmC+EOAni4QUFk1V4LsSO0F4G8XaI2Vlfceb8jT9riJ/PzxnC6rwGhBwmUc [...]
- preserveAspectRatio="none"
- height="65.842171"
- width="201.18443"
- x="5.6494861"
- y="91.440536" />
- <text
- xml:space="preserve"
-
style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:3.74454px;line-height:117.017px;font-family:'Bitstream
Charter';-inkscape-font-specification:'Bitstream
Charter';text-align:center;letter-spacing:0px;word-spacing:0px;text-anchor:middle;fill:#000000;fill-opacity:1;stroke:none;stroke-width:0.117017px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
- x="182.27733"
- y="-5.0046802"
- id="text56522"
- transform="rotate(32.475037)"><tspan
- style="stroke-width:0.117017px"
- sodipodi:role="line"
- id="tspan56520"
- x="182.27733"
- y="-5.0046802">6. deposit coins (optional)</tspan></text>
- <path
- sodipodi:nodetypes="cc"
-
style="fill:none;fill-rule:evenodd;stroke:#000000;stroke-width:0.117017px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;marker-start:url(#Arrow1Lstart-9);marker-end:url(#marker11275-3)"
- d="m 126.90052,77.884296 53.17311,33.588754"
- id="path10953-1"
- inkscape:connector-curvature="0" />
- <path
- sodipodi:nodetypes="cc"
-
style="fill:none;fill-rule:evenodd;stroke:#000000;stroke-width:0.117017px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;marker-start:url(#Arrow1Lstart);marker-end:url(#marker11275)"
- d="M 79.154946,82.266582 34.224376,114.37703"
- id="path10953"
- inkscape:connector-curvature="0" />
- <text
- xml:space="preserve"
-
style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:3.74454px;line-height:117.017px;font-family:'Bitstream
Charter';-inkscape-font-specification:'Bitstream
Charter';text-align:center;letter-spacing:0px;word-spacing:0px;text-anchor:middle;fill:#000000;fill-opacity:1;stroke:none;stroke-width:0.117017px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
- x="-9.5554037"
- y="111.14681"
- id="text56514"
- transform="rotate(-34.51916)"><tspan
- style="stroke-width:0.117017px"
- sodipodi:role="line"
- id="tspan56512"
- x="-9.5554037"
- y="111.14681">3. withdraw coins</tspan></text>
- <text
- xml:space="preserve"
-
style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:3.74454px;line-height:117.017px;font-family:'Bitstream
Charter';-inkscape-font-specification:'Bitstream
Charter';text-align:center;letter-spacing:0px;word-spacing:0px;text-anchor:middle;fill:#000000;fill-opacity:1;stroke:none;stroke-width:0.117017px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
- x="81.049461"
- y="-185.26154"
- id="text56530"
- transform="rotate(90)"><tspan
- style="stroke-width:0.117017px"
- sodipodi:role="line"
- id="tspan56528"
- x="81.049461"
- y="-185.26154">8. view balance</tspan></text>
- <path
- sodipodi:nodetypes="cc"
-
style="fill:none;fill-rule:evenodd;stroke:#000000;stroke-width:0.117017px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;marker-end:url(#marker10915)"
- d="M 184.08348,52.656855 V 109.29393"
- id="path10905"
- inkscape:connector-curvature="0" />
- <text
- xml:space="preserve"
-
style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:3.74454px;line-height:117.017px;font-family:'Bitstream
Charter';-inkscape-font-specification:'Bitstream
Charter';text-align:center;letter-spacing:0px;word-spacing:0px;text-anchor:middle;fill:#000000;fill-opacity:1;stroke:none;stroke-width:0.117017px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
- x="-83.72728"
- y="20.072399"
- id="text56506"
- transform="rotate(-90)"><tspan
- style="stroke-width:0.117017px"
- sodipodi:role="line"
- x="-83.72728"
- y="20.072399"
- id="tspan56508">1. pay exchange</tspan></text>
- <path
- sodipodi:nodetypes="cc"
-
style="fill:none;fill-rule:evenodd;stroke:#000000;stroke-width:0.117017px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;marker-end:url(#Arrow1Lend)"
- d="m 22.969674,119.30382 0,-68.211062"
- id="path10891"
- inkscape:connector-curvature="0" />
- <g
- id="g15117"
- transform="matrix(0.11701702,0,0,0.11701702,-9.5830799,49.844767)">
- <text
- id="text56518"
- y="998.57141"
- x="961.8233"
-
style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:32px;line-height:1000px;font-family:'Bitstream
Charter';-inkscape-font-specification:'Bitstream
Charter';text-align:center;letter-spacing:0px;word-spacing:0px;text-anchor:middle;fill:#000000;fill-opacity:1;stroke:none;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
- xml:space="preserve"><tspan
- y="998.57141"
- x="961.8233"
- id="tspan56516"
- sodipodi:role="line">4. offer payment</tspan></text>
- <path
- inkscape:connector-curvature="0"
- id="path12122"
- d="M 466.33664,948.57143 H 1454.908"
-
style="fill:none;fill-rule:evenodd;stroke:#000000;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;marker-end:url(#marker12132)"
/>
- </g>
- <text
- transform="rotate(32.475037)"
- id="text56522-9"
- y="1.1439257"
- x="180.8817"
-
style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:3.74454px;line-height:117.017px;font-family:'Bitstream
Charter';-inkscape-font-specification:'Bitstream
Charter';text-align:center;letter-spacing:0px;word-spacing:0px;text-anchor:middle;fill:#000000;fill-opacity:1;stroke:none;stroke-width:0.117017px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
- xml:space="preserve"><tspan
- y="1.1439257"
- x="180.8817"
- id="tspan56520-9"
- sodipodi:role="line"
- style="stroke-width:0.117017px">5. Identify to receive
payment</tspan></text>
- <g
- transform="matrix(0.04430172,0,0,0.04430172,175.03069,142.7867)"
- id="g18960">
- <path
- fill="#03aa4b"
- d="m 16.244,48.699 c 0,-8.535 -0.388,-13.19 -1.164,-31.811 h 36.854 l
0.776,32.199 c 18.233,-30.647 50.432,-35.302 66.337,-35.302 41.897,0
81.855,28.708 81.855,100.865 0,72.544 -42.285,104.355 -88.838,104.355 -28.319,0
-49.269,-12.026 -59.743,-29.096 v 96.597 H 16.244 Z m 89.614,143.538 c 9.311,0
28.708,-1.94 41.122,-19.01 13.966,-19.009 15.906,-46.94 15.906,-60.906
0,-34.915 -10.475,-71.381 -53.536,-71.381 -58.19,0 -58.19,61.683 -58.19,79.14
-10e-4,23.664 3.49,72.157 54.698,72.157 z"
- id="path18954" />
- <path
- fill="#03aa4b"
- d="m 239.708,94.082 h 206.138 v 26.836 H 239.708 Z m 0.084,-77.23 H
445.928 V 43.686 H 239.792 Z m 0,154.648 h 206.136 v 26.834 H 239.792 Z"
- id="path18956" />
- <path
- fill="#03aa4b"
- d="m 497.676,48.699 c 0,-8.535 -0.389,-13.19 -1.164,-31.811 h 36.854
l 0.777,32.199 c 18.232,-30.647 50.432,-35.302 66.338,-35.302 41.896,0
81.854,28.708 81.854,100.865 0,72.544 -42.285,104.355 -88.838,104.355 -28.318,0
-49.268,-12.026 -59.742,-29.096 v 96.597 H 497.677 V 48.699 Z m 89.613,143.538
c 9.311,0 28.709,-1.94 41.123,-19.01 13.965,-19.009 15.904,-46.94
15.904,-60.906 0,-34.915 -10.475,-71.381 -53.535,-71.381 -58.191,0
-58.191,61.683 -58.191,79.14 0,23.664 3.492,72.157 [...]
- id="path18958" />
- </g>
- </g>
-</svg>
diff --git a/prototype-2018/application.txt b/prototype-2018/application.txt
deleted file mode 100644
index b3b74bd..0000000
--- a/prototype-2018/application.txt
+++ /dev/null
@@ -1,138 +0,0 @@
------------------------------
-GitHub/BitBucket Accounts:
-
-=>
-
-https://git.taler.net/,
-https://git.gnunet.org/
-
------------------------------
-An welchen Open-Source-Projekten hast Du/habt Ihr bisher gearbeitet?
-
-=> GNUnet, GNU Taler
-
------------------------------
-Bewerbt Ihr Euch als Team um die Förderung?*
-
-=> nein
-
------------------------------
-Projekttitel
-
-=> Vorschläge:
-
-1. Bargeldloses Zahlen ohne Überwachung
-2. Infrastruktur für bargeldlose Zahlungen
- mit Privatsphäre-Schutz von Kund*innen
-
-(statt Bargeldloses Zahlen => NFC-Zahlungen?)
-
-=> Infrastruktur für bargeldlose Zahlungen ohne Überwachung
-
------------------------------
-Ordne das Projekt einem Bereich zu.
- Civic Tech
- Datensicherheit
- Data Literacy
- Infrastruktur
-(genau eine Option auswählbar)
-
-=>
-
-Datensicherheit oder Infrastruktur?
-
-FD: ich tendiere zu Infrastruktur
-
------------------------------
-Bezieht sich Dein Projekt auf den Themenschwerpunkt der 5. Runde?
-(Maschinen lernen lassen – Technologien für die Zukunft.)
-
-=> Nein
-
------------------------------
-Beschreibe Dein Projekt kurz.
-Max. 700 Zeichen
-
-GNU Taler ist ein freies Online-Bezahlsystem welches die Privatspäre von
Kund*innen schützt und gleichzeitig das Einkommen von Händler*innen gegenüber
Buchprüfer*innen offenlegt. Damit werden illegale Aktivitäten wie
Steuerhinterziehung oder der Handel mit illegalen Waren erschwert. Die
bisherige Implementation von GNU Taler ist jedoch stark auf das Bezahlen von
Online-Inhalten im Browser fokussiert.
-
-Ziel dieses Projekts ist, GNU Taler mit NFC-Zahlungen auf Hardware-Platformen
(primär Smartphones) zu erweitern, um somit auch bequeme bargeldlose Zahlungen
in Präsenzsituationen zu ermöglichen. Dies umfasst Szenarien, in denen nur
eine der beiden Parteien Internetzugang hat.
-
-
-
------------------------------
-Welches gesellschaftliche Problem willst Du mit Deinem Projekt lösen?*
-Max. 700 Zeichen
-
-=>
-
-Durch technischen Fortschritt verdrängen bargeldlose Zahlungssysteme immer
mehr die Benutzung von Bargeld im Alltag vieler Bürger*innen. Während die
Bequemlichkeit dieser Zahlungsmöglichkeiten wilkommen ist, werden die Nachteile
oft übersehen: Die derzeitige Umsetzung ermöglicht die Totalüberwachung der
ökonomische Aktivität der Benutzer*innen.
-
-Properitäre Lösungen wie Apple Pay und Google Pay basieren auf geschlossenen
Implementationen/Schnittstellen und werden von mächtigen US-Amerikanischen
Oligopolen kontrolliert. Diese erlangen so Zugriff auf die Aktivitätsprofile
von Benutzer*innen, welche dann für Werbezwecke ausgewertet und/oder verkauft
werden.
-
------------------------------
-Wie willst Du Dein Projekt technisch umsetzen?*
-Max. 1300 Zeichen
-
-Basis des Projekts bildet die existierende Implementation von GNU Taler,
bestehend aus folgenden Komponenten (vereinfacht):
-
-1. Die Exchange, der Zahldienstleister welcher Geld von einem Bankkonto (oder
anderen Werteregistern) in anonymes digitales Bargeld umwandelt. Die
Anonymität der Kund*innen beim Kauf wird mit der Benutzung von blinden
Signaturen zum Abheben des digitalen Bargeldes gewährleistet.
-
-2. Das Händler*innen-Backend, welches ein einfaches API zur Integration zur
Abwicklung von Zahlungen mit GNU Taler in dem Online-Shop der Händler*innen
bietet.
-
-3. Die digitale Geldbörse (Wallet) der Kund*innen, welche digitales Bargeld
verwaltet und Zahlungen abwickelt.
-
-Um NFC-Zahlungen zu ermöglichen, muss eine Bezahlterminal-App für
Händler*innen entwickelt werden, welche sowohl mit dem Wallet als auch dem
Backend kommuniziert. Das Wallet muss auf Smartphones portiert werden und das
NFC Protokoll implementieren. Falls das Smartphone der Nutzer*in keinen
Internetzugang hat, muss das Wallet über die Händler*in mit der Exchange
kommunizieren.
-
-Um den Anforderungen von NFC-Payments gerecht zu werden, müssen kleinere
Änderungen an den existierenen Protokollen implementiert werden, so wie
eventuell existierende Fehler vorhandenen Implemetation behoben werden.
-
-
------------------------------
-Welche ähnlichen Lösungen gibt es schon, und was wird Dein Projekt anders bzw.
besser machen?*
-Max. 400 Zeichen
-
-=>
-
-Nur wenige Zahlsysteme legen Wert auf Datenminimierung und Privatsphäre für
Kund*innen. Spezielle cryptocurrencies (wie z.B. ZCash) bieten komplette
Anonymität, was zum Missbrauch für illegale Aktivitäten einlädt. Zudem sind
solche Blockchain-basierten cryptocurrencies nicht performant genug für
alltägliche Transaktionen.
-
-Uns sind keine benutzbaren Zahlsysteme als Freie Software bekannt.
-
------------------------------
-Wer ist die Zielgruppe, und wie soll Dein Tool sie erreichen?*
-Max. 700 Zeichen
-
-Das Projekt richtet sich an Institutionen und Organisationen die ihren
Mitgliedern oder Kund*innen ein bargeldloses Zahlungsmittel anbieten wollen,
ohne dabei die Privatsphäre der Käufer*innen zu verletzen.
-
-Im Kleinen könnte das Mensa/Cafeteria einer Schule, Universität oder Firma
sein. In einem Größeren Umfang können Finanzdienstleister (wie z.B. Banken)
Händler*innen und Kund*innen untereinander Zahlungen abwickeln lassen und von
Transaktionsgebühren profitieren.
-
-Kunden und Händler profitieren dabei von der Austauschbarkeit des
Zahlungsdienstleisters und Wettbewerb unter den Dienstleistern, da das
Bezahlsystem auf einem offenen Protokoll mit offener Implementation basiert.
-
------------------------------
-Hast Du schon an der Idee gearbeitet? Wenn ja, beschreibe kurz den aktuellen
Stand und erkläre die Neuerung.*
-Max. 700 Zeichen
-
-Bisher habe ich als einer der Hauptentwickler an dem GNU Taler Projekt
gearbeitet, und die Kryptographie im Rahmen meiner (derzeit noch laufenden)
Dissertation weiterentwickelt und formell betrachtet.
-
-Die Idee der NFC-Zahlungen ist neu, und eine App für die Android-Platform
besteht noch nicht. Der bisherige Fokus des GNU Taler Projekts war die
Integration in Desktop-Browsern (Chrome/Firefox) und die Entwicklung der
Kryptographie und Backend-Infrastruktur.
-
------------------------------
-Wie viele Stunden willst Du (bzw. will das Team) in den 6 Monaten
Förderzeitraum an der Umsetzung arbeiten?*
-Bitte eine Zahl eintragen.
-
-=>
-
-(15 Arbeitstage / Monat, halbzeit)
-15 * 6 * 4 = 360
-
-(Is this enough? Since the project is a bit ambitious ...)
-
------------------------------
-Skizziere kurz die wichtigsten Meilensteine, die Du (bzw. das Team) im
Förderzeitraum umsetzen willst.*
-Max. 700 Zeichen
-
-Meilenstein 1: Spezifikation des NFC-Protokolls zwischen Käufer*innen und
Bezahlterminal der Händler*innen.
-
-Meilenstein 2: Implementation einer Bezahlterminal-App für die
Android-Platform, welche das in (1) spezifizierte NFC-Protokoll unterstützt und
mit dem existierenden GNU Taler Backend der Händler*innen kommuniziert.
-
-Meilenstein 3: Portierung des existierenden GNU Taler Wallets (= digitale
Geldbörse) auf die Android-Platform.
-
-Meilenstein 4: Implementation des NFC-Protokolls und der dazugehörigen
Benutzeroberfläche in der GNU Taler Wallet auf Android.
--
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.
- [taler-marketing] branch master updated: cleanup,
gnunet <=