results.tex (1844B)
1 \section{Results}\label{results} 2 Currently the Donau REST API is fully implemented. The Donau can manage any 3 number of charities using the \texttt{/charities} endpoint. 4 All the keys used for signing and blind signing are managed by the Donau 5 together with the Secmod helpers. 6 7 Overall the Donau is able to issue donation receipts and provide the necessary 8 donation statement to the donor, all while keeping the data anonymized and 9 protecting the privacy of the donor. It is also worth mentioning that the 10 unusual cryptography of blinded signatures does not effect the performance. 11 With the binding of the tax number to the donation receipts and the signature 12 of the tax authority with year-dependent keys, the receipts are absolutely 13 bound to a donor and to a year and cannot be falsified or imitated without 14 falsifying the signature. Therefore donation fraud can be prevented. By 15 summarizing the receipts into one single QR-Code, the user convenience for the 16 tax authority and for the donor could be improved. 17 18 Important components that are needed to operate the Donau are not yet 19 implemented. This includes the charity side and donor client side. The Android 20 verification app is only partially implemented. Although test where written to 21 ensure that the Donau endpoints operate as expected, there are still some other 22 bugs and most likely also unknown bugs, not yet found. 23 24 The tax authority emphasizes user convenience and simplicity in a system like 25 the Donau. The tax authority also mentioned the challenges that arise when 26 operating such a system in the federalism. Each party often has different 27 requirements that a system like the Donau should fulfill. 28 Although the Donau is in its early stages and the prototype has not yet been 29 deployed, the tax authority Zürich definitely sees potential in the user 30 convenience side of the Donau. 31