[taler-anastasis] branch master updated: nana comments

[gnunet]

This is an automated email from the git hooks/post-receive script.

grothoff pushed a commit to branch master
in repository anastasis.

The following commit(s) were added to refs/heads/master by this push:
     new 75ea0ca  nana comments
75ea0ca is described below

commit 75ea0ca42e4a44fd6cf9cd382519f095204a0ba9
Author: Christian Grothoff <address@hidden>
AuthorDate: Mon Jan 27 13:58:12 2020 +0100

    nana comments
---
 doc/ledger.txt | 26 ++++++++++++++++++--------
 1 file changed, 18 insertions(+), 8 deletions(-)

diff --git a/doc/ledger.txt b/doc/ledger.txt
index ecd532d..9e609d0 100644
--- a/doc/ledger.txt
+++ b/doc/ledger.txt
@@ -9,6 +9,13 @@ Tagline (140 c): Password-less key recovery via multi-factor 
multi-party authent
 
 Brief description: (1000 c)
 
+Anastasis will allow users to securely recover secret keys without
+necessarily relying on passwords or other key material.  Instead, the
+key material is split across multiple independent Anastasis service
+providers, and users are enabled to recover their master key by
+authenticating with each provider.
+
+% NANA: be specific about 'in situations' => wallets, finance, OpenPGP
 In situations where users can remember sufficiently strong
 passphrases, key recovery is easily implemented by deriving the key
 from the secret passphrase.  However, for many applications this
@@ -17,12 +24,6 @@ the GNU Taler team had with the European Central Bank, which 
informed
 them about a requirement for electronic wallets denominated in Euros
 to support password-less recovery.
 
-Anastasis will allow users to securely recover secret keys without
-necessarily relying on passwords or other key material.  Instead, the
-key material is split across multiple independent Anastasis service
-providers, and users are enabled to recover their master key by
-authenticating with each provider.
-
 Our protocol ensures that - without prior knowledge- the service
 providers learn nothing from the protocol except the minimum amount of
 data required to authenticate the user. Even that information is only
@@ -50,6 +51,8 @@ Challenge and Product / Service (1000 characters)
 -- Problem product addresses, how we overcome, Value-add
  -- core innovation
 
+NANA: more on the problem first? 
+
 Anastasis enables ordinary users to remain in control of their data --
 including ensuring their data remains available to them --, even if
 they cannot remember or securely store any sufficiently high-entropy
@@ -73,13 +76,18 @@ offered service.
 Description of research component (500 characters)
 -- relation to Distributed Data governnance / privacy by design
 
+NANA: simple => straightforward
+
 Secret splitting is a well-known technique for distributing
 trust. Given that the user is fully trusted, the Anastasis scenario is
-actually a simple form of secret splitting, as no distributed key
+actually a straightforward form of secret splitting, as no distributed key
 generation is required. However, Anastasis would likely be the first
-secret splitting services to be offered to end-users. Thus ease of
+secret splitting service to be offered to end-users. Thus ease of
 use and low operating costs are the real research challenges.
 
+NANA: reformulate on the research challenges, as never picked up later.
+NANA: will make proposal for formulation.
+
 Technology description: (500 characters)
 -- how does it work, architecture
 
@@ -102,6 +110,8 @@ example:  
https://twitter.com/VitalikButerin/status/1219059083451326464
 
 How will your product improve citizen's control over their data: (500 
characters)
 
+NANA: this is a bit repetitive, maybe more on the use-cases here?
+
 Having core secrets is crucial for all scenarios where citizens are
 their own data controllers. While being one's own data controller is
 the best-case scenario for privacy, the availability of the core

-- 
To stop receiving notification emails like this one, please contact
address@hidden.