diff options
| author | Florian Dold <florian.dold@gmail.com> | 2018-10-03 00:50:42 +0200 |
|---|---|---|
| committer | Florian Dold <florian.dold@gmail.com> | 2018-10-03 00:50:42 +0200 |
| commit | 09c44df3a2fd71e453492fb1edf451436f4473e4 (patch) | |
| tree | 2b0064f079ed0a5a95058694eec1996698039007 /stuff.txt | |
| parent | eaf071a33682ecab342b9e5881d68f58b1caff9e (diff) | |
| download | dold-thesis-phd-09c44df3a2fd71e453492fb1edf451436f4473e4.tar.gz dold-thesis-phd-09c44df3a2fd71e453492fb1edf451436f4473e4.tar.bz2 dold-thesis-phd-09c44df3a2fd71e453492fb1edf451436f4473e4.zip | |
sync
Diffstat (limited to 'stuff.txt')
| -rw-r--r-- | stuff.txt | 18 |
1 files changed, 12 insertions, 6 deletions
@@ -1,17 +1,15 @@ Priorities: * Christian's feedback for chapter 2 -* add simple system diagram to intro -* Add full protocol to chapter 3 -* go over implementation * add benchmarks +** add complete description of what benchmark does +** discuss coinsim * add blockchain discussion to byz consensus -* discuss coinsim -* incorporate Christian's feedback for acks * Auditor diagram -* backport crypto stuff from FC paper +* add simple system diagram to intro * fix all references * fix bibliography (incl. output) +* fix gamma issue in security chapter stretch goals: * protocol diagrams for tipping and refunds @@ -20,6 +18,8 @@ stretch goals: -------------------------- Q&A: +where do we show how expensive refresh is in terms of the time needed? + would it not be better if the exchange knew about the amount for a contract and could refund automatically if the payment wasn't completed before the pay deadline? => No, since the customer can complete the payment themselves @@ -44,6 +44,12 @@ Should we rename RefreshRequest to RefreshPrepare? Where do we describe the indian merchant scenario? +Where do we clearly state the security assumptions used in practice? + +Does the customer check that the exchange gave the same +gamma when the protocol is replayed? +!!! It doesn't! + -------------------------- Issues: |