View Issue Details

IDProjectCategoryView StatusLast Update
0006721Talerlibeufin-nexuspublic2024-04-17 20:17
ReporterFlorian Dold Assigned ToFlorian Dold  
PrioritynormalSeverityfeatureReproducibilityhave not tried
Status assignedResolutionopen 
Target Versionpost-1.0 
Summary0006721: consider a way to synchronize the row_id with the TWG
DescriptionWe should be able to recover as cleanly as possible in case the LibEuFin state somehow gets purged.

The TWG might notify the exchange to reset to a lower row_id when the transactions request is "unreasonable".
TagsNo tags attached.


Christian Grothoff

2021-01-25 23:23

manager   ~0017393

I don't think the exchange can possibly reset -- it must not have duplicate row IDs. More importantly, it is necessary that the auditor sees/computes the same row IDs!

So what instead can/should be done, is that a resuming libeufin can be told to _begin_ its row IDs at a non-zero offset. That offset could then be extracted from the exchangedb.

Issue History

Date Modified Username Field Change
2021-01-25 15:14 Florian Dold New Issue
2021-01-25 15:14 Florian Dold Status new => assigned
2021-01-25 15:14 Florian Dold Assigned To => Christian Grothoff
2021-01-25 23:23 Christian Grothoff Note Added: 0017393
2021-01-25 23:23 Christian Grothoff Assigned To Christian Grothoff => Florian Dold
2022-08-25 21:12 Christian Grothoff Project Taler => libeufin
2022-08-25 21:12 Christian Grothoff Category exchange => General
2023-01-08 11:37 Christian Grothoff Category General => command-line tools
2023-01-08 11:37 Christian Grothoff Target Version => 1.0
2023-04-13 20:39 Florian Dold Category command-line tools => libeufin-cli
2023-04-13 20:50 Florian Dold Project libeufin => Taler
2023-04-13 20:50 Florian Dold Category libeufin-cli => General
2023-04-13 21:38 Florian Dold Category General => libeufin-nexus
2023-12-02 11:35 Christian Grothoff Severity minor => feature
2023-12-22 14:21 Christian Grothoff Target Version 1.0 => post-1.0