View Issue Details

IDProjectCategoryView StatusLast Update
0004962Talerauditorpublic2018-04-15 18:34
ReporterChristian Grothoff Assigned ToChristian Grothoff 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
PrioritylowSeverityfeatureReproducibilityN/A
Status closedResolutionfixed 
Platformi7OSDebian GNU/LinuxOS Versionsqueeze
Product Versiongit (master) 
Target Version0.5Fixed in Version0.5 
Summary0004962: generate financial report from audit DB
DescriptionThe main auditor tool checks signatures and generates a report about "bad" things. We should probably have a separate tool to generate a business report about the financial situation of the exchange. The auditor does (largely?) store the required information nicely in the database, we just need to extract and layout it.
Additional InformationSee in particular (for now):

* select_historic_denom_revenue() - coin expiration profits
* get_denomination_summary() - current overall balance from fees and risk exposure
* select_historic_losses() - for emergency (0003887) losses
TagsNo tags attached.

Required notifications

Address or linkRemarkAdded byNotifiedActions

Activities

Christian Grothoff

2017-10-20 20:54

manager   ~0012498

Basic scripting logic for TeX template / JSON-instantiation exists.

What is now needed:
1) Auditor report (JSON output) needs to be made nicer, in particular better summaries (sum up misc. fields), add time range, add name of auditor & exchange, etc. So that the JSON provides more data for a nice report.

2) TeX template needs to be improved, in particular handling of very large tables, and just the general format/output (and actually reporting everything that could be in an auditor's report).

Christian Grothoff

2017-11-06 18:14

manager   ~0012570

As of cc09fbb..45c443f, the TeX template should nicely render all reports the auditor may generate, and the auditor was modified to include totals for summaries as required.

Naturally, was we progress on 0004958 further updates to the templating will be required, but the basic report rendering logic is now there and complete.

Issue History

Date ModifiedUsernameFieldChange
2017-03-18 22:09Christian GrothoffNew Issue
2017-03-18 22:09Christian GrothoffStatusnew => assigned
2017-03-18 22:09Christian GrothoffAssigned To => Christian Grothoff
2017-03-18 22:12Christian GrothoffAssigned ToChristian Grothoff =>
2017-03-18 22:12Christian GrothoffPrioritynormal => low
2017-03-18 22:12Christian GrothoffStatusassigned => implementing
2017-03-18 22:12Christian GrothoffAdditional Information Updated
2017-03-18 22:25Christian GrothoffTarget Version => 0.7.1
2017-04-08 22:09Christian GrothoffAssigned To => Christian Grothoff
2017-04-08 22:09Christian GrothoffStatusimplementing => assigned
2017-10-20 20:54Christian GrothoffNote Added: 0012498
2017-11-06 18:14Christian GrothoffStatusassigned => informing
2017-11-06 18:14Christian GrothoffResolutionopen => fixed
2017-11-06 18:14Christian GrothoffFixed in Version => 0.5
2017-11-06 18:14Christian GrothoffNote Added: 0012570
2017-11-06 18:14Christian GrothoffTarget Version0.7.1 => 0.5
2018-04-15 18:34Christian GrothoffStatusinforming => closed