View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0009371 | Taler | specification | public | 2024-12-07 20:23 | 2025-05-10 04:10 |
Reporter | oec | Assigned To | oec | ||
Priority | normal | Severity | feature | Reproducibility | N/A |
Status | closed | Resolution | fixed | ||
Product Version | git (master) | ||||
Target Version | 1.0 | Fixed in Version | 1.0 | ||
Summary | 0009371: Design and implement a unified /withdraw endpoint for age-withdraw and batch-withdraw | ||||
Description | Right now, there is code duplication for handling calls to /batch-withdraw and /age-withdraw. This was OK for the prototype phase of /age-withdraw. However, now it is hurting maintenance and creates overhead when adding additional functionality, such as KYC and AML. Ultimately /withdraw and /age-withdraw should be unified into one endpoint and code shared between them. | ||||
Additional Information | This issue tracks the building of the specification. Children to this issue are implementation related tasks. | ||||
Tags | No tags attached. | ||||
parent of | 0009372 | closed | oec | Remove code duplication for /age-withdraw and /batch-withdraw |
parent of | 0009377 | closed | Christian Grothoff | [withdraw] refactor error handling |
parent of | 0009387 | closed | oec | introduce new withdraw protocol with single-signature for batch withdraw |
parent of | 0008704 | closed | oec | consider checking and storing output denominations in the refresh melt phase [5d] |
parent of | 0009483 | closed | oec | Implement new /blinding-prepare endpoint for csr preparation in batches |
parent of | 0009669 | closed | oec | Fix auditor failures after new withdraw endpoint was introduced |
|
Commit 486a815183202b8b4e90949746db2e070a038dda introduced the endpoints /withdraw, /reveal-withdraw and /blinding-prepare. Except for the auditor, all tests pass. |
|
After a series of commit, ending with 032865011b1705a683b651be6b747fc80ba79f8b, work on this has been finished. |
Date Modified | Username | Field | Change |
---|---|---|---|
2024-12-07 20:23 | oec | New Issue | |
2024-12-07 20:23 | oec | Status | new => assigned |
2024-12-07 20:23 | oec | Assigned To | => oec |
2024-12-07 20:26 | oec | Relationship added | parent of 0009372 |
2024-12-07 23:01 | Christian Grothoff | Target Version | post-1.0 => 1.1 |
2024-12-10 16:59 | oec | Relationship added | parent of 0009377 |
2024-12-16 10:54 | oec | Relationship added | parent of 0009387 |
2024-12-17 15:42 | Christian Grothoff | Target Version | 1.1 => 1.0 |
2024-12-29 23:58 | Christian Grothoff | Relationship added | parent of 0008704 |
2025-01-27 12:41 | oec | Relationship added | parent of 0009483 |
2025-03-18 10:52 | oec | Relationship added | parent of 0009626 |
2025-03-25 12:36 | Christian Grothoff | Relationship added | child of 0009639 |
2025-03-28 13:37 | oec | Relationship added | parent of 0009669 |
2025-03-28 13:38 | oec | Note Added: 0024331 | |
2025-05-07 21:40 | oec | Relationship deleted | parent of 0009626 |
2025-05-07 21:40 | oec | Relationship deleted | child of 0009639 |
2025-05-07 21:41 | oec | Status | assigned => resolved |
2025-05-07 21:41 | oec | Resolution | open => fixed |
2025-05-07 21:41 | oec | Fixed in Version | => git (master) |
2025-05-07 21:41 | oec | Note Added: 0024819 | |
2025-05-08 16:32 | Christian Grothoff | Fixed in Version | git (master) => 1.0 |
2025-05-10 04:10 | Christian Grothoff | Status | resolved => closed |