aboutsummaryrefslogtreecommitdiff
path: root/src/exchangedb/test_exchangedb.c
AgeCommit message (Collapse)Author
2022-02-04added CS data structures, implemented CS keypairGian Demarmels
2022-01-21[age restriction] progress 12/nÖzgür Kesim
- taler-offline-tool now handles extensions - command "extensions" added with subcommands "show" and "sign" - parses extensions from taler config - shows and signs of extensions and their configurations - creates signed set of configurations for upload - added test for retrieval of extension config - simplified signature verification for extensions - remove per-extension signatures, also from DB schema - adjust prepared statements accordingly - adjust DB event handler for extensions - allow NULL for config for extension in DB schema - handler for /management/extensions adjusted to new datastructures - changed test for TALER_denom_blind/TALER_denom_sign_blinded with and without TALER_AgeHash - minor updates and various fixes
2022-01-11The current recoup API is broken. I guess this is another example where ↵Christian Grothoff
"trivial" API changes turn out to have (multiple!) unexpected consequences. The current "/recoup" API does not have clear idempotency semantics, as we've discussed on the phone. This is already bad by itself, as it makes it hard to write down what the API does other than "whatever the implementation does". However, it actually breaks correctness in this (admittedly kinda contrived, but not impossible) case: Say that we have a coin A obtained via withdrawal and a coin B obtained via refreshing coin A. Now the denominations of A gets revoked.. The wallet does a recoup of A for EUR:1. Now the denomination of B also gets revoked. The wallet recoups B (incidentally also for EUR:1) and now A can be recouped again for EUR:1. But now the exchange is in a state where it will refuse a legitimate recoup request for A because the detection for an idempotent request kicks in. This is IMHO bad API design, and the exchange should simply always recoup the maximum amount. Furthermore, we usually follow the principle of "API calls that take up DB space are paid". With the current recoup API, I can do many tiny recoup requests which the exchange then has to store, right? I guess it would not be a big change to remove the "amount" value from the recoup/recoup-refresh request bodies, right? - Florian
2021-12-25-fix FTBFSChristian Grothoff
2021-12-25protocol v12 changes (/recoup split, signature changes) plus database ↵Christian Grothoff
sharding plus O(n^2)=>O(n) worst-case complexity reduction on coin balance checks
2021-12-19denormalize reserve_pub in reserve tables to enable shardingChristian Grothoff
2021-12-16-fix recoup uglinessChristian Grothoff
2021-12-15-fix FTBFSChristian Grothoff
2021-12-05change order of statements when making coin known to possibly reduce ↵Christian Grothoff
serialization failures
2021-12-05major rework of withdraw transaction to use stored procedure and ↵Christian Grothoff
(presumably) reduce serialization failures by avoiding SELECT before INSERT
2021-11-27sql fixChristian Grothoff
2021-11-20fix typo: s/row_id/rowid/Thien-Thi Nguyen
2021-11-19-fix leaks and compiler warningsChristian Grothoff
2021-11-16[age restriction] progress 3/nÖzgür Kesim
- remove redundant struct members for age commitment hash - undo pre-mature implementation in taler-exchange-secmod-rsa.c - carry through age restriction parameter for TALER_denom_blind
2021-11-07add missing fileChristian Grothoff
2021-11-06more RSA cleanupChristian Grothoff
2021-11-06RSA-despecializationChristian Grothoff
2021-11-05-fixesChristian Grothoff
2021-11-05abstract denomination keys a bit moreChristian Grothoff
2021-11-01fix shardingChristian Grothoff
2021-10-31consistently distinguish blinded/unblinded denomination sigsChristian Grothoff
2021-10-31DB test passes againChristian Grothoff
2021-10-31fixing SQL statementsChristian Grothoff
2021-10-31misc fixesChristian Grothoff
2021-10-31fix test FTBFSChristian Grothoff
2021-10-30-more dB workChristian Grothoff
2021-10-27fix FTBFS of exchangedbChristian Grothoff
2021-10-27-more changes towards fixing FTBFSChristian Grothoff
2021-10-17implement returning KYC status from GET /deposits/ endpointChristian Grothoff
2021-10-14start with KYC support in DBChristian Grothoff
2021-10-13-modify C API to future-proof it for returning more details as required for ↵Christian Grothoff
KYC implementation
2021-09-05implement taler-exchange-transfer DB sharding logicChristian Grothoff
2021-09-03preliminary work on supporting sharding/parallel aggregation (undertested, ↵Christian Grothoff
but tests pass again)
2021-08-23complete implementation of long-polling for reserve status; remove support ↵Christian Grothoff
for multi-threaded exchange httpd
2021-08-08-fix testChristian Grothoff
2021-08-08-sepa is ancient, iban is correctChristian Grothoff
2021-07-31-more json_pack fixesChristian Grothoff
2021-07-23-rename TALER_amount_get_zero to TALER_amount_set_zeroChristian Grothoff
2020-07-22fix misc typosChristian Grothoff
2020-07-08synchronize with latest GANAChristian Grothoff
2020-07-08simplify DB access: do not fetch fields we do not needChristian Grothoff
2020-07-05GNUNET_free_non_null is gone, use GNUNET_freeChristian Grothoff
2020-07-05towards changing timestamp in deposit confirmation (tests failing)Christian Grothoff
2020-04-08fix #6170 and rest of #6164Christian Grothoff
2020-03-31typosCodeBlau-NGI-2019Christian Grothoff
2020-03-27avoid warningChristian Grothoff
2020-03-27fix inconsistency in field namingChristian Grothoff
2020-03-26fix recoup-refresh audit logicChristian Grothoff
2020-03-14expand DB test to cover #6124 better (passed immediately, does not explain ↵Christian Grothoff
the failure)
2020-03-05new coins => fresh coins, also move comments into the database itselfChristian Grothoff
generated by cgit v1.2.3 (git 2.26.2) at 2024-10-16 09:00:43 +0000