Dev branch for age restriction, deposit policies, Brandt-Vickrey auctions etc.
e5d3c21043
+ adding a new 'input' field to get the base URL of the receiving-money mint + adapting 'detail' object passed to the wallet to indicate all the DOM ids from the SEPA form needed by the wallet to perform the submission |
||
---|---|---|
contrib | ||
doc | ||
m4 | ||
src | ||
website | ||
.gitignore | ||
.gitmodules | ||
AUTHORS | ||
bootstrap | ||
ChangeLog | ||
configure.ac | ||
COPYING | ||
INSTALL | ||
Makefile.am | ||
NEWS | ||
README |
Welcome to GNU Taler What is Taler? ============== Taler is an electronic payment system providing the ability to pay anonymously using digital cash. Taler consists of a network protocol definition (using a RESTful API over HTTP), a Mint (which creates digital coins), a Wallet (which allows customers to manage, store and spend digital coins), and a Merchant website which allows customers to spend their digital coins. Naturally, each Merchant is different, but Taler includes code examples to help Merchants integrate Taler as a payment system. Taler is currently developed by a worldwide group of independent free software developers and the DECENTRALISE team at Inria Rennes. Taler is free software and a GNU package (http://www.gnu.org/). This is not even a release yet, but some raw development prototype that does not work yet. This package also only includes the Taler mint, not the other components of the system. Documentation about Taler can be found at http://taler.net/. Dependencies: ============= These are the direct dependencies for running a Taler mint: - GNUnet >= 0.10.2 - GNU libmicrohttpd >= 0.9.38 - Postgres >= 9.3 Project structure is currently as follows: src/include/ -- installed headers for public APIs src/util/ -- common utility functions (currency representation, Taler-specific cryptography, Taler-specific json support) src/pq/ -- Postgres-specific utility functions src/mintdb/ -- Mint database backend (with DB-specific plugins) src/mint/ -- taler mint server src/mint-tools/ -- taler mint helper programs src/mint-lib/ -- libtalermint: C API to issue HTTP requests to mint Getting Started ============== The following steps illustrate how to set up a mint HTTP server. They take as a stub for configuring the mint the content of 'contrib/mint-template/config/'. 1) Create a 'test/' directory and copy the stubs in it: mkdir -p test/config/ cp mint/contrib/mint-template/config/* test/config/ cd test/ 2) Create the mint's master with the tool 'gnunet-ecc': gnunet-ecc -g1 master.priv 3) Edit config/mint-common.conf by replacing the right value on the line with the MASTER_PUBLIC_KEY entry with the fresh generated (ASCII version of) master.priv. This ASCII version is obtained by issuing: gnunet-ecc -p master.priv 4) Generate other mint related keys ('denomination' and 'signing' keys), by issuing: taler-mint-keyup -d `pwd` -m master.priv 5) Check with: taler-mint-keycheck -d `pwd` 6) A mint needs a database to operate, so the following instructions relate to how to set up PostgreSQL. On debian, the two packages needed are: * postgresql * postgresql-client For other operating systems, please refer to the relevant documentation. In this settlement, the mint wll use a database called 'talercheck' and will run under the username through which 'taler-mint-httpd' is launched. Thus assuming that this user is 'demo', we need to create a 'demo' role for postgresql and make him the owner of 'talercheck' database. To perform these administrative tasks we have to impersonate the 'postgres' (by default, postgres installation assigns privileges to such a user) user, then connect to the running DBMS. Issue the following: su # give your root password su - postgres psql # this is the command-line client to the DMBS # the following lines are SQL CREATE USER demo; CREATE DATABASE talercheck OWNER demo; # quit with CTRL-D 7) If any previous step has been successful, it is now possbile to start up the mint web server (by default it will listen on port 4241); issue: taler-mint-httpd -d `pwd` # assuming we did not move outside of the 'test' directory