path: root/design-documents
diff options
authorChristian Grothoff <>2021-01-06 20:00:11 +0100
committerChristian Grothoff <>2021-01-06 20:00:11 +0100
commit44931d751ef0dd091b13cecf05e9c869cab6528c (patch)
tree0227b3dd4c53a1f283cf5aef2367aaf4d91f4b04 /design-documents
parentb1841f2970d4f205774a0f0b667bd04770ca6c07 (diff)
parent275de898eeff924b0658adbbc3cd51cadcd749d6 (diff)
Merge branch 'master' of git+ssh://
Diffstat (limited to 'design-documents')
1 files changed, 2 insertions, 2 deletions
diff --git a/design-documents/011-auditor-db-sync.rst b/design-documents/011-auditor-db-sync.rst
index aba7b50..3443298 100644
--- a/design-documents/011-auditor-db-sync.rst
+++ b/design-documents/011-auditor-db-sync.rst
@@ -78,7 +78,7 @@ Proposed Solution
tables from other data *if* we need to recover from backup.
* On schema migration, halt exchange, once auditor DB has
synchronized, update all DB schema (the "ingress" DB schema
- may be update automatically when the exchange DB schema is
+ may be updated automatically when the exchange DB schema is
migrated, but the "trusted" DB of the auditor must most likely
be manually migrated), then finally resume "ingress" to "trusted"
helper-based DB synchronization and restart the exchange.
@@ -159,7 +159,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,