0005958: some accounts should not have a spending limit

ID	Project	Category	View Status	Date Submitted	Last Update
0005958	Taler	obsolete component	public	2019-11-01 21:50	2021-08-24 14:23

Reporter	Florian Dold	Assigned To	Marcello Stanisci	Resolution deadline
Implementer		Reviewer
Release signed by		Deployed by
Verifier		Communicator
Data protection authority notification required	No
CSIRT notification required	No
Estimated effort (hours)		Actual effort (hours)	0
Fast-track	No
Work package	none
Priority	high	Severity	feature	Reproducibility	always
Status	closed	Resolution	won't fix
Target Version	0.8	Fixed in Version	0.8

Summary	0005958: some accounts should not have a spending limit
Description	Accounts like "survey" shouldn't run out of funds, since this disrupts the tipping demo! Maybe these can be marked as "service accounts".
Tags	No tags attached.

Date Modified	Username	Field	Change
2019-11-01 21:50	Florian Dold	New Issue
2019-11-01 21:50	Florian Dold	Status	new => assigned
2019-11-01 21:50	Florian Dold	Assigned To	=> Marcello Stanisci
2020-07-27 15:34	Florian Dold	Status	assigned => informing
2020-07-27 15:34	Florian Dold	Resolution	open => won't fix
2020-07-27 15:34	Florian Dold	Note Added: 0016528
2020-08-06 23:44	Christian Grothoff	Fixed in Version	=> 0.8
2020-08-06 23:44	Christian Grothoff	Target Version	=> 0.8
2021-08-24 14:23	Christian Grothoff	Status	informing => closed
2022-08-23 18:26	Christian Grothoff	Category	bank (demonstrator) => py bank (demonstrator, obsolete)
2023-12-03 00:23	Christian Grothoff	Category	py bank (demonstrator, obsolete) => obsolete componet
2023-12-11 19:08	Florian Dold	Category	obsolete componet => obsolete component

Florian Dold 2020-07-27 15:34 manager ~0016528	This is IMHO already solved in a better way right now. We do normal "double entry book-keeping" where money is never created, but always deducted from the bank's "root" account, which can go negative.