2016-04-10 17:10:20 +02:00
|
|
|
# This file is in the public domain.
|
|
|
|
#
|
|
|
|
# Database-backend independent specification for the exchangedb module.
|
|
|
|
#
|
|
|
|
[exchangedb]
|
|
|
|
# Where do we expect to find information about auditors?
|
|
|
|
AUDITOR_BASE_DIR = ${TALER_DATA_HOME}/auditors/
|
2017-03-03 19:23:34 +01:00
|
|
|
|
|
|
|
# Where do we expect to find information about wire transfer fees
|
|
|
|
# for aggregate payments? These are the amounts we charge (subtract)
|
|
|
|
# the merchant per wire transfer. The directory is expected to
|
|
|
|
# contain files "$METHOD.fee" with the cost structure, where
|
|
|
|
# $METHOD corresponds to a wire transfer method.
|
2017-03-04 16:49:33 +01:00
|
|
|
WIREFEE_BASE_DIR = ${TALER_DATA_HOME}/exchange/wirefees/
|
2017-04-20 21:38:02 +02:00
|
|
|
|
|
|
|
|
|
|
|
# After how long do we close idle reserves? The exchange
|
|
|
|
# and the auditor must agree on this value. We currently
|
|
|
|
# expect it to be globally defined for the whole system,
|
|
|
|
# as there is no way for wallets to query this value. Thus,
|
|
|
|
# it is only configurable for testing, and should be treated
|
|
|
|
# as constant in production.
|
|
|
|
IDLE_RESERVE_EXPIRATION_TIME = 4 weeks
|
2019-07-24 12:19:36 +02:00
|
|
|
|
|
|
|
|
|
|
|
# After how long do we forget about reserves? Should be above
|
|
|
|
# the legal expiration timeframe of withdrawn coins.
|
|
|
|
LEGAL_RESERVE_EXPIRATION_TIME = 7 years
|
2022-03-26 09:00:19 +01:00
|
|
|
|
|
|
|
# What is the desired delay between a transaction being ready and the
|
|
|
|
# aggregator triggering on it?
|
|
|
|
AGGREGATOR_SHIFT = 1 s
|
2022-10-09 23:23:14 +02:00
|
|
|
|
|
|
|
# How many concurrent purses may be opened by a reserve
|
|
|
|
# if the reserve is paid for a year?
|
|
|
|
DEFAULT_PURSE_LIMIT = 1
|