Age | Commit message (Collapse) | Author | |
---|---|---|---|
2022-02-07 | fix DB API for generic blinded planchet storage | Christian Grothoff | |
2022-02-07 | get DB test to build | Christian Grothoff | |
2022-02-07 | -rename fest | Christian Grothoff | |
2022-02-04 | uncrustify | Gian Demarmels | |
2022-02-04 | exchangedb fix | Gian Demarmels | |
2022-02-04 | resolves merge conflicts | Gian Demarmels | |
2022-02-04 | refactor TALER_coin_ev_hash | Gian Demarmels | |
2022-02-04 | include denom_pub into coin_ev_hash | Gian Demarmels | |
2022-02-04 | implement feedback | Lucien Heuzeveldt | |
2022-02-04 | refactoring | Gian Demarmels | |
2022-02-04 | removed varargs | Gian Demarmels | |
2022-02-04 | added CS data structures, implemented CS keypair | Gian 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-11 | The 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 FTBFS | Christian Grothoff | |
2021-12-25 | protocol 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-19 | denormalize reserve_pub in reserve tables to enable sharding | Christian Grothoff | |
2021-12-16 | -fix recoup ugliness | Christian Grothoff | |
2021-12-15 | -fix FTBFS | Christian Grothoff | |
2021-12-05 | change order of statements when making coin known to possibly reduce ↵ | Christian Grothoff | |
serialization failures | |||
2021-12-05 | major rework of withdraw transaction to use stored procedure and ↵ | Christian Grothoff | |
(presumably) reduce serialization failures by avoiding SELECT before INSERT | |||
2021-11-27 | sql fix | Christian Grothoff | |
2021-11-20 | fix typo: s/row_id/rowid/ | Thien-Thi Nguyen | |
2021-11-19 | -fix leaks and compiler warnings | Christian 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-07 | add missing file | Christian Grothoff | |
2021-11-06 | more RSA cleanup | Christian Grothoff | |
2021-11-06 | RSA-despecialization | Christian Grothoff | |
2021-11-05 | -fixes | Christian Grothoff | |
2021-11-05 | abstract denomination keys a bit more | Christian Grothoff | |
2021-11-01 | fix sharding | Christian Grothoff | |
2021-10-31 | consistently distinguish blinded/unblinded denomination sigs | Christian Grothoff | |
2021-10-31 | DB test passes again | Christian Grothoff | |
2021-10-31 | fixing SQL statements | Christian Grothoff | |
2021-10-31 | misc fixes | Christian Grothoff | |
2021-10-31 | fix test FTBFS | Christian Grothoff | |
2021-10-30 | -more dB work | Christian Grothoff | |
2021-10-27 | fix FTBFS of exchangedb | Christian Grothoff | |
2021-10-27 | -more changes towards fixing FTBFS | Christian Grothoff | |
2021-10-17 | implement returning KYC status from GET /deposits/ endpoint | Christian Grothoff | |
2021-10-14 | start with KYC support in DB | Christian Grothoff | |
2021-10-13 | -modify C API to future-proof it for returning more details as required for ↵ | Christian Grothoff | |
KYC implementation | |||
2021-09-05 | implement taler-exchange-transfer DB sharding logic | Christian Grothoff | |
2021-09-03 | preliminary work on supporting sharding/parallel aggregation (undertested, ↵ | Christian Grothoff | |
but tests pass again) | |||
2021-08-23 | complete implementation of long-polling for reserve status; remove support ↵ | Christian Grothoff | |
for multi-threaded exchange httpd | |||
2021-08-08 | -fix test | Christian Grothoff | |
2021-08-08 | -sepa is ancient, iban is correct | Christian Grothoff | |
2021-07-31 | -more json_pack fixes | Christian Grothoff | |
2021-07-23 | -rename TALER_amount_get_zero to TALER_amount_set_zero | Christian Grothoff | |
2020-07-22 | fix misc typos | Christian Grothoff | |