aboutsummaryrefslogtreecommitdiff
path: root/src/lib/exchange_api_common.c
AgeCommit message (Collapse)Author
2022-12-29expand DB API with AML functions, fix purse refund calculations in ↵Christian Grothoff
libtalerexchange
2022-11-04policy extensions and age restriction refactoringÖzgür Kesim
- refactoring of extension-plugin-mechanism - refactoring of age restriction extension - added policy extensions plugin plumbing - added DB schema and api - policy_details - policy_fulfillments
2022-10-22-remove bogus testsChristian Grothoff
2022-10-15handle purse-refund and reserve-open-deposit events in coin history in ↵Christian Grothoff
libtalerexchange
2022-10-15handle reserve open/close responses in reserve history in libtalerexchangeChristian Grothoff
2022-08-11major rework of the KYC logic, making it more configurable, not complete, ↵Christian Grothoff
but tests pass again
2022-07-05-annotate bugsChristian Grothoff
2022-07-01-exchange_api_batch_deposit.c compilesChristian Grothoff
2022-06-28-fix issue with missing signature over denomination and age restriction hash ↵Christian Grothoff
in purse deposit
2022-06-07-more minor bugfixesChristian Grothoff
2022-06-05no purse fee if purse is successfully mergedChristian Grothoff
2022-06-05complete P2P/W2W conflict handling, deduplicate code across handlersChristian Grothoff
2022-06-05-work on error proof response checking for p2p paymentsChristian Grothoff
2022-06-04-more work on p2p payments and tests thereofChristian Grothoff
2022-06-04handle case where purse expiration refunded the coin's deposited amountChristian Grothoff
2022-06-02-work on P2P payment detailsChristian Grothoff
2022-05-30-fix reserve history, include in testsChristian Grothoff
2022-05-29add batch signing support to taler-exchange-secmod-rsaChristian Grothoff
2022-05-23handle purse deposit client-sideChristian Grothoff
2022-05-23-misc fixes to reserve historyChristian Grothoff
2022-05-23-deduplicate and expand reserve history validation logic in testing libraryChristian Grothoff
2022-05-23-add missing break, clean up fee logicChristian Grothoff
2022-05-23-refactor coin history checkerChristian Grothoff
2022-05-22-complete extended reserve history signature check logic to libtalerexchangeChristian Grothoff
2022-05-22-towards client-side support for merge and history requests in reserve historyChristian Grothoff
2022-05-22-more work on reverse historyChristian Grothoff
2022-04-05adapt to latest GNUnet API: GNUNET_JSON_spec_mark_optional() changedChristian Grothoff
2022-03-29centralize exchange online signature logicChristian Grothoff
2022-03-21add logic to check timestamp, revise history balance calculation logic in clientChristian Grothoff
2022-03-20towards support for new reserve history/status APIsChristian Grothoff
2022-02-22double melt test no works with age restrictionÖzgür Kesim
- added missing field h_age_commitment in exchange's error response - slight refactoring
2022-02-22[age restriction] progress 16/n - refresh/reveal/link testsÖzgür Kesim
Age restriction works now with withdraw, melt/refresh/reveal and link, including tests. However, there is still a problem with the tests: The melting operation "refresh-melt-failing-age" that should fail (because of conflict), but currently fails for other reasons. I decided to disable that particular test (and the next) and submit the patch I have so far.
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-16[age restriction] progress 14/n - withdraw and depositÖzgür Kesim
Age restriction support for - withdraw is done and tested - deposit is done and tested TODOs: - melt/refresh/reveal - link ------ Added functions - TALER_age_restriction_commit - TALER_age_commitment_derive - TALER_age_commitment_hash - TALER_age_restriction_commitment_free_inside - Hash of age commitment passed around API boundaries Exchangedb adjustments for denominations - all prepared statements re: denominations now handle age_mask - signature parameters adjusted Hash and signature verification of /keys adjusted - Hashes of (normal) denominations and age-restricted denominations are calculated seperately - The hash of the age-restricted ones will then be added to the other hash - The total hash is signed/verified Tests for withdraw with age restriction added - TALER_EXCHANGE_DenomPublickey now carries age_mask - TALER_TESTING_cmd_withdraw_amount* takes age parameter - TALER_TESTING_find_pk takes boolean age_restricted - WithdrawState carries age_commitment and its hash - withdraw_run derives new age commitment, if applicable - Added age parameter to testing (13 as example) Various Fixes and changes - Fixes of post handler for /management/extensions - Fixes for offline tool extensions signing - Slight refactoring of extensions - Age restriction extension simplified - config is now global to extension - added global TEH_age_restriction_enabled and TEH_age_mask in taler-exchange-httpd - helper functions and macros introduced
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-25v12: also do not sign over merchant_pub in REFUND signature, centralize logicChristian 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-16-fix recoup uglinessChristian Grothoff
2021-12-14introducing GNUNET_TIME_Timestamp, recoup now with amountsChristian Grothoff
2021-12-11fix #7123Christian Grothoff
2021-12-06-fix balance calculationChristian Grothoff
2021-12-05-add FIXMEsChristian Grothoff
2021-11-19-fix leaks and compiler warningsChristian Grothoff
2021-11-06introduce TALER_wallet_deposit_verifyChristian Grothoff
2021-10-27fix lib/ FTBFSChristian Grothoff
2021-10-27-work on FTBFS;Christian Grothoff
2021-10-27-fix misc FTBFSChristian Grothoff
2021-10-17implement /kyc-wallet in libtalerexchangeChristian Grothoff