| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2022-04-26 | -implement purses get db sketch | Christian Grothoff | |
| 2022-04-24 | -fix fieldnames, regenerated DBs | Christian Grothoff | |
| 2022-04-23 | add purses-get to build | Christian Grothoff | |
| 2022-04-22 | add purses_deposit to build | Christian Grothoff | |
| 2022-04-21 | -skeleton logic for deposits into purse | Christian Grothoff | |
| 2022-04-21 | add taler-exchange-httpd_reserves_purse.c to build | Christian Grothoff | |
| 2022-04-20 | -refactor deposits_get logic to help ttn with signature logic refactoring | Christian Grothoff | |
| 2022-04-19 | find extensions case-insensitively | Florian Dold | |
| 2022-04-15 | -skeleton for p2p test | Christian Grothoff | |
| 2022-04-12 | -implementing purse merge DB logic | Christian Grothoff | |
| 2022-04-11 | -towards new GET /contracts/$C_PUB hander | Christian Grothoff | |
| 2022-04-11 | -add draft handler for purse merge client request | Christian Grothoff | |
| 2022-04-11 | -load wire fees only when needed | Christian Grothoff | |
| 2022-04-11 | -draft implementation of /purses//merge endpoint | Christian Grothoff | |
| 2022-04-08 | -draft for merge endpoint | Christian Grothoff | |
| 2022-04-06 | -towards testing purse creation | Christian Grothoff | |
| 2022-04-05 | adapt to latest GNUnet API: GNUNET_JSON_spec_mark_optional() changed | Christian Grothoff | |
| 2022-04-04 | -fix FTBFS | Christian Grothoff | |
| 2022-04-01 | work on purse creation logic | Christian Grothoff | |
| 2022-03-24 | first draft of service API for p2p payments | Christian Grothoff | |
| 2022-03-24 | implement more taler-crypto-worker ops | Florian Dold | |
| 2022-03-21 | add logic to check timestamp, revise history balance calculation logic in client | Christian Grothoff | |
| 2022-03-21 | first rough-cut implementation of POST /reserves//status | Christian Grothoff | |
| 2022-03-19 | improve style of some SQL queries (no semantic change) | Christian Grothoff | |
| 2022-03-08 | add missing files for system documentation book | Florian Dold | |
| 2022-03-05 | add more logic for new global fees | Christian Grothoff | |
| 2022-02-19 | -bump version requirement | Christian Grothoff | |
| 2022-02-19 | reject wire deadline of 'never' (#7157) | Christian Grothoff | |
| 2022-02-19 | -update GANA | Christian Grothoff | |
| 2022-02-13 | -remove redundancies in the refresh-melt computation and fix uninitialized ↵ | Christian Grothoff | |
| bks return value | |||
| 2022-02-12 | -address FIXMEs | Christian Grothoff | |
| 2022-02-12 | -doxygen fixes | Christian Grothoff | |
| 2022-02-06 | merge more improvements from Dora | Christian Grothoff | |
| 2022-02-04 | split tests by rsa/cs | Christian Grothoff | |
| 2022-02-04 | resolves merge conflicts | Gian Demarmels | |
| 2022-02-01 | corrections from Dora | Christian Grothoff | |
| 2022-01-31 | cbdc - Italian edition | Christian Grothoff | |
| 2022-01-27 | fix RFC 8785 JSON normalization | Florian Dold | |
| 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 | |||
| 2022-01-10 | improve error response for withdrawal | Florian Dold | |
| 2021-12-28 | -cleanup | 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-23 | [age restriction] progress 8/n | Özgür Kesim | |
| More work towards support for extensions and age restriction - updated gana - added handler for DB-Event - added TEH_extensions_init() and _done() - added global for age restriction - added stub for post handler - added SQL-table for extension metadata - added enum type for extensions and other data structures Also: - fixed some warnings -Wmaybe-unitialized | |||
| 2021-12-11 | fix uncrustify | Christian Grothoff | |
| 2021-12-08 | optimize /deposit logic to minimize serialization failures (presumably) | Christian Grothoff | |
| 2021-11-21 | update contrib/gana to b7320181c5e0d95c6f2e2a9e5c53dce0bc1a35a8 | Thien-Thi Nguyen | |
| 2021-11-21 | fix #7099 | Christian Grothoff | |
| 2021-11-15 | avoid duplication | Christian Grothoff | |
| 2021-11-15 | -better types | Christian Grothoff | |
| 2021-11-09 | -fixes for test | Christian Grothoff | |
 |
index : exchange.git | |
| Exchange implementation. |
| summaryrefslogtreecommitdiff |