path: root/contrib
diff options
authorChristian Grothoff <>2020-01-19 14:53:24 +0100
committerChristian Grothoff <>2020-01-19 14:53:31 +0100
commitdbf85bbc0d23b044aa47be67ceae4e6ecd709298 (patch)
tree9dcc2c8dc8e6d0fee4a5524ea9058b57ea9a0d76 /contrib
parentca7d8434dd05a77eb4202b12f3db10d42b71f88b (diff)
clarify FIXMEs
Diffstat (limited to 'contrib')
1 files changed, 2 insertions, 2 deletions
diff --git a/contrib/auditor-report.tex.j2 b/contrib/auditor-report.tex.j2
index a21ded1c..7704d54a 100644
--- a/contrib/auditor-report.tex.j2
+++ b/contrib/auditor-report.tex.j2
@@ -279,14 +279,14 @@ Note that some minimal lag may be normal as transactions may be in-flight.
This section analyzes the lag, which is by how much the exchange's
database reporting is behind in providing us with information about
-deposit confirmations. Merchants probabilisitcally report deposit
+deposit confirmations. Merchants probabilistically report deposit
confirmations to the auditor directly, so if the exchange is slow at
synchronizing its database with the auditor, some deposit
confirmations may be known at the auditor only directly. However, any
delta not accounted for by database synchronization delays is an
indicator of a malicious exchange (or online singing key compromise)
and should be answered by revoking the exchange's online siging keys.
-% FIXME: reference PhD thesis?
+% TODO: maybe reference PhD thesis on this?
The total amount the exchange currently lags behind is
{\bf {{ data.missing_deposit_confirmation_total }} } from a total number of