[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[donau] branch master updated (d4ec313 -> c6863c0)
From: |
gnunet |
Subject: |
[donau] branch master updated (d4ec313 -> c6863c0) |
Date: |
Tue, 21 Jan 2025 18:14:04 +0100 |
This is an automated email from the git hooks/post-receive script.
jonathan-levin pushed a change to branch master
in repository donau.
from d4ec313 3.2.2: grammar fix
new 780b906 3.1: remove space
new c0eff53 Remove confusing mention of yearly donation limit for
charities
new c6863c0 3.2: minor edits
The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
doc/usenix-security-2025/paper/technicaldesign.tex | 25 +++++++++++-----------
1 file changed, 12 insertions(+), 13 deletions(-)
diff --git a/doc/usenix-security-2025/paper/technicaldesign.tex
b/doc/usenix-security-2025/paper/technicaldesign.tex
index 8c1ccc3..4b5f292 100644
--- a/doc/usenix-security-2025/paper/technicaldesign.tex
+++ b/doc/usenix-security-2025/paper/technicaldesign.tex
@@ -97,7 +97,7 @@ some cryptographic background followed by the setup and usage.
\textrm{Slightly more formally, we define blind signatures as a quadruple
of algorithms:}
\begin{itemize}
- \item $ KeyGen(1^\lambda)$: Generates a verification/signing key pair
$(K^{\pub}, K^{\priv})$.
+ \item $KeyGen(1^\lambda)$: Generates a verification/signing key pair
$(K^{\pub}, K^{\priv})$.
\item $Blind(m, b, K^{\pub})$: Takes a message $m$, blinding factor $b$,
and verification key $K^{\pub}$ of the signer and computes the blinded message
$\overline{m}$.
\item $BlindSign(K^{\priv}, \overline{m})$: Takes secret signing key
$K^{\priv}$ and blinded message $\overline{m}$ and computes the blind signature
$\overline{\sigma}$.
\item $Unblind(\overline{\sigma}, b, K^{\pub})$: Takes blind signature
$\overline{\sigma}$, blinding factor $b$ and verification key $K^{\pub}$ of the
signer, and returns the unblinded signature $\sigma$ on message $m$ (or $\bot$).
@@ -106,8 +106,9 @@ some cryptographic background followed by the setup and
usage.
\subsection{Key generation and initial
setup}\label{key_generation_and_initial_setup}
-Before incognito donations to charities can be executed, all parties (Donau,
-charities, and donors) must perform an initial setup.
+Before incognito donations to charities can be executed, all participants in
+the donation system (i.e., the Donau, charities, and donors) must perform some
+initial setup steps.
\subsubsection{Donau key generation}\label{donau_key_generation}
\begin{enumerate}
@@ -123,23 +124,21 @@ 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}
-Each donor generates a personal \textbf{Donor Identifier} by computing a
-salted hash of their taxpayer ID.
-They use this Donor Identifier value for each donation they make and later to
-receive a donation receipt from the Donau.
+Each donor generates a personal \textbf{Donor Identifier} by computing a salted
+hash of their taxpayer ID.
+A donor uses their Donor Identifier every time they
+make a donation and again when requesting a donation receipt from the Donau.
-The donor computes their Donor Identifier $\DI$ as
+The donor computes their Donor Identifier $\DI$ as the hash
\begin{align*}
\DI = H(\texttt{TAXID}, S)
\end{align*}
@@ -228,7 +227,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.
--
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.
- [donau] branch master updated (d4ec313 -> c6863c0),
gnunet <=