aboutsummaryrefslogtreecommitdiff
path: root/src/exchangedb/test_exchangedb.c
AgeCommit message (Collapse)Author
2022-11-27-db tests pass againChristian Grothoff
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-11-01remove wad fee, kyc fee and kyc-timeoutChristian Grothoff
2022-10-30add support for reserve open/close operations to auditor, begin to split off ↵Christian Grothoff
purse auditing logic
2022-10-15-modify DB logic to return open/close requests in reserve historyChristian Grothoff
2022-08-22-fix clang compiler warningsChristian Grothoff
2022-08-20-major KYC update, fixes misc. issuesChristian Grothoff
2022-08-14-start with DB cleanupChristian Grothoff
2022-08-14-work on new KYC logic: tests pass againChristian Grothoff
2022-08-11major rework of the KYC logic, making it more configurable, not complete, ↵Christian Grothoff
but tests pass again
2022-07-06fix auditor refund fee calculationsChristian Grothoff
2022-07-05-remove dead argumentChristian Grothoff
2022-06-13-towards coin audits with purse depositsChristian Grothoff
2022-05-22-towards purse merge and history requests in reserve history (incomplete)Christian Grothoff
2022-03-31privatize more signature structs, simplify codeChristian Grothoff
2022-03-27-fix leak, uninitialized psChristian Grothoff
2022-03-27-remove tiny field, no longer neededChristian Grothoff
2022-03-27towards removing tiny bitChristian Grothoff
2022-03-24rework deposits sharding, towards making aggregator faster (not necessarily ↵Christian Grothoff
done)
2022-03-05refactor /wire to include logic to return the wad fee (for W2W payments)Christian Grothoff
2022-03-03use 32 byte hash for hpayto, use that for joins on queries to better align ↵Christian Grothoff
queries with partitions
2022-03-03include shard when marking deposits tiny/done to make better use of ↵Christian Grothoff
partitions/shards
2022-03-02fix num partitionsMarco Boss
2022-03-02include partitioning logic in dbinitMarco Boss
2022-02-28get test-auditor and #7181 to passChristian Grothoff
2022-02-21-big renaming of structs for consistent naming with P suffixChristian Grothoff
2022-02-20-ensure different HKDF is used in melt vs. withdrawChristian 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-15-correctly implement CS idempotency check on withdrawChristian Grothoff
2022-02-12-address FIXMEsChristian Grothoff
2022-02-11-simplify: nonce no longer hashedChristian Grothoff
2022-02-10-fixes to tests, and half-baked fixes for CS-/link (still fails)Christian Grothoff
2022-02-07fix DB API for generic blinded planchet storageChristian Grothoff
2022-02-07get DB test to buildChristian Grothoff
2022-02-07-rename festChristian Grothoff
2022-02-04uncrustifyGian Demarmels
2022-02-04exchangedb fixGian Demarmels
2022-02-04resolves merge conflictsGian Demarmels
2022-02-04refactor TALER_coin_ev_hashGian Demarmels
2022-02-04include denom_pub into coin_ev_hashGian Demarmels
2022-02-04implement feedbackLucien Heuzeveldt
2022-02-04refactoringGian Demarmels
2022-02-04removed varargsGian Demarmels
2022-02-04added CS data structures, implemented CS keypairGian 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-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-25-fix FTBFSChristian 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-19denormalize reserve_pub in reserve tables to enable shardingChristian Grothoff
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-14 09:19:12 +0000