aboutsummaryrefslogtreecommitdiff
path: root/doc/design.md
diff options
context:
space:
mode:
authorRasmus Dahlberg <rasmus.dahlberg@kau.se>2021-10-12 17:51:16 +0200
committerRasmus Dahlberg <rasmus.dahlberg@kau.se>2021-10-12 17:51:16 +0200
commit924b2d40311831dd8158f63afe067fd43db7ee98 (patch)
treee1fb2cdf37c992ba644000719000cb5cedced7c3 /doc/design.md
parent8c10d09289289ddbc349503dac4b0493bf73b2b3 (diff)
cleaned-up more questions section
These questions are to some extent answered as part of our refactor, or addressed as things we are still open to think more about. I think we can leave them out for now and add them later _with answers_ if needed. I kept the privacy concerns question because that is not addressed anywhere yet. We think that the answer is "mostly none".
Diffstat (limited to 'doc/design.md')
-rw-r--r--doc/design.md6
1 files changed, 1 insertions, 5 deletions
diff --git a/doc/design.md b/doc/design.md
index e1f3b5e..4f7c06a 100644
--- a/doc/design.md
+++ b/doc/design.md
@@ -394,9 +394,5 @@ the original proposal by
which puts an authority right in the middle of a slowly evolving witnessing policy.
#### 4.5 - More questions
-- Why not store data in the log? XXX: answered enough already?
-- Why not store rich metadata in the log? XXX: answered enough already?
-- What (de)serialization parsers are needed and why?
-- What cryptographic primitives are supported and why?
- What are the privacy concerns?
-- How does it work with more than one log?
+- Add more questions here!