View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009387 | Taler | specification | public | 2024-12-15 19:44 | 2024-12-16 12:17 |
| Reporter | Christian Grothoff | Assigned To | oec | ||
| Priority | urgent | Severity | feature | Reproducibility | N/A |
| Status | assigned | Resolution | open | ||
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
| Product Version | git (master) | ||||
| Target Version | 1.0 | ||||
| Summary | 0009387: introduce new withdraw protocol with single-signature for batch withdraw | ||||
| Description | This way, we can align the age and non-age withdraw paths better and don't have a major DB transition with major backwards-compatibility issues in the future. | ||||
| Tags | No tags attached. | ||||
|
|
I like to add a note to the docs/core/api-exchange.rst stating from which version on the new API is available. That should be protocol version 1.0.1 (so that the API of 0.14.0 is still accepted) , correct? |
|
|
Eh, there is no protocol version 1.0.1. You should state that the new API will be available as of **v24**, *or* if you're quite unsure about this being done soon, using "**vUWITHDRAW** and then we'll do a global search-and-replace of vUWITHDRAW with vXX once we know the number. |
|
|
Ah, of course, I meant the EXCHANGE_PROTOCOL_VERSION in exchange/src/exchange/taler-exchange-httpd_config.h, my bad. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-12-15 19:44 | Christian Grothoff | New Issue | |
| 2024-12-15 19:44 | Christian Grothoff | Status | new => assigned |
| 2024-12-15 19:44 | Christian Grothoff | Assigned To | => oec |
| 2024-12-16 10:54 | oec | Relationship added | child of 0009371 |
| 2024-12-16 11:50 | oec | Note Added: 0023881 | |
| 2024-12-16 11:56 | Christian Grothoff | Note Added: 0023882 | |
| 2024-12-16 12:17 | oec | Note Added: 0023883 |
