commit c0eff53990745e3afba0a112c108e61500c74a2e
parent 780b90671354fcf4bdfeb277318e2608f2dfca41
Author: Jonathan <ondesmartenot@riseup.net>
Date: Wed, 22 Jan 2025 01:12:25 +0800
Remove confusing mention of yearly donation limit for charities
Diffstat:
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/doc/usenix-security-2025/paper/technicaldesign.tex b/doc/usenix-security-2025/paper/technicaldesign.tex
@@ -123,14 +123,12 @@ currency denominations $x$ that a donation can be composed of.
\item Each charity generates its own Ed25519 charity key $( C^{\pub},
C^{\priv} )$.
\item The charity also fetches the Donation Unit public keys from the Donau.
- \item The charity transmits its public key $C^{\pub}$ and its requested
-yearly donation limit (if any) to the party controlling the Donau (e.g the
+ \item The charity transmits its public key $C^{\pub}$ to the party controlling the Donau (e.g the
local tax authority) using an authenticated channel.
\item The party in charge of Donau administration (usually the relevant tax
authority) ensures that the charity is authentic and a legally recognized
charitable organization. After successful verification, the charity public key
-$C^{\pub}$ together with its requested yearly donation limit (if any)
-are registered in the Donau database.
+$C^{\pub}$ is registered in the Donau database.
\end{enumerate}
\subsubsection{Donor Identifier generation}
@@ -228,7 +226,7 @@ The charity sends the array $\vec{\mu}$ of BKPs and their signature $\sigma_c$ t
\subsection{Donau generates donation receipt}\label{donau_creates_donation_receipt}
When the Donau receives a signed set of BKPs from a charity, it verifies the charity's signature.
-It then checks that no legal restrictions, such as a possible yearly donation limit for the charity, is being violated.
+It then checks that no legal restrictions are being violated.
If not, the Donau increments its record of the charity's total receipts by the
total amount of the donation, i.e., the sum of the denominations used in the
BKPs.
