summaryrefslogtreecommitdiff
path: root/src/auditor/taler-helper-auditor-reserves.c
AgeCommit message (Collapse)Author
2022-03-31privatize more signature structs, simplify codeChristian Grothoff
2022-03-05refactor /wire to include logic to return the wad fee (for W2W payments)Christian Grothoff
2022-02-21-big renaming of structs for consistent naming with P suffixChristian Grothoff
2022-02-17-fix CS nonce reuse check logicChristian Grothoff
2022-02-12-address misc. fixmesChristian Grothoff
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-16-fix recoup uglinessChristian Grothoff
2021-12-14introducing GNUNET_TIME_Timestamp, recoup now with amountsChristian Grothoff
2021-11-05-fixesChristian Grothoff
2021-10-27fix auditor FTBFSChristian Grothoff
2021-10-14-basic logic for withdraw KYC checksChristian Grothoff
2021-08-23-remove sessions also from auditorChristian Grothoff
2021-08-23complete implementation of long-polling for reserve status; remove support ↵Christian Grothoff
for multi-threaded exchange httpd
2021-07-31-more json_pack fixesChristian Grothoff
2021-07-31-more json_pack cleaningChristian Grothoff
2021-07-23-rename TALER_amount_get_zero to TALER_amount_set_zeroChristian Grothoff
2021-01-07make reserve balance check used in internal_auditor mode onlyChristian Grothoff
2021-01-07fix remaining #6679 issues in exchangeChristian Grothoff
2021-01-06add -i option to taler-auditorChristian Grothoff
2020-12-04centralize (most) offline signing/verifying operations into offline_signatures.cChristian Grothoff
2020-08-28improve reporting, also use auditor fee calculation when computing reserve ↵Christian Grothoff
balance updates in case of disagreement on coin value/fee
2020-07-15fix #6133: enable nice shutdown of auditor helpers with CTRL-CChristian Grothoff
2020-07-05GNUNET_free_non_null is gone, use GNUNET_freeChristian Grothoff
2020-07-05fix status codeChristian Grothoff
2020-04-08fix #6170 and rest of #6164Christian Grothoff
2020-04-08rename a_balance (#6170)Christian Grothoff
2020-04-08adapt to new GNUnet sign API (#6164)Christian Grothoff
2020-03-28address FIXMEChristian Grothoff
2020-03-24more testing for auditor logicChristian Grothoff
2020-03-22first pass at auditor-coins, also reviewing checks around amount arithmetic, ↵Christian Grothoff
can and should be made harsher
2020-03-22clean up auditor-reserves logicChristian Grothoff
2020-03-21stylefixesChristian Grothoff
2020-03-21style fixesChristian Grothoff
2020-03-21completing auditor splitChristian Grothoff
2020-03-21steps towards new split-auditor logicChristian Grothoff
2020-03-21rename fest on refactored auditor logicChristian Grothoff
generated by cgit v1.2.3 (git 2.39.1) at 2024-05-24 22:18:21 +0000