View Issue Details

IDProjectCategoryView StatusLast Update
0007269Talerspecificationpublic2024-01-12 14:03
ReporterChristian Grothoff Assigned ToChristian Grothoff  
PrioritylowSeverityfeatureReproducibilityN/A
Status closedResolutionfixed 
Platformi7OSDebian GNU/LinuxOS Versionsqueeze
Product Versiongit (master) 
Target Version0.9Fixed in Version0.9 
Summary0007269: forcing reserve closure is not implemented
DescriptionThe question is if we want this, and if so some details (like should we include a timestamp from the client, and if so what does that timestamp signify) should be discussed. Forcing reserve closure might be a nice feature if we have otherwise long-lived reserves for which auto-closure is not implemented. Goes together with discussions about accounts, account fees and the number of purses an account can create 'for free'.
TagsNo tags attached.

Activities

Christian Grothoff

2022-10-20 12:25

manager   ~0019259

What is now missing is the auditor support -- and more testing.

Christian Grothoff

2022-11-03 00:11

manager   ~0019350

Now supported by auditor. More testing will require wallet/merchant support first.

Issue History

Date Modified Username Field Change
2022-07-05 11:23 Christian Grothoff New Issue
2022-07-05 11:23 Christian Grothoff Status new => assigned
2022-07-05 11:23 Christian Grothoff Assigned To => Christian Grothoff
2022-07-05 13:20 Christian Grothoff Priority normal => low
2022-10-20 12:25 Christian Grothoff Note Added: 0019259
2022-11-03 00:11 Christian Grothoff Status assigned => resolved
2022-11-03 00:11 Christian Grothoff Resolution open => fixed
2022-11-03 00:11 Christian Grothoff Fixed in Version => 0.9
2022-11-03 00:11 Christian Grothoff Note Added: 0019350
2022-11-03 00:11 Christian Grothoff Target Version => 0.9
2022-11-04 20:52 Christian Grothoff Status resolved => closed
2024-01-12 14:03 Christian Grothoff Category exchange API (HTTP specification) => specification