summaryrefslogtreecommitdiff
path: root/design-documents/011-auditor-db-sync.rst
diff options
context:
space:
mode:
authorThien-Thi Nguyen <ttn@gnuvola.org>2021-01-05 16:36:05 -0500
committerThien-Thi Nguyen <ttn@gnuvola.org>2021-01-05 16:36:05 -0500
commit275de898eeff924b0658adbbc3cd51cadcd749d6 (patch)
tree465ca62336cd3e459392576a8d267a3bd40d5005 /design-documents/011-auditor-db-sync.rst
parent315ef919bdc1332ceca519f13fb4e32c9a67d67d (diff)
downloaddocs-275de898eeff924b0658adbbc3cd51cadcd749d6.tar.gz
docs-275de898eeff924b0658adbbc3cd51cadcd749d6.tar.bz2
docs-275de898eeff924b0658adbbc3cd51cadcd749d6.zip
fix typo: s/ingres/ingress/
Diffstat (limited to 'design-documents/011-auditor-db-sync.rst')
-rw-r--r--design-documents/011-auditor-db-sync.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/design-documents/011-auditor-db-sync.rst b/design-documents/011-auditor-db-sync.rst
index 505f7b4..f4befdf 100644
--- a/design-documents/011-auditor-db-sync.rst
+++ b/design-documents/011-auditor-db-sync.rst
@@ -131,7 +131,7 @@ Drawbacks
is the answer, to be investigated what performs better.
* A malicious exchange could theoretically send expensive transactions
to the auditor via the replication mechanism (possibly ones that
- it did not even execute locally itself) to DoS the "ingres"
+ it did not even execute locally itself) to DoS the "ingress"
database. This would be noticed primarily by load
monitoring or even the auditor lagging unusually far behind the
exchange's transaction history. We believe this is acceptable,