summaryrefslogtreecommitdiff
path: root/stuff.txt
diff options
context:
space:
mode:
authorFlorian Dold <florian.dold@gmail.com>2018-11-13 00:43:54 +0100
committerFlorian Dold <florian.dold@gmail.com>2018-11-13 00:43:54 +0100
commit5f7e8e7a545684218bce2836dff19541e2bb2b36 (patch)
tree3d720c4a99afc2fa7cfb7d22ccc9d59a9bccbf10 /stuff.txt
parent33b64e3f02ee859d9ded3064704a254d833fb2ce (diff)
downloaddold-thesis-phd-5f7e8e7a545684218bce2836dff19541e2bb2b36.tar.gz
dold-thesis-phd-5f7e8e7a545684218bce2836dff19541e2bb2b36.tar.bz2
dold-thesis-phd-5f7e8e7a545684218bce2836dff19541e2bb2b36.zip
impl/typos
Diffstat (limited to 'stuff.txt')
-rw-r--r--stuff.txt21
1 files changed, 3 insertions, 18 deletions
diff --git a/stuff.txt b/stuff.txt
index 6279a41..394960d 100644
--- a/stuff.txt
+++ b/stuff.txt
@@ -2,10 +2,10 @@ priorities:
* impl eval (transaction rate!)
stretch goals:
-* talk about fungibility
+* nice system diagram for implementation scaling (incl. load balancing)
* put things in side-boxes
* taler libtool versioning in impl chapter?
-* add blockchain discussion / related work to byz consensus
+* add blockchain discussion / newer related work to byz consensus
* notation index
* glossary (copy from docs.taler.net)
* protocol diagrams for tipping
@@ -13,22 +13,9 @@ stretch goals:
* illustration for contract terms etc.
* full reproducible setup (describe Guix setup and configure flags) in appendix
* benchmark that shows DB perf doesn't degrade
-
-final submission (after committee):
+* talk about fungibility vs blockchain somewhere?
* screenshots in Firefox
-passes:
-* go through Taler docs and tools
- and see what parts are not documented
-* English
-* check that everything is cited properly
-
-missing citations:
-* monero
-* algorand, consensus stuff that jeff sent
-* blockmania
-* BIS reports (where?)
-
--------------------------
Q&A:
@@ -47,8 +34,6 @@ should the simple diagram be in the intro?
where do we explain wire plugins?
=> in the exchange implementation section
-where do we talk about wallet detection?
-
where do we show how expensive refresh is in terms of the time needed?
=> There is one single comparison (0% vs 10%) plus base latency,
is that enough?