View Issue Details

IDProjectCategoryView StatusLast Update
0009387Talerspecificationpublic2025-05-10 02:11
ReporterChristian Grothoff Assigned Tooec Resolution deadline
ImplementerReviewer 
Release signed byDeployed by 
VerifierCommunicator 
Data protection authority notification requiredNo  
CSIRT notification requiredNo  
Estimated effort (hours)Actual effort (hours)0 
Fast-trackNo
Work packagenone
PriorityurgentSeverityfeatureReproducibilityN/A
Status closedResolutionfixed 
Platformi7OSDebian GNU/LinuxOS Versionsqueeze
Product Versiongit (master) 
Target Version1.0Fixed in Version1.0 
Summary0009387: introduce new withdraw protocol with single-signature for batch withdraw
DescriptionThis 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.
TagsNo tags attached.

Required notifications

Address or linkRemarkAdded byNotifiedActions

Relationships

child of 0009371 closedoec Design and implement a unified /withdraw endpoint for age-withdraw and batch-withdraw 

Activities

oec

2024-12-16 10:50

developer   ~0023881

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?

Christian Grothoff

2024-12-16 10:56

manager   ~0023882

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.

oec

2024-12-16 11:17

developer   ~0023883

Ah, of course, I meant the EXCHANGE_PROTOCOL_VERSION in exchange/src/exchange/taler-exchange-httpd_config.h, my bad.

oec

2025-03-28 12:34

developer   ~0024330

Implemented with 486a815183202b8b4e90949746db2e070a038dda
according to https://docs.taler.net/core/api-exchange.html#withdraw

Issue History

Date ModifiedUsernameFieldChange
2024-12-15 18:44Christian GrothoffNew Issue
2024-12-15 18:44Christian GrothoffStatusnew => assigned
2024-12-15 18:44Christian GrothoffAssigned To => oec
2024-12-16 09:54oecRelationship addedchild of 0009371
2024-12-16 10:50oecNote Added: 0023881
2024-12-16 10:56Christian GrothoffNote Added: 0023882
2024-12-16 11:17oecNote Added: 0023883
2025-03-28 12:34oecStatusassigned => informing
2025-03-28 12:34oecResolutionopen => fixed
2025-03-28 12:34oecFixed in Version => git (master)
2025-03-28 12:34oecNote Added: 0024330
2025-03-28 13:06Christian GrothoffFixed in Versiongit (master) => 1.0
2025-05-10 02:11Christian GrothoffStatusinforming => closed