| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2024-11-05 | working through auditors | Christian Grothoff | |
| 2024-10-25 | remove dead GNUNET_STRINGS_get_utf8_args(), just a NOP | Christian Grothoff | |
| 2024-09-14 | santity for /balances and /progress endpoints, fix various leaks and other bugs | Christian Grothoff | |
| 2024-08-28 | fix patch from Nic and also fix various other auditor bugs found during review | Christian Grothoff | |
| 2024-08-26 | fixes | Christian Grothoff | |
| 2024-08-26 | add error handling | Christian Grothoff | |
| 2024-08-25 | auditor test fixes | Christian Grothoff | |
| 2024-08-24 | improve error handling of reserves auditor | Christian Grothoff | |
| 2024-08-24 | improve error handling of reserves auditor | Christian Grothoff | |
| 2024-08-23 | fix uninit variable | Christian Grothoff | |
| 2024-08-21 | clean up auditor and bugfixes | Christian Grothoff | |
| 2024-08-21 | auditor bugfixes | Christian Grothoff | |
| 2024-08-20 | clean up auditor code more | Christian Grothoff | |
| 2024-08-20 | fix some helper FTBFS | Christian Grothoff | |
| 2024-08-19 | get finally rid of TALER_ARL_report | Christian Grothoff | |
| 2024-06-25 | typos | Christian Grothoff | |
| 2024-06-24 | real-time-auditor | Nic Eigel | |
| 2024-03-25 | remove -m option, add -t option to all auditor helpers | Christian Grothoff | |
| 2024-02-07 | auditordb tabularasa | Christian Grothoff | |
| 2023-11-28 | fix spelling issues | Christian Grothoff | |
| 2023-10-25 | new blind signing code builds | Christian Grothoff | |
| 2023-09-18 | remove coin and reserve histories from exchange replies | Christian Grothoff | |
| 2023-02-21 | -misc minor bugfixes | Christian Grothoff | |
| 2022-11-03 | -ref bug | Christian Grothoff | |
| 2022-11-02 | -doxygen | Christian Grothoff | |
| 2022-10-30 | -doxygen | Christian Grothoff | |
| 2022-10-30 | add support for reserve open/close operations to auditor, begin to split off ↵ | Christian Grothoff | |
| purse auditing logic | |||
| 2022-08-14 | -work on new KYC logic: tests pass again | Christian Grothoff | |
| 2022-07-05 | -annotate bugs | Christian Grothoff | |
| 2022-07-01 | -exchange_api_batch_deposit.c compiles | Christian Grothoff | |
| 2022-06-28 | -fix issue with missing signature over denomination and age restriction hash ↵ | Christian Grothoff | |
| in purse deposit | |||
| 2022-06-26 | -fix misc doxygen warnings, code clean up | Christian Grothoff | |
| 2022-06-19 | -add missing checkpointing logic | Christian Grothoff | |
| 2022-06-18 | -more work on taler-helper-auditor-reserve p2p audits | Christian Grothoff | |
| 2022-06-15 | -more DB logic for taler-helper-auditor-reserves | Christian Grothoff | |
| 2022-06-15 | -more DB prep work towards reserve auditing with p2p payments | Christian Grothoff | |
| 2022-06-14 | -preparatory steps to expand auditor to know about purse and history fees | Christian Grothoff | |
| 2022-06-14 | -include purse deposits in aggregation coin value analysis; note issues ↵ | Christian Grothoff | |
| discovered with deposit fee waiver logic | |||
| 2022-03-31 | privatize more signature structs, simplify code | Christian Grothoff | |
| 2022-03-05 | refactor /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 suffix | Christian Grothoff | |
| 2022-02-17 | -fix CS nonce reuse check logic | Christian Grothoff | |
| 2022-02-12 | -address misc. fixmes | Christian Grothoff | |
| 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-16 | -fix recoup ugliness | Christian Grothoff | |
| 2021-12-14 | introducing GNUNET_TIME_Timestamp, recoup now with amounts | Christian Grothoff | |
| 2021-11-05 | -fixes | Christian Grothoff | |
| 2021-10-27 | fix auditor FTBFS | Christian Grothoff | |
| 2021-10-14 | -basic logic for withdraw KYC checks | Christian Grothoff | |
| 2021-08-23 | -remove sessions also from auditor | Christian Grothoff | |
 |
index : slackcoder/taler/exchange | |
| Mirror |
| aboutsummaryrefslogtreecommitdiff |